[Webkit-unassigned] [Bug 103172] implement the HTML <main> element

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sun Nov 25 11:29:16 PST 2012


https://bugs.webkit.org/show_bug.cgi?id=103172


Ian 'Hixie' Hickson <ian at hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ian at hixie.ch




--- Comment #12 from Ian 'Hixie' Hickson <ian at hixie.ch>  2012-11-25 11:31:25 PST ---
Personally I don't care one way or the other; the reason it's not in the WHATWG spec isn't about my opinion, it's about the lack of compelling use cases. Adding a feature to the platform is expensive. Adding a feature which is likely to be misused (as determined by looking at how people use class=main now, compared to the proposed definition of the element) just pollutes the Web for no good reason.

In the case of this patch the danger is even worse; it is likely to actually make accessibility worse. The patch makes <main> act like role=main, but this will cause the many pages that will misuse it to report less useful results to AT users than if the element wasn't there. There are other mechanisms that have been suggested for similar results, which are less likely to be misused.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list