Anne van Kesteren

Interesting bugs

Interesting Mozilla bugs. NOTE: It is not interesting that they have bugs, but that they already started to implement these things.

• CSS3 selectors. This bug is a tracking bug for every the new CCS selectors. There aren't bugs for every selector yet, but some are already (partly) implemented. I'm not sure about this, maybe someone can confirm if it is ok to open new bugs for other selectors?
• ::first-line in CSS2.1. See the example from Ian Hixie why it should be 'outermost' (that is also the reason it is still a Mozilla bug). The only thing I don't understand is why it is 'innermost' in CSS3, though that will be discusses I hope.
• :target selector. This is a CSS selector and a part of the first mentioned bug. The only problem left is that you it currently impossible to do this: :target{background:green;}. This should match the root element of the document, but currently it doesn't, that is why this bug is still there.
• ::selection element. This pseudo-element is already available within Mozilla as ::-moz-selection. If all the the other problems are solved, it will be named the same as the CSS3 pseudo-element. I really like it, but it affects the accessibility in a hard way. You could style the selected text for example exactly the same as the text looks normal :).

The example code from Hixie (written in CSS and XHTML, duh..). Note that this code is not correctly rendered in IE. Please view source ;):

<p>
 Line one <span> Line one. </span> Still line one. <span> Line one.
 Line two. </span> Line two.
</p>

::first-line{
 background:no-repeat url(blob) top left;
}

After I thought about this for a while it seems to be totally correct to not render it innermost. The only disadvantage of this is that people could think the following rule is valid (it is invalid): ::first-line span. This is invalid since there can't be any selector after a pseudo-element. With pseudo-classes this is perfectly fine, so :hover + span is ok, but it doesn't work in Mozilla.