|
![](/i/fill.gif) |
Orchid XP v8 escreveu:
>>> I'm particularly pleased with how I managed to insert chevrons
>>> *between* the links, but not before or after them. That look some
>>> figuring out.
>>
>> I was thinking about how you managed that one.
>
>> Guess I'm missing latest CSS goodies, cause I've not heard of "content:"
>> before...
>
> I read about the "content:" property way, waaaaaay back in 1998 or so.
damn, I'm truly behind the times... :p
ok, I'm just unaware of the complete spec... I've got the box model
pretty worked out though... :)
> Of course, reading about this, I was very excited, and immediately went
> to try it out. But, as it turns out, neither Netscape nor IE took any
> notice of these properties at all. I promptly forgot all about them,
> since they don't work.
>
> (In a similar vein, it's supposed to be possible to add drop shadows to
> text and so on. That didn't work either.)
weirdly enough, I'm aware of latest CSS goodies like drop shadows,
transitions, gradients, border-radius and so on. Since they are still
experimental, web browsers tend to have them available only via prefixes
such as -moz-border-radius or -webkit-border-radius... won't cause any
problem to browsers unaware of them because html-related techs were
build around the idea to simply ignore tags and properties they don't
understand.
Imagine if they used a static type system like in haskell: "This page
can't be shown: a type mismatch has occurred!" :)
> Fast forward 10 years, and it seems these funky features are actually
> *implemented* now. (I didn't bother to check whether IE supports it -
> mainly since I don't give a damn.)
yeah, what percentage of your 2 blog readers would possibly be using IE?...
--
a game sig: http://tinyurl.com/d3rxz9
Post a reply to this message
|
![](/i/fill.gif) |