- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 24 Nov 2009 11:15:20 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8361
Summary: 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
Product: HTML WG
Version: unspecified
Platform: Other
URL: http://www.whatwg.org/specs/web-apps/current-work/#the-
noscript-element
OS/Version: other
Status: NEW
Severity: normal
Priority: P3
Component: HTML5 spec bugs
AssignedTo: dave.null@w3.org
ReportedBy: contributor@whatwg.org
QAContact: public-html-bugzilla@w3.org
CC: ian@hixie.ch, mike@w3.org, public-html@w3.org
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
--
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, 24 November 2009 11:15:29 UTC