Closed Bug 17409 Opened 25 years ago Closed 25 years ago

[perf] [dogfood] Order of 'http-equiv' and 'content' affects result

Categories

(Core :: DOM: HTML Parser, defect, P3)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: alistair.vining, Assigned: ftang)

Details

(Whiteboard: [PDT+] fix in local tree. Need review and M12 tree open)

Attachments

(1 file)

Sorry, crummy summary, but at present: <META content="text/html; charset=utf-8" http-equiv="Content-Type"> <META http-equiv="Content-Type" content="text/html; charset=utf-8"> have different results. With 'content' first, the <meta> tag has no effect in viewer.exe or mozilla.exe, although it does in View Source under viewer.
Assignee: rickg → ftang
Summary: Order of 'http-equiv' and 'content' affects result → [perf] [dogfood] Order of 'http-equiv' and 'content' affects result
Frank -- this problem appears to be in your metacharset observer code. I'd also like to discuss the implementation, which looks pretty inefficient. Given that we make this call for every tag, it's gotta be fixed.
Status: NEW → ASSIGNED
OS: Windows 95 → All
Hardware: PC → All
Target Milestone: M12
agree what rickg stated...
Whiteboard: [PDT+]
Putting on [PDT+] radar.
patch available at http://warp/u/ftang/tmp/meta17409.txt Wait till M12 open to check in. I will take out the #if else part 1 week after I check in for risk management....
Whiteboard: [PDT+] → [PDT+] fix in local tree. Need review and M12 tree open
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
fix check into M12 tip.
Status: RESOLVED → VERIFIED
seems to be fixed. Verified.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: