window targeting to _content does not always work.

VERIFIED FIXED in mozilla0.9.5

Status

()

Core
Document Navigation
VERIFIED FIXED
17 years ago
16 years ago

People

(Reporter: rpotts (gone), Assigned: rpotts (gone))

Tracking

Trunk
mozilla0.9.5
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: PDT+)

Attachments

(1 attachment)

(Assignee)

Description

17 years ago
XUL uses a special window target called "_content" as a means of targeting the
closest 'non-chrome' window.

It turns out that if no 'non-chrome' windows are available then the URI load
simply fails.  The correct behavior would be to open up a new browser window and
target its content area.
(Assignee)

Comment 1

17 years ago
Created attachment 48394 [details] [diff] [review]
patch to nsDocShell.cpp
(Assignee)

Comment 2

17 years ago
r=jst@netscape.com

(he really said so)

Comment 3

17 years ago
Comment on attachment 48394 [details] [diff] [review]
patch to nsDocShell.cpp

r=pavlov
Attachment #48394 - Flags: review+

Updated

17 years ago
Attachment #48394 - Flags: superreview+
(Assignee)

Comment 4

17 years ago
patch checked into the trunk.
Target Milestone: --- → mozilla0.9.4
(Assignee)

Comment 5

17 years ago
Nominating for PDT consideration...
Whiteboard: PDT

Updated

17 years ago
Keywords: nsbranch

Updated

17 years ago
Blocks: 99194

Comment 6

17 years ago
Marking as nsbranch+ to nominate to the PDT for a PDT+.
Keywords: nsbranch → nsbranch+

Comment 7

17 years ago
0.9.4 is out the door.
Target Milestone: mozilla0.9.4 → mozilla0.9.5

Comment 8

17 years ago
PDT+. Pls check it in by 3 am.
Whiteboard: PDT → PDT+
(Assignee)

Comment 9

17 years ago
the patch is now checked into the 0.9.4 branch.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED

Comment 10

16 years ago
mdunn - can you help to verify this?
QA Contact: adamlock → mdunn

Comment 11

16 years ago
Ashish Please verify as fixed
QA Contact: mdunn → ashishbhatt

Comment 12

16 years ago
Verified
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.