This document:Public document·View comments·Disposition of Comments·
Nearby:Mobile Web Best Practices Working Group Other specs in this tool Mobile Web Best Practices Working Group's Issue tracker
Quick access to LC-442 LC-443 LC-444 LC-445 LC-446 LC-447 LC-448 LC-449 LC-450 LC-451 LC-452 LC-453 LC-454 LC-455 LC-456
Previous: LC-452 Next: LC-443
1) 5.1.3 Work around deficient implementations. Question: If I conform to standards without looking further, do I satisfy this practice? If the answer is "yes" then I am satisfied and ask only that this be made clear in the document. If the answer is "no, you have to do more than conform to standards," then I have an issue. I think it places an unreasonable burden on authors to have to learn about the diverse landscape of browsers, platforms, and bugs. There may be large organizations that have resources to do this, but I believe that for the millions of individuals or small organizations that will likely wish to satisfy this document (or be required to, who knows), this is an unreasonable burden. Instead, I suggest: "Even if it means that you have to deviate from standards, you MAY work around deficient implementations." I realize that the group is creating "best practices" and considers this to be good practice. However, even if satisfying this requirement is possible for a few content providers, I think it will be very difficult for ordinary authors. If content that conforms to the standards that define the default delivery context satisfies this requirement, then please make that abundantly clear. However, because authors are asked to do more than design for the default delivery context (practice #2), it still sounds like one is forced to go beyond the defaults in order to conform. Lastly, I believe a desirable property of conforming content is that once it conforms, it always conforms. Because browser bugs vary over time, content that once conformed may not conform in the future. One way to handle this is to date conformance claims, but that does not improve on the fact that the content's conformance status may vary over time.