-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Learning more about web developers needs in the text and editing space #34
Comments
Thank you Taylore. @tidoust for visibility on this, as my co-chair on the group. This is a survey that our team at Edge would love to run in order to learn more about this space. |
Thanks! Added to next week's TPAC meeting's agenda. |
@captainbrosset thanks for notifying :) This looks to me like a good potential fit for MDN short surveys. I'll re-send the guidelines et al 👍 |
See #35 for the analysis. |
To help shape future investments in the text and editing space, we'd like to run a survey to understand web developer satisfaction and challenges with existing APIs. Below is an initial draft of the proposed survey content that we're looking for feedback from the CG on.
Survey prompt: We want to get feedback from web developers on the text and editing APIs listed below to help shape future investments in the space.
APIs shipping in at least one browser:
Response options for each API above:
API proposals:
Response Options for each API above:
Free form question: Are there any text or editing related features that are difficult to implement?
@sanketj @captainbrosset
The text was updated successfully, but these errors were encountered: