-
Notifications
You must be signed in to change notification settings - Fork 4
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
Discussion - week of 07/21/14 #57
Comments
Interesting tests results. Though hard to make a direct correlation from these user tests with data from submission website, seems to validate that a larger percent of app submission validations fail validation. Creating manifests is difficult for many developers, especially with packaged apps that then need to be edited, repackaged, and retried. If there is a way to auto-generate some of the manifest, that might help. |
Many respondents have remarked that starting from a sample file (versus from scratch) will net them more correct end results. We specifically chose not to test a sample file here, because we want our respondents to read the instructions and see whether we can make improvements to the existing MDN article. Once they get a helpful sample file to start with, our validation and correctness rate might jump up. This might be an interesting research to do later, when we want to validate our chosen approach. |
"Less than 10% named the file correctly as manifest.webapp. This is likely to be a major source of manifest validation failure." |
Thanks for the information. That information can be added to the instructions on MDN. |
This is where we'll talk this week.
The text was updated successfully, but these errors were encountered: