Default link target should be most recently used browser

RESOLVED WONTFIX

Status

SeaMonkey
Sidebar
RESOLVED WONTFIX
18 years ago
7 years ago

People

(Reporter: Steve Lamm, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
Currently, sidebar content developers have to set the default link target to 
"_content". Otherwise, link will replace the sidebar content. The default should 
be to load in the main browser window or the most recently used browser. 

Once this new default is used, content developers can use the "_self" target to 
replace the sidebar content if they want.
(Reporter)

Updated

18 years ago
Status: NEW → ASSIGNED
Depends on: 27161
Target Milestone: M14

Comment 1

18 years ago
I think this bug needs to get fixed now that 27161 has been fixed, since you 
still have to set target= "_content" so marking beta1
Keywords: beta1

Comment 2

18 years ago
PDT need more info on how this affects the end user please.  Does this affect 
3rd party ability to add contect to the sidebar?
Whiteboard: [NEED INFO]

Comment 3

18 years ago
PDT-
Whiteboard: [NEED INFO] → [PDT-]

Comment 4

17 years ago
Move to M16 ...
Target Milestone: M14 → M16

Comment 5

17 years ago
spam: changing qa contact on sidebar bugs from paulmac to shrir@netscape.com 
(all 67 of them!)
QA Contact: paulmac → shrir

Updated

17 years ago
Target Milestone: M16 → M17

Comment 6

17 years ago
Move to M20 target milestone.
Target Milestone: M17 → M20

Comment 7

17 years ago
Reassigning 50 Sidebar bugs to Matt.  I was told this was going to be done 
shortly about two months ago, but it clearly hasn't been.  I think that's long 
enough for all these bugs to remain assigned to nobody.

Feel free to filter all this spam into the trashcan by looking for this string 
in the message body: ducksgoquack
Assignee: slamm → matt
Status: ASSIGNED → NEW

Comment 8

17 years ago
ns6 has been out for a while.. probably too late to change this.
Keywords: beta1 → nsbeta1

Updated

17 years ago
Target Milestone: --- → mozilla0.9

Updated

17 years ago
Whiteboard: [PDT-] → [PDT-][nsbeta1+]

Updated

17 years ago
Priority: P3 → P4
Target Milestone: mozilla0.9 → Future
descheduling this from matt's 0.9 plate. lowering priority and moving to 
mfuture. doing this to make room for 55052 new on the nsbeta1 list. 

Comment 10

17 years ago
spam : changing qa to sujay (New Sidebar QA)
QA Contact: shrir → sujay

Comment 11

16 years ago
Nominating for mozilla0.9.  This is important if users are going to be able to 
add arbitrary pages as sidebar tabs (bug 50063).

Disagreeing with what I said a few months ago: fixing this bug probably won't 
break a lot of existing sidebars, since not many sidebars try to load 
additional content in the sidebar after the user clicks on a link.

See also bug 50748, "mail sidebar links open a NEW browser window EVERY time".
Keywords: mozilla0.9
nav triage: in fact, we should be careful about changing the default behaviour, 
because there may be tabs out there that assume that no target => the target is 
self. we probably should just keep this behaviour in the interests of backward 
compatibility. matt, do you think we should WONTFIX the bug? 
Keywords: nsbeta1 → nsbeta1-
Whiteboard: [PDT-][nsbeta1+]

Comment 13

16 years ago
This bug indirectly caused bug 65625, "Edit button in Sidebar 'Stocks' tab does 
not work", which is nsbeta1+.  (There is a workaround for that problem, but it 
took three months to figure out what the problem was.)

Comment 14

16 years ago
-> default owner
Assignee: matt → sgehani

Comment 15

14 years ago
Will there be any anniversary on the 9th? :)
Product: Browser → Seamonkey
Assignee: samir_bugzilla → nobody
Priority: P4 → --
QA Contact: sujay → sidebar
Target Milestone: Future → ---

Comment 16

8 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 17

8 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 18

8 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 19

8 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 20

8 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 21

8 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 22

8 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 23

7 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
Last Resolved: 7 years ago
Resolution: --- → EXPIRED
Not changing the default behaviour after over ten years without any striking reasons.
Resolution: EXPIRED → WONTFIX
You need to log in before you can comment on or make changes to this bug.