More forgiving Content-Type header processing

RESOLVED INVALID

Status

()

Core
HTML: Parser
RESOLVED INVALID
16 years ago
16 years ago

People

(Reporter: Ilya Konstantinov, Assigned: harishd)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
Many webmasters frequently make the mistake of specifying the page encoding with:
<meta http-equiv="Content-Type" content="text/html"; charset="ISO-8859-8"> and
similiar.
(Probably thinking charset is an attribute of the META tag)

We should either make it more forgiving, atleast in Quirks mode, 
or leave all those cases to evanglizing.

Comment 1

16 years ago
Marking INVALID if you have more specific examples lets use those but this bug
is just way to vague to be useful.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → INVALID
(Reporter)

Comment 2

16 years ago
I can think of a dozen Israeli sites which specify an encoding in an incorrect
fashion. Especially widespread is the opinion that "charset" is an attribute of
the META tag. Thus, the following mistakes are widespread:

<meta http-equiv="Content-Type" content="text/html"; charset="ISO-8859-8">
<meta http-equiv="Content-Type" content="text/html" charset="ISO-8859-8">
<meta HTTP-EQUIV="Content-Type" content="text/html" charset="iso-8859-8-i" ;>
<meta charset="ISO-8859-8">
<meta charset="Visual"> <!-- BiDi MSIE 3-introduced equivalent to ISO-8859-8 -->
<meta charset="Logical"> <!-- BiDi MSIE 3-introduced equivalent to ISO-8859-8-I
or maybe Windows-1255 - not sure -->
<meta http-equiv="Content-Type" content="text/html" charset="visual">          
                               

...and other combinations of the above.

Those could be possibly cases for endless Evangelism, but wouldn't it be smarter
to support them ("don't be right, be smart"), atleast in Quirks mode?

Updated

16 years ago
QA Contact: bsharma → moied
You need to log in before you can comment on or make changes to this bug.