Closed Bug 815 Opened 26 years ago Closed 26 years ago

We shouldn't process content inside <NOSCRIPT> tags

Categories

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

Product:
Core
Component:
DOM: HTML Parser
Platform:
All
Windows NT
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: joki, Assigned: rickg)

Details

Currently we're processing content inside NOSCRIPT tags.  This problem is most
visible on various Netcenter pages, the first of which being the sign in page.
The sign in page uses a meta-redirect inside a NOSCRIPT tag to avoid non script
browsers.  We need to get this fixed if we want to be able to test Netcenter in
NGLayout.
Status: NEW → ASSIGNED
Severity: normal → major
Priority: P2 → P1
Upping priority/severity - this bug prevents users from browsing netcenter.

A quick fix is to ignore anything inside noscript. In the future, we'll need to
be able to query libprefs for the value of the javascript.enabled pref and
conditionally process content inside the noscript tags.
This is a stop-ship bug. It prevents users from logging into Netcenter.
Summary: We shouldn't process content inside <NOSCRIPT> tags → STOP SHIP: We shouldn't process content inside <NOSCRIPT> tags
Putting STOP SHIP in Summary to assist with bug prioritization.
Adding myself to the cc: list.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
This is NOT a bug. Content inside noscript tags should in fact be stored in the
content model. The only problem (only slightly related) was that <meta> tag
content inside the <noscript> section was being processed into the open head.
I've stopped doing that, so this bug report has value anyway.
Summary: STOP SHIP: We shouldn't process content inside <NOSCRIPT> tags → We shouldn't process content inside <NOSCRIPT> tags
Removing STOP SHIP in Summary.  joki, could you please Verify with next build.
Thanks!
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.