On 21/09/2010 03:27 PM, Le_Forgeron wrote:
> Le 21/09/2010 16:19, Invisible a écrit :
>>>> Irritatingly, what you *cannot* do is content: "→ ". This is
>>>> extremely frustrating, and currently I cannot find any way around this
>>>> flaw.
>>>
>>> content: "\2192"
>>
>> Oh God, you *are* kidding me, right?? o_O
>
> content: is not reparsed by the engine, so no entities would be
> substituted, but that should not stop you to encode the right char.

It's even weirder than that: If the CSS is a seperate file (like it 
normally is), this doesn't work. But if it's inline inside the HTML 
file, then it *does* work. (!)

Presumably because the character stream inside the <style> element in 
the document head has entities expanded during parsing.

Post a reply to this message