Modal windows could be opened only with chrome

RESOLVED EXPIRED

Status

()

--
major
RESOLVED EXPIRED
15 years ago
13 years ago

People

(Reporter: tt, Assigned: dveditz)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; pl-PL; rv:1.7) Gecko/20040702
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; pl-PL; rv:1.7) Gecko/20040702

The following code should open modal window if the javascript is signed and the
user grants proper priviledge. But it doesn't work:
----------------
netscape.security.PrivilegeManager.enablePrivilege("UniversalXPConnect");
window.open("modaltest.html","test","chrome, centerscreen, dependent,
dialog, modal, alwaysRaised");
----------------


Reproducible: Always
Steps to Reproduce:
1. prepare test javascript with above code
2. sign it with proper certificate
3. launch it from HTTP server.
4. grant priviledge

Actual Results:  
the opened window won't be modal

Expected Results:  
open modal window
(Reporter)

Comment 1

15 years ago
I'm adding CC to danm.moz@gmail.com(hint from Boris Zbarsky ;) )
I couln't reassign this bug because it is UNCONFIRMED yet.

Comment 2

15 years ago
*** Bug 255354 has been marked as a duplicate of this bug. ***

Comment 3

15 years ago
Does it work if you ask for UniversalBrowserWrite instead?

note that even if i were to confirm this bug you still wouldn't be able to
reassign the bug to someone else.

While people who write code expect UBR to be implied by UBW and UBW to be
implied by UXPC, i can find no evidence of code which enforces this behavior.

http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/embedding/components/windowwatcher/src/nsWindowWatcher.cpp&rev=1.91&mark=1308-1311,1317-1321,1327#1308
Assignee: jag → dveditz
Component: XP Toolkit/Widgets → Security: CAPS
QA Contact: jrgmorrison
(Reporter)

Comment 4

15 years ago
(In reply to comment #3)
> Does it work if you ask for UniversalBrowserWrite instead?

Nope.
I even put all possible priviledges, and none of them helped.

netscape.security.PrivilegeManager.enablePrivilege("UniversalBrowserWrite");
netscape.security.PrivilegeManager.enablePrivilege("UniversalBrowserRead");
netscape.security.PrivilegeManager.enablePrivilege("UniversalXPConnect");

At first I contacted Borys Zbarski via e-mail, and he suggested to reassign this
bug to danm.moz@gmail.com.  He also mentioned:
"I just checked the code in Mozilla, and we only allow
chrome:// to open modal windows, not anything with universal priveleges.
That's probably a bug;"
Severity: normal → enhancement
(Reporter)

Comment 5

15 years ago
restored previous severity (unproper value was obviously caused by mouse
operator failure :))
now it will be correct(i hope).
Severity: enhancement → major

Comment 6

15 years ago
Try it without spaces in the features string.

Comment 7

15 years ago
Re: previous comment: I forgot, we strip spaces out of the features string
ourselves.

Modal windows can be opened from normal, unprivileged content loaded using the
file: protocol, with (temporary) UniversalBrowserWrite privileges. The same goes
for http: content if the signed.applets.codebase_principal_support pref is true.
I thought trusted signed content would work without any extra hurdles. We could
use the opinion of someone who knows what they're doing and is set up for
testing with the whole cert thing on this and bug 249038.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.