This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section: http://www.whatwg.org/specs/web-apps/current-work/#tabular-data Comment: Define inheritance of lang, dir, style, and presatational attributes (HTML4 §11.3.2.1 "Inheritance of alignment specifications") [ms] Posted from: 91.180.138.210
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Did Not Understand Request Change Description: no spec change Rationale: In what sense is this not already done? Could you give an example of a Web page whose processing isn't defined?
It's defined, but in a counter-intuitive way. Given the code <table lang=en> <col><col><col lang=de> <tr> <td>Foo <td>Bar <td>Bäz </table> According to HTML5, the language of "Bäz" is English. HTML4 defines it to be German, which is probably closer to the author's intention.
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: Ah, indeed. Yes, HTML4's processing would be ideal. However, as far as I can tell it's still not what browsers implement, and they've had more than a decade, so I don't see much point in continuing to insist on this. If you would like this changed, I recommend pushing on browser vendors first.