- From: <bugzilla@jessica.w3.org>
- Date: Fri, 10 Jun 2011 17:23:51 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12935
Summary: <rt> should not auto-close <rtc>
Product: HTML WG
Version: unspecified
Platform: PC
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: HTML5 spec (editor: Ian Hickson)
AssignedTo: ian@hixie.ch
ReportedBy: bzbarsky@mit.edu
QAContact: public-html-bugzilla@w3.org
CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
public-html@w3.org
We're implementing ruby support in Gecko, and discovered that the HTML5 parsing
algorithm requires that <rt> close <rtc>.
This behavior does not match the pre-HTML5-parser Gecko behavior, the
pre-HTML5-parser WebKit behavior, Presto, or IE9+.
It does match IE8-.
Given that IE has already changed its behavior here once, I see no reason to
require them to change it again to what is arguably a less-useful behavior. So
I think what we should do is to remove the <rt> magic from the spec entirely,
simplifying the spec and making it compatible with what IE9, Gecko 1.9.2,
Presto, and pre-HTML-parser WebKit.
There will still be the issue that it's not safe for authors to actually use
<rtc> until IE8- marketshare becomes negligible, but I would expect the
timeframe for this to be on par with the timeframe for HTML5 getting anywhere
close to REC if not shorter. In the meantime, there is clearly not a serious
web compat issue with the proposed change, since IE9, Gecko 1.9.2, Presto, and
pretty recent WebKit all have/had that behavior. So there should be nothing
stopping Gecko and WebKit from changing away from their current behavior.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 10 June 2011 17:23:53 UTC