Open Bug 785111 Opened 10 years ago Updated 4 years ago

Expose the origin of window.open caller via mozbrowseropenwindow

Categories

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

defect

Tracking

()

blocking-basecamp -

People

(Reporter: ferjm, Unassigned)

References

Details

As discussed in Bug 768943, we need to expose the origin of the window.open caller.
Blocks: browser-api
Summary: Expose the origin window.open caller → Expose the origin of window.open caller
Blocks: 768943
Can't you get the URI of the caller with window.opener?
(In reply to Mounir Lamouri (:mounir) from comment #1)
> Can't you get the URI of the caller with window.opener?

No. Sorry, I should have explained it properly. What we need is to expose the origin of the caller of window.open via 'mozbrowseropenwindow', so the Gaia system app can check if the caller application is certified or not. That's the use case that we've identified for bug 768943, but it could be extended to other use cases (like a popup blocker as Justin mentioned in https://bugzilla.mozilla.org/show_bug.cgi?id=768943).
Summary: Expose the origin of window.open caller → Expose the origin of window.open caller via mozbrowseropenwindow
(In reply to Fernando Jiménez Moreno [:ferjm] from comment #2)
>(like a popup blocker as Justin mentioned in
> https://bugzilla.mozilla.org/show_bug.cgi?id=768943).

I meant https://bugzilla.mozilla.org/show_bug.cgi?id=768943#c55
blocking-basecamp: --- → ?
Blocking a blocker so + ... unless of course this isn't the solution we go ahead with :)
blocking-basecamp: ? → +
Ben, can you be the owner here?
Assignee: nobody → ben
Justin says this is no longer needed.
blocking-basecamp: + → -
This doesn't need to be a blocker anymore, based on our approach in bug 768943 .
Assignee: ben → nobody
No longer blocks: 768943
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046

Move all DOM bugs that haven't been updated in more than 3 years and has no one currently assigned to P5.

If you have questions, please contact :mdaly.
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.