This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8361 - Dropping the noscript element from XHTML is problematic. E.g., in the provided example, the calculate button cannot be removed before it the browser displays it, causing a graphical glitch, whitch can be quite large depending on the size of the alterative
Summary: Dropping the noscript element from XHTML is problematic. E.g., in the provide...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-24 11:15 UTC by contributor
Modified: 2010-10-04 14:33 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2009-11-24 11:15:19 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#the-noscript-element

Comment:
Dropping the noscript element from XHTML is problematic. E.g., in the provided example, the calculate button cannot be removed before it the browser displays it, causing a graphical glitch, whitch can be quite large depending on the size of the alterative content, and even loading overhead if it contains references to external files (images, inline frames, etc.). However, this glitch does not occur if the noscript element is used. You cal yourself the Web Hypertext Applications Technology WG, so I assume you don't like such glitches either. No alternative solutions are available to solve the glitch, so re-allow noscript in XHTML for convenient loading of scripted pages both with script support enabled and disabled.

Posted from: 145.94.18.52
Comment 1 Ian 'Hixie' Hickson 2010-01-05 10:53:54 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: You can easily avoid the flicker: wrap a <div> around the fallback, and put a script immediately inside the fallback that hides it straight away. That way the fallback never renders in script-enabled UAs.