Closed Bug 91779 Opened 23 years ago Closed 17 years ago

about: do not work if javascript is disabled, about:plugins is fixed

Categories

(Core :: Security: CAPS, defect)

Product:
Core
Component:
Security: CAPS
Type:
defect
Priority:
Not set
Severity:
minor

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: sakari, Assigned: dveditz)

References

(
URL
)

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:0.9.2+) Gecko/20010720
BuildID:    2001072008

about:plugins is empty if JavaScript is disabled. I see that
the about:plugins page uses javascript to display available plugins,
but shouldn't this work even if javascript is disabled.

Reproducible: Always
Steps to Reproduce:
1. Go to Edit/Preferences/Advanced and disable javascript
2. Go to Help/About Plug-ins
3. 

Actual Results:  Mozilla displayed an empty page.

Expected Results:  Display the list of available plugins.

I have currently only the null plugin and flash 5 plugin installed
in the the mozilla/plugins directory. The correct .class file for
flash is installed too.
This is not a bug. It is not supposed to work without JavaScript. It likely 
falls into category of desired feature, but I don't know, many things will not 
work without JavaScript, this is just one of them. Marking invalid, but if 
somebody feels different please reopen.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
reopening.  This may be a low priority, but it's a valid request.  The reasoning
is in bug 65378 -- "The reason for browsing with Javascript off (IMHO) is to
avoid the more obnoxious features of some webpages; it shouldn't have the
side-effect of crippling part of the user interface."

It's possible for parts of the browser to turn on javascript for themselves. 
There was a bug to turn it on for PSM (bug 65378), so it must be possible
somehow.  Also, chrome:// urls work with JS even when JS is off...

about:plugins could do that if it has the necessary permissions.
Status: RESOLVED → UNCONFIRMED
Keywords: mozilla1.1
OS: Linux → All
Hardware: PC → All
Resolution: INVALID → ---
Status: UNCONFIRMED → NEW
Ever confirmed: true
bbaetz pointed out to me that this broke after mstoltz's 7-20 checkin in bug 
88087 to make about: pages run without system principal.  Fixing this bug 
without reverting that checkin might depend on bug 86932, allowing (hidden) 
prefs to specify that specific sites can or cannot run javascript.
I'll take this. about: pages are no longer privileged, so they are subject to
the JS Enabled pref just like any other content page. I could change that.
Assignee: av → mstoltz
Component: Plug-ins → Security: CAPS
QA Contact: shrir → ckritzer
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.4
Target is now 0.9.4, Priority P2.
Priority: -- → P2
Moving to 0.9.5.
Target Milestone: mozilla0.9.4 → mozilla0.9.5
on a current linux cvs build about:plugins doesn't work at all - regardless of
js settings in prefs for the browser.
*** Bug 98169 has been marked as a duplicate of this bug. ***
about:plugins likewise doesn't work at all on a current Windows
build ( build ID 2001090408 ). View Source shows that all the
source is there, and JavaScript is enabled, but the plugin listing
doesn't show up.
about:plugins doesn't work here as well (Linux, build 2001090400),
with JavaScript turned on.

I just see a blank page, and this error message in the JavaScript console:

Error: bundle has no properties
Source File: jar:resource:///chrome/toolkit.jar!/content/global/plugins.html
Line: 84

about:plugins with JS enabled is an already fixed bug....
time marches on. Retargeting to 0.9.6.
Target Milestone: mozilla0.9.5 → mozilla0.9.6
Moving the most time-critical bugs and minor security fixes to 0.9.7
Target Milestone: mozilla0.9.6 → mozilla0.9.7
Very similar `bug': the about: page doesn't show the version number
if Javascript is disabled.

(Noticed in 0.9.5 and in 0.9.6
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.6) Gecko/20011120)
Target Milestone: mozilla0.9.7 → mozilla0.9.9
Mozilla1.0
Target Milestone: mozilla0.9.9 → mozilla1.0
Perhaps Mozilla could at least display a message (inside a <noscript> tag) that
the user must enable Javascript to properly view the page.  This would at least
alleviate a bit of user confusion until this is properly fixed.
Moving Netscape owned 0.9.9 and 1.0 bugs that don't have an nsbeta1, nsbeta1+,
topembed, topembed+, Mozilla0.9.9+ or Mozilla1.0+ keyword.  Please send any
questions or feedback about this to adt@netscape.com.  You can search for
"Moving bugs not scheduled for a project" to quickly delete this bugmail.
Target Milestone: mozilla1.0 → mozilla1.2
*** Bug 132880 has been marked as a duplicate of this bug. ***
mstoltz if you don't want this, then please reassign this to someone to implement a <noscript> band aid for 1.0
Keywords: mozilla1.1 → helpwanted, mozilla1.0
Target Milestone: mozilla1.2alpha → ---
*** Bug 179090 has been marked as a duplicate of this bug. ***
Adjusting summary to reflect dupes.

Even if this is not completely fixed, it should be not too difficult to include
some noscript element which warns that this does not work without javascript. So
people at least know what the problem is. A white page or missing information is
not helpful.

pi
Summary: about:plugins does not work if javascript is disabled → about:plugins and about: do not work if javascript is disabled
QA Contact: ckritzer → bsharma
*** Bug 170851 has been marked as a duplicate of this bug. ***
*** Bug 207801 has been marked as a duplicate of this bug. ***
"I'll take this. about: pages are no longer privileged, so they are subject to
the JS Enabled pref just like any other content page. I could change that."

This sounds like something simple that could be addressed quickly. Would that be
possible? Since this preference:
user_pref("javascript.enabled", false); 

overrides all capability.policy prefs, including
capability.policy.default.javascript.enabled, for all sites, it's impossible to
even set this on a single site basis in the preferences. 

http://www.mozilla.org/projects/security/components/ConfigPolicy.html
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6) Gecko/20040113

 Further to Comment #14: Not only is the version number omitted from
the 'about:' page if Javascript is disabled, the user agent string 
is also absent.

 To state the obvious: if you know the user-agent string should be 
there, not finding it on the 'about:' page is confusing.
Depends on: 236839
On Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040514

The about:plugins link works with JavaScript disabled.  I would consider this
aspect of this bug fixed.  Perhaps is it a fix for bug #186490 or for another
dependency that fixed the problem?
both about: and about:plugins were fixed for 1.3

marking WFM
Status: ASSIGNED → RESOLVED
Closed: 23 years ago → 20 years ago
Resolution: --- → WORKSFORME
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6) Gecko/20040113

about:plugins WFM

about: still broken. It doesn't show the version number (1.6) or the 
user-agent string (above) when javascript is disabled.

Right, about: still does not work. Changing summary.

pi
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Summary: about:plugins and about: do not work if javascript is disabled → about: does not work if javascript is disabled
Warning: Rantings about BTS practices first - actual bug report at end. 

1) Don't mark a bug "WFM" and "Resolved" because it was "fixed for 1.3". There
are bug reports post 1.3 that show that this was not "fixed for 1.3". Why not
take a minute to test the bug in a current release to see if it is actually
fixed? Regressions and bad patches happen and while I don't know what the
problem is in this case, it's still not working. 

2) Don't change summaries of bugs mid-stream unless the original summary was
totally off-base or misleading. Doing so makes it confusing for those of us
tracking bugs or searching for bugs. By changing the summary to remove the text
about "about:plugins", you've removed a way for someone to check to see when and
how this bug was resolved for "about:plugins". Please return the summary to its
 original form. These probably should have been separate bugs in the first place
but now is not the time to change the summary.  

Thank you!

About: does not display the version string with Javascript disabled in Mozilla
1.7 RC2 on Windows 2000. 

About:plugins works with Javascript disabled in Mozilla 1.7 RC2 on Windows 2000. 
Per the sugestions in comment 30 undoing bug 'morphing'

Returned summary to original summary from when the bug was first filed. 

Resloving worksforme because I and several other reporters can view
about:plugins with javascript disabled Mozilla/5.0 (Windows; U; Windows NT 5.1;
en-US; rv:1.8a) Gecko/20040517

Bug 199263 Is open for the about: problem. "Mozilla Version Info missing from
'Help->About Mozilla' Page ( about: ), if Javascript is disabled
Status: REOPENED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → WORKSFORME
Summary: about: does not work if javascript is disabled → about:plugins does not work if javascript is disabled
 Kevin, the following bugs which solely report the Javascript problem with
the about: page have been marked as duplicates of this bug: Bug 98169,
Bug 132880, Bug 179090, Bug 207801. Leaving Bug 199263 open for the about: 
problem with Javascript renders all of the comments in those other bugs 
nonsense.

 May I ask that you please (1) restore the summary to its pre-comment #29 
state and (2) mark Bug 199263 as a duplicate of this bug, consistent with 
previous practice?

Sorry for the bug spam. I did not realize that other bugs that are the same as
199263 were duped to this bug.
URL: about:plugins → about:
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Summary: about:plugins does not work if javascript is disabled → about: do not work if javascript is disabled, about:plugins is fixed
*** Bug 199263 has been marked as a duplicate of this bug. ***
Can someone test and see if this works in current trunk/branch builds? I think this should work now...
Assignee: security-bugs → dveditz
Status: REOPENED → NEW
Keywords: helpwanted
Priority: P2 → --
QA Contact: bsharma → caps
about: and about:plugins work for me on K/Ubuntu 6.10 with Firefox 2.0.0.2
Resolving WFM. Doesn't look like anyone can reproduce this problem now.
Status: NEW → RESOLVED
Closed: 20 years ago → 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.