Note: This site might seem inactive… That’s because it is. Don’t worry though, I’m still coding webpages and stuff! If you’re interested, I suggest you get a translator and head over to Qiwi; or you could just check the latest site we’ve been working on: Apotheek Goethals – Debrabandere. Enjoy!
The basics of becoming a browser nazi
- Make proper use of web standards.
- Serve your files with the correct MIME type. Don’t worry about
application/javascriptandapplication/xhtml+xml. Don’t even consider using long-winded XHTML content negation scripts. - Use Apache’s excellent MultiViews, and never type extensions when linking to files on your server again.
- Use HTTP headers to link to stylesheets.
- Use
id="tags". - Use gzip compression for all text-based documents, such as whateverML, CSS, JS and plenty other documents.
Thank you.
Comments (9)
Listed below are the responses for this entry.
Trackbacks & Pingbacks (1)
Listed below are resources on the web that mention this article.
-
- Wasn das? oder: Wie man den IE abserviert » contactsheet.de:
[…] im Originalartikel heißt das “Linking to style sheets with HTTP headers” und ist auf der Demoseite in Aktion zu begutachten. Im IE funktioniert das nicht, was Mathias Bynens als die eigentliche Intention der Angelegenheit unter dem Motto […]
- Pingback made on August 23rd, 2006 @ 10:13 am
That’s some really good stuff. Yeah, I’m a perfectionista with leanings toward browser nazism. I wonder though, is your intention to break IE with
id="tags"?Oh yes. The whole above list is full of anti-shitbrowser stuff:
application/xhtml+xml(for XHTML) andapplication/javascript(for JS), which sometimes leads to extensive discussions as to which markup language is better. Which is kind of sad, obviously, since all that’s wrong is this one browser’s programming.Options +MultiViewsto your.htaccess, you don’t need to use file extensions anymore on your site… Unless you want it to work in IE, that is; on some occasions, that shadow of a browser returns 406 errors when trying to access such multiviewed files.idattribute with a value oftagsmay cause IE to crash.How Microsoft can just get away with all this is beyond me. IE7 better be good.
And for added fun, spread lists like these to increase browser nazism morale.
Very well listed.
Maybe we should develop a script that automatically downloads Firefox and crashes IE. ;)
hmmm
i guess i won’t ever be a browser nazi…got to fine tune my almost non-existent skills first
why are there no dates on your posts? is that a choice? or am i blind? blind! i see it!!!
While I agree that some degree of browser nazism is good, you should be careful not to break any standards-compliant web browsers. For example, using HTTP headers to link to stylesheets breaks Safari — even the latest CVS version.
Linking to stylesheet using HTTP headers has other drawbacks… suppose you download the HTML file and the CSS file to your hard disk; the link between both files will be gone and a lot of users will hate you.
I’m most likely taking this far too seriously. ;)
Oh, and using proper web standards doesn’t always break Internet Explorer. (I have my hopes up for IE7, by the way… so far it’s looking pretty good.)
IE is simply the best!
I can appreciate this sort of post, but I have to make sure there’s a level of sarcasm in it, because… the whole idea behind standardization is to improve usability/accessibility for both authors as — and especially — the end-users. Browser vendors and document authors both have a responsibility in implementing such standards, but they also have to help each other out where possible. Your dogmatic approach towards standards is like communism; it sounds nice in theory, but it doesn’t really work out well in practice. Purposely breaking a document for IE is essentially breaking the document for a broad range of people, rendering it ultimately unusable and inaccessible. This is in contrast with the philosophy (if you will) of standardization.
My 2 ct…
Those are new, interesting bugs to me.