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 17998 - Clarify what "immediately precedes" means here, in particularly I don't think that would include previous <rt> element.
Summary: Clarify what "immediately precedes" means here, in particularly I don't think...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Robin Berjon
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords: CR
Depends on:
Blocks:
 
Reported: 2012-07-18 07:58 UTC by contributor
Modified: 2013-08-16 21:31 UTC (History)
7 users (show)

See Also:

Attachments

Description contributor 2012-07-18 07:58:59 UTC 
This was was cloned from bug 15005 as part of operation convergence.
Originally filed: 2011-11-30 13:41:00 +0000

================================================================================
 #0   contributor@whatwg.org                          2011-11-30 13:41:30 +0000 
--------------------------------------------------------------------------------
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/text-level-semantics.html
Multipage: http://www.whatwg.org/C#the-rt-element
Complete: http://www.whatwg.org/c#the-rt-element

Comment:
Clarify what "immediately precedes" means here, in particularly I don't think
that would include previous <rt> element. 

Posted from: 114.43.115.15 by kennyluck@csail.mit.edu
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_1) AppleWebKit/534.48.3 (KHTML, like Gecko) Version/5.1 Safari/534.48.3
================================================================================
 #1   Ian 'Hixie' Hickson                             2011-12-07 23:34:44 +0000 
--------------------------------------------------------------------------------
It doesn't include a previous <rt> element because an <rt> element isn't phrasing content.

But I guess I'll try to find another way to describe it. Maybe by introducing a term that is defined imperatively (with an algorithm), and then saying that's what it annotates.

While I'm at it I should make multiple adjacent <rt>s be multiple annotations for the same content, and make it explicitly skip inter-element whitespace text nodes.
================================================================================
Comment 1 Erika Doyle Navara 2013-08-16 21:31:25 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:


   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: Looks like this was already fixed in both CR and 5.1 drafts. The description of rt has been rewritten and content model of ruby element clarified. For reference, here is the earlier version (containing this spec bug):

http://www.w3.org/TR/2012/WD-html5-20120329/single-page.html#the-ruby-element
http://www.w3.org/TR/2012/WD-html5-20120329/single-page.html#the-rt-element

And here is the current text in CR:

http://www.w3.org/TR/html5/single-page.html#the-ruby-element
http://www.w3.org/TR/html5/single-page.html#the-rt-element

Rationale: HTML WG already approved this change as part of WHATWG merge review process. Also work is underway for Ruby extension spec: http://darobin.github.io/html-ruby/