ExposureGuidelines: Difference between revisions

→‎How do we know what web developers want?: Provide a better answer for this question
(Add clearer evaluation guidelines around feature additions/changes/removals)
(→‎How do we know what web developers want?: Provide a better answer for this question)
Line 115: Line 115:
==How do we know what web developers want?==
==How do we know what web developers want?==


* Mozilla's [[Engagement/Developer_Engagement|Developer Engagement]] coordinates a [https://openwebapps.uservoice.com/forums/258478-open-web-apps Open Web Apps UserVoice] forum
There's no good way to determine this currently, but feedback on GitHub, StackOverflow, workarounds in JavaScript libraries, MDN surveys, as well as use cases brought up during standardization help paint a picture.
* [http://chromestatus.com chromestatus.com] has a column for new features entitled "Documented or perceived web developer views"


==How do we know what other browser engines think?==
==How do we know what other browser engines think?==
Confirmed users
112

edits