This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/obsolete.html Multipage: http://www.whatwg.org/C#non-conforming-features Complete: http://www.whatwg.org/c#non-conforming-features Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/index.html Comment: what about <rtc>? See also https://www.w3.org/Bugs/Public/show_bug.cgi?id=26187 Posted from: 50.163.53.37 User agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.84 Safari/537.36
To elaborate: <rb> is listed explicitly as a "non-conforming" feature. Is <rtc> non-conforming as well? (The parsing of these tags differ between the W3C and WHATWG specs, see https://www.w3.org/Bugs/Public/show_bug.cgi?id=26187 ).
Support for parsing <rb> and <rtc> has landed in webkit (https://bugs.webkit.org/show_bug.cgi?id=131175) and gecko (https://bugzilla.mozilla.org/show_bug.cgi?id=664104). Are there any technical objections to adding these to the WHATWG spec?
*** Bug 26187 has been marked as a duplicate of this bug. ***
<rtc> didn't exist until some browsers added it, that's why it wasn't listed as obsolete. There are arguments against it, see bug 20114 and bug 20115. However, if browsers are ignoring the spec and implementing it anyway, then it's time to ignore whether it's a good idea or not, and spec it because it's reality...
If browsers do decide to continue down this flawed path, here's a few tests (though given the complexity of ruby in the HTML spec I imagine we'll need many more): https://github.com/html5lib/html5lib-tests/pull/27/files
https://github.com/whatwg/html/pull/101