@Jake Oh, isn’t it? Shit, I’m actually USING it. I am fully expecting it to bite me in the arse, though.
I tested the ‘content’ property across FF/Opera/Safari/Chrome (but admittedly only the latest versions) and got it to work. I’ve yet to test IE9 (because my VirtualBox has flaked out for the moment). Not bothered about IE<9 seeing as they won’t see the media queries anyway.
One thing I found was that if you want to pass JSON across, you have to lop off leading and trailing quotes, which I found odd. It seems that if you define this:
content: ‘hello’
then querying the CSS gives you “hello”, but if you define this:
content: ‘{“message”: “hello”}’
then querying the CSS gives you “’{“message”: “hello”}’” – ie. the single quote marks become part of the string. Weird.
Stephen Band
@Jake Oh, isn’t it? Shit, I’m actually USING it. I am fully expecting it to bite me in the arse, though.
I tested the ‘content’ property across FF/Opera/Safari/Chrome (but admittedly only the latest versions) and got it to work. I’ve yet to test IE9 (because my VirtualBox has flaked out for the moment). Not bothered about IE<9 seeing as they won’t see the media queries anyway.
One thing I found was that if you want to pass JSON across, you have to lop off leading and trailing quotes, which I found odd. It seems that if you define this:
then querying the CSS gives you “hello”, but if you define this:
then querying the CSS gives you “’{“message”: “hello”}’” – ie. the single quote marks become part of the string. Weird.