want "Browse to" feature on context menu in Moz Composer (same as had in Nav4 Composer)

NEW
Unassigned

Status

SeaMonkey
Composer
P3
enhancement
17 years ago
9 years ago

People

(Reporter: Eric Krock, Unassigned)

Tracking

(Blocks: 1 bug, {polish})

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
When you're editing a page in Composer, it's convenient to be able to put the 
mouse cursor within a link and then choose Browse to from the context (right 
click popup) menu. Nav4 Composer had this feature. Moz Composer currently lacks 
it, and I would appreciate it if that feature could be restored when time 
allows. Marking 4xp.
(Reporter)

Updated

17 years ago
Keywords: 4xp

Comment 1

17 years ago
future
Priority: -- → P5
Target Milestone: --- → Future

Comment 2

17 years ago
-->cmanske
is this a dup?
Assignee: beppe → cmanske

Comment 3

17 years ago
Don't thinks so. I don't have it.

Comment 4

17 years ago
spam composer change
Component: Editor: Core → Editor: Composer

Comment 5

16 years ago
*** Bug 163017 has been marked as a duplicate of this bug. ***

Updated

16 years ago
Blocks: 163017

Updated

16 years ago
Keywords: nsbeta1, polish
Target Milestone: Future → ---

Comment 6

16 years ago
nsbeta1+
This is a big usability problem with composer right now.  I wish for this
feature (or at least SOME way of doing this) several times every day.
Keywords: nsbeta1 → nsbeta1+

Comment 7

15 years ago
Composer triage team: nsbeta1-
Keywords: nsbeta1+ → nsbeta1-
Product: Browser → Seamonkey
Assignee: cmanske → nobody
Priority: P5 → --
QA Contact: sujay → composer

Comment 8

9 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 9

9 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 10

9 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 11

9 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 12

9 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 13

9 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
(Reporter)

Comment 14

9 years ago
Wow, six entries in the bug comments for the mass change. ;-) This is a low-priority enhancement request. I think it would be a handy feature to use while editing documents for quick link checking, etc. so it's still worth tracking, so setting to NEW and P3 (not intimately aware of Seamonkey project priorities, but doubt this is a P1 or P2). I've confirmed the enhancement is not present in:

SeaMonkey 1.1.16
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.21) Gecko/20090402 SeaMonkey/1.1.16

I know that's not a nightly build, but I highly doubt that someone has implemented this enhancement request between 1.1.16 and the last nightly build, and I don't have the time to install a nightly build right now. In the unlikely event that they have, I apologize.
Status: UNCONFIRMED → NEW
Priority: -- → P3

Comment 15

9 years ago
(In reply to comment #14)
> I know that's not a nightly build, but I highly doubt that someone has
> implemented this enhancement request between 1.1.16 and the last nightly build

There are two or three years of fixes between the 1.1.x series and the 2.0b1pre nightly series we're running now. Fortunately or unfortunately, however you want to see it, Composer hasn't seen a lot of fixes, so this probably is still valid if someone cares about it - and you just have proven you do ;-)
You need to log in before you can comment on or make changes to this bug.