This is a problem split from 54467.
As CSS specs 5.12.2 metioned :
"Some languages may have specific rules about how to treat certain letter
combinations. In Dutch, for example, if the letter combination "ij" apprears at
the beginning of a word, both letters should be considered within the
Should we include those situations? I doubt if anyone will list a lot of such
examples. Even to include above mentioned example is rather difficult, because
we have to know what language it is. (Encoding normally is easier to get. )
It is not clear either we want to implement this or not. But anyway, I don't see
any solution in near future.
This bug belongs to Internationalization, like bug 54467.
i18n folks need to identify the combinations of letters that should be considered
as a single letter, and the language in which they occur, then extend the patch
crafted by Shanjian in bug 54467 keeping in mind that the :first-letter pseudo
can in fact cover up to 3 characters (1 punctuation sign + 2 letters).
reassining to the correct core and core owner.
Apparently, \u0132 en \u0133 are the Unicode characters for the Dutch "ij".
Could this be resolved as WONTFIX now there are characters for this? (I will
bring this up at www-style.)
In most cases ij or IJ isn't seen as one character in Dutch and in most
publications it isn't treated as such. I doubt whether the single character
unicode values for ij/IJ are ever used in Dutch publications at all.
Some Dutch references on the usage of ij can be found on:
Seeing popular use and the very limited support of the unicode signs it doesn't
make sense to not support it. Although it has been tried to get computers to see
it as one character before (Dutch DOS character set and keyboards had it as a
single sign), no one actually uses it. It is not even auto converted for in most
Corrected the summary.
Also, that's already documented https://developer.mozilla.org/en-US/docs/Web/CSS/::first-letter.
Sebastian: doesn't this mean that this is a duplicate of another bug? (meaning it should be RESOLVED DUPLICATE or RESOLVED WORKFORME)
I couldn't find any other bug related to this. And it is also not implemented yet.
What is done is the documentation of the feature according to the specification (though no browser seems to support this yet). FWIW I added a test case in the URL field.
Maybe I was too hasty, as the browser compatibility table still needs to be updated once this bug is fixed. Should the keyword be changed back to dev-doc-needed?
Yep, that we update Fx XY for devs and the compat table when this lands :-)