|
|
Posted by Luigi Donatello Asero on 02/27/06 17:25
"Michael Winter" <m.winter@blueyonder.co.uk> skrev i meddelandet
news:OBiMf.26795$wl.17280@text.news.blueyonder.co.uk...
> On 26/02/2006 09:21, Els wrote:
>
> [snip]
>
> > (If I understood appendix B of the CSS1 specs correctly (of which I'm
> > not sure), only 1 class/id/pseudo-class is allowed per selector in
> > CSS1)
>
> I'm not quite sure what you're trying to express, here.
>
> .className or #id
>
> but not
>
> #id.className
>
> An id, class, or pseudo-class selector can appear by itself [optionally
> combined with an element], but more than one type of attribute selector
> cannot be combined.
>
> Or perhaps:
>
> #id.className
>
> but not
>
> .class1.class2
>
> Multiple attribute selector types can be used together, but only one of
> each type can be used at once.
>
> As I read it, the grammar permits the latter, but it also places very
> tight constraints on the /order/ of simple selector components: element,
> id, class, pseudo-class. A simple selector can contain any of these, but
> if any are present, they must appear in that order and can only occur
> once at most.
>
> The reason why
>
> .subsubsection#sverige a
>
> fails is because the id selector follows the class name.
>
> #sverige.subsubsection a
>
> will be accepted.
So is the latter the correct form although the former is tolerated?
Is
#sverige.subsection a=
<a class="subsection" id="sverige"> ?
--
Luigi Donatello Asero
https://www.scaiecat-spa-gigi.com/sv/faktaomitalien.php
今天二零零六年二月二十七日
星期一
Navigation:
[Reply to this message]
|