Problem/Motivation

  • #2390621: [policy, no patch] Update Drupal's browser support policy lists the browsers we intend to claim to support. Once that issue is fixed, that list will be published to https://www.drupal.org/docs/8/system-requirements/browser-requirements.
  • That list includes browsers that require certain devices to run. For example, iOS Safari requires an iPhone. Samsung Internet requires a Samsung phone. We can't expect every contributor, reviewer, or maintainer to own every device.
  • Emulators exist for some browsers, but a) don't always emulate perfectly, and b) don't exist for every browser.
  • Commercial services, such as BrowserStack, can assist with real-device testing. For BrowserStack specifically, individual contributors may purchase a license to use the service, or an open source project may apply for a project license, but that comes with certain terms, such as placing their logo on the project's website, and has limits for how many users from a project are given access. Additionally, Opera Mini is not testable via BrowserStack.

Proposed resolution

  • Decide on what we expect the process to be for a) front-end patches in general, and b) patches that fix a bug for a specific browser. For example, does a patch that fixes a bug for Samsung Internet require the reviewer who RTBC's the patch to test on Samsung Internet? Does it require the committer who commits it to test on Samsung Internet?
  • Decide on how we achieve automated testing for these fixes to prevent their future regressions.
  • Discuss whether Drupal core as a project should apply for a license to BrowserStack or similar service, and if so, work out the details of that with the Drupal Association.
  • Anything else?

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Comments

effulgentsia created an issue. See original summary.

effulgentsia’s picture

effulgentsia commented
Issue summary: View changes
wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented

TIL we have a browser system component 🤯

catch’s picture

catch
he/him
Primary language English
commented
Component: browser system » other

The browser system component pre-dates Guzzle and we should probably remove it...

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.