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 11365 - "An rp element whose parent element is not a ruby element" - confusing, as this doesn't seem to be supported based upon contexts in which this element can be used.
Summary: "An rp element whose parent element is not a ruby element" - confusing, as th...
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-21 21:07 UTC by contributor
Modified: 2011-08-04 05:34 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-11-21 21:07:18 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/text-level-semantics.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#the-rp-element

Comment:
"An rp element whose parent element is not a ruby element" - confusing, as
this doesn't seem to be supported based upon contexts in which this element
can be used.

Posted from: 98.193.44.168
Comment 1 Ms2ger 2010-11-22 10:29:34 UTC 
It isn't allowed, but it is supported. That's why this is inside span.impl.
Comment 2 Michael[tm] Smith 2011-08-04 05:34:09 UTC 
mass-move component to LC1