You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.)"
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:
attr()function)attr()support extended capabilities (Interop 2023) #86backdrop-filterproperty:blankand:emptypseudo-classes:blankpseudo-selector support (re form fields) #179color(),lab(), gradients, etc.)contain,contain-intrinsic-size,content-visibility)@property)@property#158:dir()pseudo-class:dir()improved support #177outlineproperty (includingoutline-color)border-image,image(),image-set())border-image#146image()function #153leading-trimpropertyleading-trim#155maskproperty (mask-image,mask-mode, etc.)round(),sin(),pow(),abs(), etc.)offset-path,offset-distance, etc.)@media screen and (428px < width < 744px)):nth-child()pseudo-class with selector-list argument:nth-*pseudo-classes interoperability #225@scopeat-rule)computedStyleMap()API):user-invalidand:user-validpseudo-classes:user-invalid&:user-validbrowser support #178:emptypseudo-selector (spec updated) #180APIs & JavaScript
For pages under API and JavaScript, show this list:
navigator.clipboard)contenteditable)navigator.storage.getDirectory())window.history)window.navigation)fetchpriorityHTML attribute)navigator.storage.estimate())new URL()#145navigator.userAgentData)AudioDecoder,VideoDecoder, etc.)Not Included
These proposals aren't included, for a variety of reasons:
inertattribute +:modalpseudo-class #135 (MDN short surveys design #196 (comment))conic-gradient#174 (already supported, unclear if there are bugs):paused/:playing/:seeking/:buffering/:stalled/:muted/:volume-locked#224 (could be included under CSS, but hit limit of 20)