sudo apt-get build-dep mozilla-firefox
cvs -d :pserver:anonymous:firstname.lastname@example.org:/cvsroot co mozilla
make -f client.mk build
First impression: fonts need work.
Does anyone know what the rationale for the change was?
Looking at the rewrite rules, it seems like the just do a regular expression match against the contents of the Accept header, checking to see if it contains “application/xhtml+xml”.
Regarding how such a request should be handled, if you have text/html and application/xhtml+xml representations of your document with equal fidelity it makes sense to give the browser whichever it prefers. However, if you’re using XHTML specific technologies such as a SVG, MathML, RDDL, etc then serving as application/xhtml+xml to any client which can accept it makes more sense. Of course, some agents include */* but can’t actually handle XHTML, complicating matters.
If Mozilla wants to avoid user complaints regarding the Yellow Screen of Death, switching to prefer text/html and thus the non-draconian parser is the way to go.
You’ve got a stray backslash there (in front of the zero), and the pattern doesn’t account for cases like 000., should they be permitted, or for additional whitespace separating the q value from the next MIME type or from end-of-line/-string.
I can’t find fault with Aristotle’s latest regex after 15 minutes of trying.
However, isn’t it beside the point, given the Accept header that Gran Paradiso is sending? The client is telling the server that it prefers text/html over application/xhtml+xml. Sam, I know your server is perfectly capable of sending text/html content. Why aren’t you doing so?
@Sam: But surely there are better ways to discriminate against IE users. Perhaps wrapping your Adsense code with conditional comments? Oh, the irony. (I acknowledge your longer answer, though.)
@Jacques: wow, filed and confirmed almost a year ago and still not a single reviewable patch. Well, lots of luck with that. I’ve seen the statistics on how many bugs get fixed after lingering for a year, and it ain’t pretty. If I were you, I’d start looking for an alternate browser sooner rather than later.
Heh. Hurry, find a new browser! Something that’s in its very first alpha doesn’t work right yet! It’s time to panic, it’s time to fear! I’m filled with uncertainty and doubt, because the total rewrite of the graphics layer, which is still broken in innumerable ways, is broken in that way too!