Interop 2023
estelle opened this issue · 0 comments
Problem statement
Ensure most recent interop features are fully documented on MDN
Proposed solutions
Ensure all documentation for interop features exist, updating content that already exists for Baseline, support lingo, removing unnecessary fallback information, linking to related content, and creating new content (guides mostly) if missing.
Task list
- Border Image
- Color Spaces and Functions
- Container Queries
- Containment
- CSS Math Functions
- CSS Pseudo-classes
- Custom Properties
- Flexbox
- Font Feature Detection and Palettes
- Forms
- Grid
- :has()
- Inert
- Masking
- Media Queries 4
- Modules
- Motion Path
- Offscreen Canvas
- Pointer and Mouse Events
- Scrolling
- Subgrid
- Transforms
- URL
- Web Codecs (video)
- Web Compat 2023
- Web Components
For each topic above, do the following:
- Module landing page updated
- Links between module and reference pages
- Create or update topic guide
- Check "learn", removing fallbacks and legacy lingo
- Accessibility, performance, and security covered
- Baseline grouping
- Feature browser tests (from interop page)
- Test topics covered in reference page
- <100% - check and document failed tests
Priority assessment
These topics were all considered important enough to be included in last year's interop. They have all been addressed in 2023 and should be fully supported in all browsers and fully covered in MDN docs. We need to confirm that they are covered, that guides exist and are useful, and the content is accurate and well linked, while ensuring new feature coverage is relevant to developer needs, discusses accessibility and best practices, and doesn't promote new features over more mundane legacy features.