[Webkit-unassigned] [Bug 10326] Charset auto-detection trumps document instructions when triggered before the content-type tag

[bugzilla-daemon at opendarwin.org]

http://bugzilla.opendarwin.org/show_bug.cgi?id=10326


ddkilzer at kilzer.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|419.x                       |418.x




------- Comment #7 from ddkilzer at kilzer.net  2006-08-10 08:29 PDT -------
(In reply to comment #6)
> Ah, ok, I wasn't sure how all of that worked.  I selected the build from the
> drop-down menu based on my Safari's About version number; my mistake for the
> confusion.

The About Safari numbers are actually Safari-only version and build numbers. 
You must use this secret decoder ring to map Safari version/build numbers to
WebKit build/version numbers:

http://developer.apple.com/internet/safari/uamatrix.html

> I'll go ahead and file a bug report over at apple.com, but I was
> under the impression that production versions of Safari eventually incorporate
> everything from the WebKit branch, so that this was the place to report it.

Yes, the source from the nightly WebKit builds will (in all likelihood) make it
into Leopard.  I didn't want to quash your bug-filing enthusiasm, though.  :) 
I wouldn't say it's pointless to file a Radar bug about this, either.  In my
opinion (which really doesn't count for much), it's not likely that it will get
fixed in Tiger unless Apple releases a version of Safari when Leopard is
released, similar to what happened with Panther (and Safari 1.3) with Tiger.


-- 
Configure bugmail: http://bugzilla.opendarwin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.