[Bug 24451] editorial comments on LCWD

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24451

Eliot Graff <eliotgra@microsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #7 from Eliot Graff <eliotgra@microsoft.com> ---
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: Partially (mostly) Accepted
    Change Description: See comments. CVS Commit 1.31
    Rationale: Varied, and explained in comments

Would appreciate any further feedback you have. Smaller bugs would be better,
though. ;-)

The XML Core Working Group has reviewed the document and decided to give no
comments.

Liam,

Thank you so much for taking the time to go through this spec in such detail
and with such thought. We really appreciate your time and effort.

Eliot


3.6.2.2.1 Safe CDATA usage rules
Can't repro the first two editorial requests.
Commented out (in source) the two bullet points about nodes, to give Leif time
to respond. If he says OK, will remove them entirely.

EXAMPLE 12
has a </script> but no <script>, is that intended?
   Added opening <script>
Disadvantage is removed, as we're leaving usage advice for another venue.
Therefore, we'll leave off the problem of CDATA injection.

3.6.3 Escapable raw text elements
   edits incorporated

3.6.5 Normal Elements
   Removed commas, used parentheses instead
   Reworded and retitled section:
4.6.5 Special elements
Unless otherwise specified, elements have no special restrictions other than
those that apply to all polyglot markup.

The iframe element has restrictions in polyglot markup, because the HTML
specification sets special restraints on iframe in XML documents. [HTML5]

3.7.1 newlines
   Incorporated suggested text.

3.8 Attributes
   Changed sentence to:
For example, within an attribute's value, polyglot markup uses &#x9; for a tab
rather than the verbatim string literal, \t. This is because of <link>attribute
normalization</link> in XML [XML10]. Note, too, that JavaScript and CSS in
attribute values are affected by attribute value normalization, because a
comment ends up commenting out not to the end of the source line but to the end
of the entire attribute value. 

3.8.1 Disallowed attributes 
   Rewrote note to say:
Note that the xml:space and xml:base attributes <strong>are</strong> allowed on
SVG and MathML elements. The attributes may therefore appear in polyglot markup
when they appear within SVG or MathML as foreign content.

3.8.3.1 The id attribute
   Added:
Polyglot markup ensures that every id attribute must be unique within the
document and must be a legal XML name, starting with a letter. [XML10] 

4.9 Named entity references
 changed to:
 however for CDATA inside foreign content, strings within comments, and for
safe CDATA, the following rules apply:

3.10 Comments
   Changed to
Polyglot markup begins a comment with either "<!" or "<!--". Polyglot markup
does not begin a comment with either ">" or "->". 

3.11.1 s/XHTM/XHTML/

3.11.2 CSS
s/[attr]{Foo:value;}/[attr]{property:value;}
comma removed


   Changed the paragraph in question to the following:
However, some of the attributes required by polyglot markup are namespaced.
Some are namespaced by default, such as the xmlns attribute. Some attributes
are namespaced by a prefix that is namespaced by default, such as xml:, xmlns:,
and xlink:. In addition, extension specs may allow namespaced attributes other
than those defined by the HTML specification. As result, a selector such as
[xmlns]{rule:foo} will not work in XHTML, where the attribute has an associated
namespace. The same is true for prefixed attributes. Even if one escapes the
colon ([xml\:lang]{rule:foo}), such selectors will only work in HTML (except
for the namespace declaration for the xlink: prefix. This works in XML and in
HTML and must thus be selected in a namespaced way in both syntaxes).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 19 March 2014 23:58:18 UTC