Not detecting a meta tag specifying content isn't the same as not
guessing right when no content type is specified (which is what that
bug is about). Unless the majority of problem sites specify a text
encoding that's not being picked up--which is doubtfull--a fix for
whatever issue Adam is seeing won't solve the problem in general.
-Stuart
On Sep 24, 2004, at 7:43 AM, Bruce Davidson wrote:
Adam,
Hrm, there appears to be a bug with Camino here, because that page
should work with the encoding that was specified in their <meta> tag,
yet instead it doesn't seem to select any encoding from the text
encoding menu. Here is their <meta> tag:
Hmmm... perhaps you could attach this information to bug 248304
(https://bugzilla.mozilla.org/show_bug.cgi?id=248304), as it might be
useful. For we UK users it would be really good to get some traction
on this bug, its infuriating to have to remember to switch character
encodings every time you think "that price can't be right..." on a
site. Worse, less experienced users might get completely confused and
give up on the browser.
Do we need people to start posting a list of sites to this bug,
attaching their HTTP headers and HTML <head> section so that we can
determine what the overall problem is?
Cheers,
-Bruce
--
Bruce Davidson
_______________________________________________
Camino mailing list
[EMAIL PROTECTED]
http://mozdev.org/mailman/listinfo/camino
_______________________________________________
Camino mailing list
[EMAIL PROTECTED]
http://mozdev.org/mailman/listinfo/camino
