[Bug 15174] rendering.html quotes rules don't allow inheritance of author-specified 'quotes'

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

--- Comment #2 from Peter Moulder <peter.moulder@monash.edu> 2011-12-14 11:55:32 UTC ---
To help with making an informed evaluation of the proposed change, I should
point out a possibly-unexpected aspect of its behaviour:

The fragment

  <body lang="en" style="quotes: '« ' ' »'">
    <p lang="en">Hello, <q>world</q></p>
  </body>

will still render as Hello, “world” with the proposed change, because the
explicit lang attribute on the p element still causes the stylesheet rule to
match, thus interrupting the inheritance from body.  I.e. any explicit use of
lang or xml:lang will reset the quotes to that language's default quotes.

I have a niggling concern about the definition of the language of a node and
the part about namespaceless lang attribute only having effect on HTML
elements, whereas the suggested rule causes resetting of 'quotes' for any use
of namespaceless lang attribute or xml:lang attribute even in places where they
aren't valid or don't affect the language of elements.  I'm not aware of
problems this would cause in practice, but possibly the [lang] part of that
should be restricted to html|* elements (i.e. change [lang]:lang(en) to
html|*[lang]:lang(en)), if that captures the intended meaning of "HTML
elements".


Btw, in elements.html (section 3.2.3.3 The lang and xml:lang elements), the
text "if none of the ancestors" is presumably not exactly correct, and should
probably be changed to "if neither the node nor any of its ancestors".  (I'm
not sure that that suggested text is actually an improvement (given that the
intent should already clear from two paragraphs up, and given certain
conceivable misunderstandings of that suggested replacement text), though it is
displeasing that the existing text says something other than what's meant.)

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 14 December 2011 11:57:35 UTC