- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Wed, 30 May 2007 17:52:19 +0100
- To: public-html@w3.org
- CC: wai-ig list <w3c-wai-ig@w3.org>, wai-xtech@w3.org
Thomas Broyer wrote: > The point is that, as actually designed, HTML5 define *one* way of > processing HTML that is compatible with what browsers do today. ... > HTML5, by design, tries to reduce browsers incompatibilities by > standardizing their current behaviors. The goal is not to have "yet > another standards mode". In that case, I wonder: why do we actually have the "headers attribute in tables" debate? Current screen readers (assuming that you generally meant "user agents" when saying "browsers") support them and use them. Not including them in the spec would result in breakage - unless we're hoping that any heuristics that were defined to compensate for the removal of headers will still be able to silently extract the same information from the table while ignoring the headers themselves and treating them as invalid code? P -- Patrick H. Lauke ______________________________________________________________ re·dux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.com ______________________________________________________________ Co-lead, Web Standards Project (WaSP) Accessibility Task Force http://webstandards.org/ ______________________________________________________________ Take it to the streets ... join the WaSP Street Team http://streetteam.webstandards.org/ ______________________________________________________________
Received on Wednesday, 30 May 2007 16:52:29 UTC