[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

http://www.w3.org/Bugs/Public/show_bug.cgi?id=8361


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX




--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-01-05 10:53:54 ---
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.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Tuesday, 5 January 2010 10:53:55 UTC