W3C home > Mailing lists > Public > public-multilingualweb-lt@w3.org > January 2013

RE: issue-77 Rule parsing precedence

From: Mārcis Pinnis <marcis.pinnis@Tilde.lv>
Date: Sun, 13 Jan 2013 10:45:44 +0200
To: Pablo Nieto Caride <pablo.nieto@linguaserve.com>, 'Yves Savourel' <ysavourel@enlaso.com>, "public-multilingualweb-lt@w3.org" <public-multilingualweb-lt@w3.org>
CC: Pēteris Ņikiforovs <peteris.nikiforovs@Tilde.lv>, Andis Lagzdiņš <andis.lagzdins@Tilde.lv>
Message-ID: <AC6FD4BB9BB02540AC7322091A6C3B5472B0D6B407@postal.Tilde.lv>
Hi Pablo and Yves,

Thank you for the clarification. I missed the external rules in the script element within a rule element (probably because it is not defined in one place, but rather scattered throughout the document).

Then the procedure is clear - top-down for link and script elements and top-down for all rule elements.

However, maybe it should be clarified so that interpretations could be limited.

" 6.4 Precedence between Selections" (also the more general XML related 5.5 section) mentions precedence between global rules, local attributes and defaults, however it does not explain the relations between inline rules and external rules (even if it is clear to some of us, it could not be the same for someone else). In our internal discussions an equally plausible sequence for reading rules was: all inline rules and only then external rules (or vice versa). Which conflicts with the non-written top-down precedence for everything (and is actually why the discussion was started). 

But ... it is clear that the "top-down everything" approach is the correct one...
Thanks again for clarification Yves and Pablo.

Best regards,
Mārcis ;o)

-----Original Message-----
From: Pablo Nieto Caride [mailto:pablo.nieto@linguaserve.com] 
Sent: Friday, January 11, 2013 8:19 PM
To: 'Yves Savourel'; public-multilingualweb-lt@w3.org
Cc: Pēteris Ņikiforovs; Andis Lagzdiņš
Subject: RE: issue-77 Rule parsing precedence

Hi Mārcis,

Yves is correct, I'm not sure if I understand exactly what you meant but developers can place the script element and the end of the body for speeding up purposes and still use both inline and external rules without precedence or overriding problems.

Cheers,
Pablo.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

> ... In such scenarios the external rules would always be overriden by 
> the inline rules and there would not be a possibility to use them in 
> such loading time sensitive scenarios (thus also my concern on the 
> limitation ...).

I'm still not sure I understand:
As far as I know *in any scenario* all global rules are overridden by the local ones.

(http://www.w3.org/TR/2012/WD-its20-20121206/#selection-precedence)

so external rules are always overridden by local attribute, just like in CSS.

or am I missing something?

> However, there is also a limitation – if prioritization is a top-down 
> one, the external rules can never override global rules that are in <body> tags!
> Please correct me if I am mistaken here?!

It can: an its:rules inside a <script> can have a link to an external file.

In other words, you have two ways to get external rules in HTML: the <link> element or the link attribute in <its:rules> inside <script>.

cheers,
-yves





Received on Sunday, 13 January 2013 08:46:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:08:26 UTC