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/text-level-semantics.html Multipage: http://www.whatwg.org/C#the-rp-element Complete: http://www.whatwg.org/c#the-rp-element Comment: rp should always represent nothing Posted from: 114.43.125.198 by kennyluck@csail.mit.edu User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0.1) Gecko/20100101 Firefox/8.0.1
Some data: IE9 doesn't display standalone <rp> produced by document.body.appendChild(document.createElement('rp')) (The markup <!DOCTYPE html><rp>test</rp> won't generate an <rp> element so there's probably also parsing inconsistency, but that's another issue) but window.getComputedStyle(document.querySelector('rp')).display always gives 'inline' no matter it's in a <ruby> or not. WebKit is following the spec here. I am just curious about why is 'ruby > rp { display: none;}' better than 'rp { display: none;}'.
I didn't want people abusing <rp> to hide stuff.
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: see comment 2