Users who Dugg This
Misko Georgievich Kissleezin
1 Followers
Ramil Alcibar
0 Followers
Closed AccountJun 12, 2006
Why do these CSS sites always look terrible?
jimb0Jun 12, 2006
This is good. A nice thing too see the future features all in one place without having to look around. I like the opacity setting, cool.
jinexileJun 12, 2006
You're wrong Podgey, there are plenty of -moz- styles that have been implimented in the spec, -moz-opacity is an example of one, Mozilla often impliments popular styles before a spec reaches recommendation status and for safety reasons they impliment it with the standard compliant method of prefixing them with a vendor tag in case the style doesn't make it to the final spec.
kazoom123Jun 15, 2006
lets hope it gets adopted quickly
v3xt0rJun 16, 2006
It's been 5 years, it ain't gonna happen! =/
joelmmccOct 23, 2006
Yeah, that CSS Zen Garden site (<a class="user" href="http://csszengarden.com)">http://csszengarden.com)</a> sure is ugly and unimpressive.
joelmmccOct 23, 2006
They’re not exclusive to Firefox. It’s just that the Gecko rendering engine has implemented more of them than other rendering engines (though Webkit [the engine for Safari 2+] is way up there as well) at this time.Do keep in mind the difference between a browser and a web rendering engine. A web browser is just the user interface wrapped around the rendering engine. Firefox, Netscape 7+, Camino (Mac OS X), and Seamonkey all have different interfaces and user capabilities, but they will all render web pages identically (within certain OS limits such as availability of fonts), because all of them use the Gecko rendering engine. Netscape 8 for Windows by itself, and Firefox for Windows with the IE Tab extension, will both let you toggle between two different rendering engines (Gecko and Trident, the WinIE engine [also used by NeoPlanet and similar browsers]) within a single tab, very handy for seeing how a site will look in both common engines. E-Mail programs also use these engines for rendering HTML E-Mail. Outlook and Outlook Express for Windows both use Trident, of course, while Thunderbird, Netscape 6 & 7 Messenger [mail], Seamonkey Mail, etc. use Gecko, and Mac OS X Mail uses Webkit.Other engines include Tasman (Mac IE and Entourage: Tasman 2 in Mac IE 5 was the first engine to achieve greater than 90% compatibility with CSS1, but has since fallen way behind, and even Microsoft no longer supports it except for its use in Entourage [the mini-Outlook in Office for Mac]), KHTML (Konquerer, which implements some CSS3 stuff that even Gecko doesn’t!), Presto (Opera), and iCab (iCab 3, a Mac browser and the first ACID2-compliant engine publically available, and also the only browser still supported for Mac OS Classic -- Safari 2 [or, rather Webkit] is the first major ACID2-compliant browser [rendering engine] from a major company, and Opera 9's Presto is the first [and so far only] ACID2-compliant engine available for Windows).To more fully illustrate: you can create a new blank worksheet in Microsoft Excel for Windows (any version) and turn it into a Web browser! All you have to do is insert the proper ActiveX control. Any Windows will have the Microsoft Web Browser control, which is the Trident engine, and if you have Firefox or other Gecko browser installed, the Gecko engine is likewise available as a control. You could even put both on the same spreadsheet! By adjusting parameters, you could disable portions of the user interface, and replace them with controls and cells on the spreadsheet itself: you could make a particular cell be the Location box, for instance, where you type the URL you want to browse to.The important thing here is that web developers need to stop thinking in terms of BROWSERS (such as detecting them) and instead think in terms of ENGINES. And, even more to the point, think in terms of engine CAPABILITIES. You need to use some W3C DOM in your JavaScript? Don’t detect the browser and compare against a list of browsers that you know support the W3C DOM. New W3C-compatible browsers will come out, and your code won’t support them. Instead, test for the actual ability to use the W3C DOM itself. Ditto for other capabilities.For CSS3 goodies using the experimental tags (“-moz-…” etc.), do feel free to use them, but only for eye candy ways that won’t adversely affect the actual functionality of your site for engines that don’t support them. And do try to support their effect on as many engines as possible. For instance, if you want a box to be 25% transparent (75% opaque), use code like this:opacity: 0.75; -moz-opacity: 0.75; -webkit-opacity: 0.75; filter: Alpha(opacity=75);This makes it work for CSS3-compliant engines [including Gecko 1.7+]; older Gecko; Webkit [Safari]; and Trident [Win IE 4 or later], respectively. But don’t rely on it if you need to read something through the transparent object, because you’d be shutting out users of web engines that can’t support it. Use it for decoration only.
knowlteyJun 4, 2008
That's actually how I do it. I write the main stylesheet in CSS3, there are only a handful of things you can't do yet, but for the majority CSS selectors and properties are either recognized by the browser or completely ignored. Then I feed out special stylesheets to various rendering engines for fixed, all CSS3 valid.
crossersJul 18, 2008
sweet! very useful information! I think it's quickly!<a class="user" href="http://www.shpe-sac.org">http://www.shpe-sac.org</a><a class="user" href="http://www.ocflex.com/">http://www.ocflex.com/</a> <a class="user" href="http://www.trgovinca.org">http://www.trgovinca.org</a><a class="user" href="http://www.chasr.org/">http://www.chasr.org/</a>
masskurecMar 4, 2009
hopefully it is working now<a class="user" href="http://xptweak.net">http://xptweak.net</a>
anibalw45Sep 6, 2011
this site looks nice and fresh...and the content its very well organized. CSS3 great features. another good site is http://abcdtips.com/ for css and web desing tips.