Closed Bug 274088 Opened 19 years ago Closed 14 years ago

alwaysRaised/alwaysLowered window.open feature incorrectly disallowed to content script

Categories

(Core :: DOM: Core & HTML, defect)

Product:
Core
Component:
DOM: Core & HTML
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla1.9.3a1

People

(Reporter: danm.moz, Assigned: wesongathedeveloper)

References

Details

(Whiteboard: [good first bug])

Attachments

(2 files)

testcase
340 bytes, text/html
Details
Patch
1018 bytes, patch
neil
: review+
Details | Diff | Splinter Review 
Content script isn't allowed to use the window.open("", "", "alwaysRaised")
feature even with expanded privileges.
Attached file testcase — 
If the user allows the expanded privileges requested by the script in this
testcase, one of the protected window.open features (titlebar) is accepted, but
the other (alwaysRaised) is not. (Note that, last I checked, this testcase
proves nothing on *nix builds, which don't support top-level window z-level at
all.)
Oops. Yeah, the testcase doesn't work when served via HTTP. To test, you'll have
to download it and run it off a local drive or set
signed.applets.codebase_principal_support true.
Whiteboard: [good first bug]
Blocks: 195867
Assignee: general → nobody
QA Contact: ian → general
Attached patch Patch — — Splinter Review 
Assignee: nobody → wesongathedeveloper
Status: NEW → ASSIGNED

        Attachment #411879 -
        Flags: review?(neil)

    
    

    
  
Comment on attachment 411879 [details] [diff] [review]
Patch

As per bug 42557 comment #15 ;-)

        Attachment #411879 -
        Flags: review?(neil) → review+

    
  
Keywords: checkin-needed

    
    

    
  
Shouldn't this be testable?
Flags: in-testsuite?

    
    

    
  
http://hg.mozilla.org/mozilla-central/rev/3c96b7a35fa7
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9.3a1
Flags: in-testsuite?

          You need to log in
          before you can comment on or make changes to this bug.