Closed
Bug 105749
Opened 24 years ago
Closed 15 years ago
window.open doesn't fill in location bar in new window
Categories
(SeaMonkey :: Location Bar, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: jruderman, Unassigned)
References
()
Details
If a window is opened by through javascript (window.open), the location bar is
blank until the URL starts to load. Note that the location bar *should* be
blank if the page opened '' or 'about:blank', or if the page didn't specify a
URL.
Testcase:
javascript:window.open('http://unreachable.host'); void 0
Updated•24 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P5
Target Milestone: --- → Future
| Reporter | ||
Comment 2•24 years ago
|
||
See also bug 88567, "target=_blank link doesn't fill in location bar in new
window."
Comment 3•22 years ago
|
||
This bug description is too specific.
"Not prefilling the location bar with the URI" is not specific to javascript,
but clicking on a link with a target (other than itself, thus pointing to
another/new window).
See the remarks in bug 209795, which I duped in favor of bug 88567.
Comment 4•22 years ago
|
||
*** Bug 214645 has been marked as a duplicate of this bug. ***
Blocks: 222975
| Assignee | ||
Updated•17 years ago
|
Product: Core → SeaMonkey
Updated•17 years ago
|
Assignee: hewitt → nobody
Status: ASSIGNED → NEW
Priority: P5 → --
QA Contact: claudius → location-bar
Target Milestone: Future → ---
Comment 5•16 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Comment 6•16 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Comment 7•15 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.
Because of this, we're resolving the bug as EXPIRED.
If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.
Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•