-
Notifications
You must be signed in to change notification settings - Fork 33
MDN short surveys design #196
Description
I have proposed to run short surveys on MDN to get some additional signals on the relative interest in the different features being proposed for Interop 2023.
This is not the only input for Interop 2023, just one more data point, and will have its blind spots.
We have a lot of proposals, and some of them have a very different target audience. Most of MDNs page views are for JavaScript reference docs like Array, so asking all MDN visitors about all features is not practical. Instead I've tried to created groups and targeting based on topic.
In the lists below, the survey wording is the first level and the proposals these map to (not shown in survey) is in a nested level. This is inherently an imperfect mapping, and wording choice can affect the results.
Prompt and Question
Survey prompt before expanding: "Browser vendors are working together to improve feature support across browsers. Shape the future of the web by taking this 1-question survey!"
(I'm open to toning down the "Shape the future of the web" bit.)
Question: "For your needs as a developer, which features should be improved across browsers in the coming year? This means enabling support or fixing bugs. Please rank up to 5. (This is not a complete list, other features may also be planned.)"
CSS & HTML
For pages under CSS and HTML, show this list:
- CSS attribute references (
attr()function) - CSS
backdrop-filterproperty - CSS
:blankand:emptypseudo-classes - CSS color font feature detection and palettes
- CSS color spaces and functions (
color(),lab(), gradients, etc.) - CSS containment (
contain,contain-intrinsic-size,content-visibility) - CSS custom properties (
@property) - CSS
:dir()pseudo-class - CSS
outlineproperty (includingoutline-color) - CSS images (
border-image,image(),image-set()) - CSS
leading-trimproperty - CSS
maskproperty (mask-image,mask-mode, etc.) - CSS math functions (
round(),sin(),pow(),abs(), etc.) - CSS motion path (
offset-path,offset-distance, etc.) - CSS media queries range syntax (example:
@media screen and (428px < width < 744px)) - CSS
:nth-child()pseudo-class with selector-list argument - CSS scoping (
@scopeat-rule) - CSS Typed Object Model (
computedStyleMap()API) - CSS
:user-invalidand:user-validpseudo-classes - Custom Paint API (Paint Worklet)
APIs & JavaScript
For pages under API and JavaScript, show this list:
- Canvas text rendering
- Clipboard API (
navigator.clipboard) - Editing (
contenteditable) - File System (
navigator.storage.getDirectory()) - History API (
window.history) - Import Maps
- Intersection Observer
- Navigation API (
window.navigation) - OffscreenCanvas
- Pointer Events
- Priority Hints (
fetchpriorityHTML attribute) - Push notifications
- Storage quota estimation (
navigator.storage.estimate()) - Temporal API
- URL (parsing and API)
- User agent client hints (
navigator.userAgentData) - Web Codecs (
AudioDecoder,VideoDecoder, etc.) - Web Components (custom elements, Shadow DOM, etc.)
- Web Components #181
- Form-Associated Custom Elements #203
- Constructable Stylesheets & adoptedStyleSheets #204
- CSS Module Scripts #206
- Imperative Slot Assignment #207
- :host(:has(...)) pointing to light DOM content #208
- @font-face and @property constructs in Shadow Roots #212
- Composed Selection (Selection APIs for Shadow DOM) #216
- WebTransport
Not Included
These proposals aren't included, for a variety of reasons:
- font-style for variable fonts with either Slant or Italic axes. #64 (hard to explain succinctly)
- Support for speak-as property to control aural presentation #114 (MDN short surveys design #196 (comment))
- Container Queries #133 (already have strong signals, likely to dominate results if included)
- :has() pseudo-class #134 (already have strong signals, likely to dominate results if included)
inertattribute +:modalpseudo-class #135 (MDN short surveys design #196 (comment))- User gestures #142 (hard to explain the exact scope)
- Machine Learning in the Browser #152 (MDN short surveys design #196 (comment))
- WebDriver BiDi #165 (target audience is mainly automation frameworks, not general web developers)
- Input write mode consistency #167 (hard to explain succinctly)
- RegExp lookbehind assertions #171 (too small?)
- css
conic-gradient#174 (already supported, unclear if there are bugs) - JPEG XL image format #176 (unclear which bucket makes sense)
- Animated AVIF #182 (unclear which bucket makes sense)
- WebGPU #185 (investigation effort)
- Web Compatibility #187 (mix of features)
- ES Module support for Web Workers #192 (this limitation is probably not widely known)
- Support for CSS Flexbox/Grid Gap Decorations #193 (new feature, likely to be conflated with flex gap)
- Non-responsive image loading #195 (hard to explain succinctly)
- MathML Core #197 (unclear which bucket makes sense)
- Mobile Testing #201 (test infrastructure)
- Consistent accessibility tree outputs #211 (not web exposed, affects users, not developers?)
- Cross-Origin Opener Policy: restrict-properties #213 (network feature, unclear which bucket makes sense)
- SVG 1.1 and 2.0 #214 (very broad, like MathML unclear which bucket)
- Web Performance: Paint Timing #215 (investigation effort)
- SameSite cookie handling #217 (network feature, doesn't fit either bucket)
- EditContext API #220 (unlikely to be recognized by web developers, not documented anywhere yet?)
- requestAnimationFrame in WorkerGlobalScope #222 (could be included under APIs, but hit limit of 20)
- Media pseudo classes:
:paused/:playing/:seeking/:buffering/:stalled/:muted/:volume-locked#224 (could be included under CSS, but hit limit of 20)