Limitations of CSS Files in IE

If you didn\’t know already, IE puts a limit on stylesheet file sizes to cap off at 288Kb. Another limitation I learned from Martin Ivanov\’s post is that IE limits the number of stylesheets loaded via link tag or @import to 32 files.

Make use of compression and minification if you\’ve got large files and lots of \’em. Besides, your styles should be reusable so you won\’t have gigantic files.

Dustin Diaz on DocTypes

I just had to share this one with you as soon as I read it. Dustin Diaz shows us a way of declaring a doctype, that puts the browser is standards mode. Thought it won\’t validate, which he explains:

There is really, absolutely no reason you need the rest of the doctype in your declaration unless you’re validating code. Furthermore, it does not mean that your page is even invalid. In the end, it puts your webpages into standards mode, which is what really matters.

Continue reading Dustin Diaz on DocTypes

Clientcide: New Form Validators and Documented Beta Code

Aaron Newton has released some new form validators (with help from contributor Chafik Barbar) and documentation for his beta code. Everyone has to deal with form validators one way or another. I\’ve posted on one from MooTools.Floor, but this is a different way of doing things. Continue reading Clientcide: New Form Validators and Documented Beta Code

Run Javascript Functions Without using \’domready\’ Event

I don\’t really like using the \’domready\’ event. The idea of adding another event to the window object just bugs me. So here\’s the alternative. In short, an array is created, functions you want to run are added to the array, and when the page reaches the bottom the functions in the array are run. Continue reading Run Javascript Functions Without using \’domready\’ Event

Don\’t Pollute the Global Space; Namespace It!

I like to namespace my code with object literals to contain all my functions and classes. It keeps things organized, decreases global space pollution from additional functions, and prevents conflicts with third-party scripts. It\’s very easy to extend too. Continue reading Don\’t Pollute the Global Space; Namespace It!

Jon Tan shows how to get @font-face to work on IE

If you\’ve designed a website or built one based off of a designer\’s vision, you\’ll understand the frustration when they don\’t want to use a common font and you have to explain why they should. There are a bunch of options of course, like sIFR and CSS image replacement. sIFR requires Flash and javascript, while CSS image replacement basically hides the text while an image with the text is placed in the background. Then there\’s the CSS @font-face construct which allows you to use an actual font file. There are two different implementations used between IE and the other popular browsers, and a whole mess about using licensed fonts. Jon Tan informs us by giving a brief background about using licensed fonts and clarifying how to use @font-face in IE. Be warned though; the implementation of using @font-face in IE requires IE conditional comments.

Thank you Jon, for such a great in-depth article. Really nice work.