Web Compatibility #187
Description
Description
A focus area for small bugs that cause known site compatibility issues, or documented problems for authors creating libraries or sites, but which are not part of a larger feature that's appropriate for its own focus area.
Rationale
Observed compatibility bugs which cause breakage for users are often not missing features, but specific cases where existing browsers don't follow the spec for features that are implemented. On their own these would be hard to fit into the Interop process since a focus area for a single bug, however important, is hard to weigh as part of the metric. However having a single focus area for these issues seems to have worked well in 2022, with browsers going from ~20% to ~100%, and fixing several bugs that were known to cause problems for users, but had not previously got priority.
Specification
All included bugs will have a specification (although in some cases it may be that "success" is changing the specification, testcase, and "conforming" implementations to match what's actually required by compat).
Inclusions will be motivated by observed compat issues (e.g. in webcompat.com or author-reported issues that they've had to work around when developing libraries.
Tests
Since this is a somewhat miscellaneous selection of bugs, it's anticipated that tests may be added from other focus areas where the overall focus area doesn't get priority but there are a small number of observed pain points which do get priority. During the selection process participants can request removal of any tests that would cause them to object to the proposal.
Suggested bugs / rationale (tests to be added):
- Remove (or standardise?) overflow: overlay
- Flexbox/abspos paint order
- Decorating box semantics