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 25954 - [new ruby model] Step 13 of segmentation algorithm may be removed.
Summary: [new ruby model] Step 13 of segmentation algorithm may be removed.
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-03 07:32 UTC by tkawabat
Modified: 2014-06-04 14:52 UTC (History)
4 users (show)

See Also:


Attachments

Description tkawabat 2014-06-03 07:32:11 UTC
he Step 13 of [1] (13. If root has a ruby element ancestor, then abort
these steps.) prohibits the the processing of nested ruby.

However, nested ruby feature is already implemented in Chrome and
Safari, and it is likely that someone in the world may already use it.
Also, it is unclear that what would be the expected result of
"aborting" the process.

As of it, I think that Step 13 of [1] may be no longer necessary, and
would like to propose to remove the step 13 from the specification.

[1] ...
http://www.w3.org/html/wg/drafts/html/CR/text-level-semantics.html#segmentation-and-categorisation-of-ruby
Comment 1 Robin Berjon 2014-06-04 14:52:27 UTC
I agree with your assessment, and have therefore removed this limitation.