-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs: add adr and note in contribution guideline about browser support
- Loading branch information
1 parent
c70d6d7
commit c4f4a9e
Showing
2 changed files
with
42 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
# ADR008: Browser Support | ||
|
||
## Status | ||
|
||
Accepted | ||
|
||
## Context | ||
|
||
Our legacy application has been experiencing issues with Firefox and other | ||
non-Chromium browsers. These issues have been causing delays in development and | ||
have been a source of bugs that are hard to track and fix. Moreover, we want to | ||
leverage the latest web features such as CSS nesting, which are best supported | ||
and regularly updated in Chromium browsers. Supporting only the latest 2 | ||
versions of Chromium browsers (Chrome and Edge) will allow us to focus our | ||
efforts on a more narrow range of browsers, reducing the complexity of our | ||
development and testing processes. | ||
|
||
## Decision | ||
|
||
We will only officially support the latest 2 versions of Chromium browsers | ||
(Chrome and Edge). This means that while the application may still work in other | ||
browsers, we will not be spending resources on testing and fixing issues that | ||
are specific to those browsers. | ||
|
||
## Consequences | ||
|
||
- Development will be easier as we only need to consider the latest 2 versions | ||
of Chromium browsers. | ||
- We can leverage the latest web features that are best supported in Chromium | ||
browsers. | ||
- We will need to test the application in the latest 2 versions of Chromium | ||
browsers. | ||
[This is not possible with Playwright, which always tests against the latest stable version](https://github.com/microsoft/playwright/issues/14435). | ||
Therefore, a small possibility of bugs in older versions remains. | ||
- Users using other browsers may experience issues. | ||
- We will need to clearly communicate this decision to our users and update our | ||
documentation accordingly. |