This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 15082 - rp should always represent nothing
Summary: rp should always represent nothing
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
Depends on:
Reported: 2011-12-06 15:03 UTC by contributor
Modified: 2012-07-18 18:39 UTC (History)
3 users (show)

See Also:


Description contributor 2011-12-06 15:03:23 UTC

rp should always represent nothing

Posted from: by
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0.1) Gecko/20100101 Firefox/8.0.1
Comment 1 Kang-Hao (Kenny) Lu 2011-12-06 15:11:50 UTC
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;}'.
Comment 2 Ian 'Hixie' Hickson 2011-12-07 23:51:05 UTC
I didn't want people abusing <rp> to hide stuff.
Comment 3 Ian 'Hixie' Hickson 2011-12-09 22:22:29 UTC
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:

Status: Rejected
Change Description: no spec change
Rationale: see comment 2