This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Plugin portal does not work when JavaScript turned off | ||
---|---|---|---|
Product: | updatecenters | Reporter: | Andrei Badea <abadea> |
Component: | Pluginportal | Assignee: | Maksim Khramov <mkhramov> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | ||
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
Andrei Badea
2007-03-02 15:22:36 UTC
Unfortunately many of the components currently used from Visual Web Pack uses javascript. Since not relying on javascript was not an initial requirement, I'm changing this to an enhancement. If I understand correctly we are early in the process still, so please consider updating the requirements. If you look at http://www.eclipse-plugins.info/ you will see they don't require JavaScript (at least not for navigating a link, that is). Why should our portal? David, until this is fixed, can you add <noscript> tags? > David, until this is fixed, can you add <noscript> tags?
Unfortunately I can not. The Javascript support is built into the components
used so this would have to be done by the component authors.
You can put a <noscript> element anywhere in the document. It doesn't have to be tied to the input fields which use JavaScript. Something like: <script type="text/javascript">var dummy;</script> <noscript>The plugin portal requires JavaScript</noscript> The <script> element is there because the HTML 4.01 spec says the contents of the <noscript> element should be rendered if a scripting language used earlier in the document is not supported: http://www.w3.org/TR/html401/interact/scripts.html#h-18.3.1 You can probably skip it if you have another <script> element before the <noscript> one. As Plugin Portal JSF site completly replaced I mark this issue as WNF... |