Oh yes - There will be lawsuits.
This has to be one of the more absurd (internet related) schemes for profit that I’ve heard. But it does bring me one step closer to a real life version of that scene in hackers when the feds bust into my apartment to arrest me. Or maybe a different, more lawerly, subpoena-eee version of that story. Keep reading.
UPDATE c/o of Brad Frost – Doing this will invalidate your CSS! However, this is appropriate because 1.) We know exactly what is keeping our CSS from validating and 2.) We did it anyways to get something we want to work in another browser.
This is one of the few situations where it’s ok to ignore the ! in your web developer bar.
——————————————————————————-
So I made a slight joke about progressive enhancement in a previous post, but let’s be real for a second: If you could easily get all your site features working the same way in every browser, you would.
Well, as far as IE6 – 8 go, you can get opacity to work. Normally we’d code opacity into our stylesheet like so:
It’s super easy to get this CSS rule to comply in IE6+ – but it does involve the inclusion of another CSS invalidating Microsoft filter effect. However, it’s really short and easy to remember, so there’s no excuse for not having opacity affects / rollovers in IE!
And that’s it! Whatever you wanted to be transparent will also work in IE6+! Obviuosly, instead of “0.6″ you’d type in “60″ for the filter rule.
There are actually a bevy of cool features available via Microsoft’s filter rule… too bad it only applies to their browsers, selfish bastards. Here’s a great post containing a lot of CSS2+ matching rules to Microsoft’s filters.
So, until Microsoft buckles under the ease of Webkit, at least get your opacities to be cross browser compliant, people!
no responsesHonestly, it’s not that Microsoft makes IE. It’s just a shitty browser. Every rendition.
IE8 makes the furthest step away from mediocrity, but here are my major two gripes: No webkit support, meaning I still have to use a rounded corners plugin to get things done. And really – why have a compatibility mode? I don’t even test for IE8, I simple include a meta tag, which I’ll probably write about in a later post.
Anyways! It appears IE is dying, in small margins, but death is a slow process. Check out the article at CNet for more.
http://news.cnet.com/8301-30685_3-10388289-264.html
no responses