12
edits
Firefox/Feature Brainstorming:Web Standards Support: Difference between revisions
Jump to navigation
Jump to search
Firefox/Feature Brainstorming:Web Standards Support (view source)
Revision as of 12:39, 25 October 2006
, 25 October 2006add request for runtime page health feedback
No edit summary |
(add request for runtime page health feedback) |
||
| Line 7: | Line 7: | ||
; Make spellchecker standard-friendly | ; Make spellchecker standard-friendly | ||
Firefox is known for its compliance to standards - then suddenly it introduces the "spellcheck" attribute. How are we any better, then, than Microsoft and all its superfluous DOM extensions? Please, put the spellcheck attribute in a namespace, get it approved by the W3C, or drop it. | Firefox is known for its compliance to standards - then suddenly it introduces the "spellcheck" attribute. How are we any better, then, than Microsoft and all its superfluous DOM extensions? Please, put the spellcheck attribute in a namespace, get it approved by the W3C, or drop it. | ||
</td><td> | |||
</td></tr> | |||
<tr><td> | |||
; Report site health at runtime | |||
Do not wait till pages are terminally broken before failing users and developpers. Provide unobstrusive run-time feedback on the errors encountered so pages can be proactively fixed | |||
* The [http://users.skynet.be/mgueury/mozilla/ HTML validator] extension shows how such a feedback could be provided without overwhelming the user. Its main value is errors/warnings are detected when they occur, not when someone thinks about looking for them. | |||
* If you wait till people take the time to open the debugger/console and/or run the various offline validators you've already lost. | |||
* You can't blame non-technical people from setting up broken websites or webapps if the PHBs have no easy way to check the contractors actually delivered clean code. | |||
</td><td> | </td><td> | ||
</td></tr> | </td></tr> | ||