Have View Source still available even when you have a helper app assigned for document source



Core Graveyard
View Source
16 years ago
8 years ago


(Reporter: Brian 'netdragon' Bober, Assigned: Brian 'netdragon' Bober)


Firefox Tracking Flags

(Not tracked)




16 years ago
Even if you assign a helper app to view source (bug 8589), I believe it would
still be of great necessity to be able to still access View Source in some way.
Maybe the menu system could be adjusted in a way to make both options available
at once. For instance:

View >
       Page >
               Source In Internal Viewer
               Source In External Viewer

Reasons for this aree:
- Multiple people using the same Mozilla application and might disagree on
whether to use a helper application
- People might not always want to use the helper app, yet still have the option
if necessary
- It would be low-cost feature to implement
- It would make more people happy than people it bothered
- Why not add more bloat to the menus? ;-)


16 years ago
Severity: normal → enhancement


16 years ago
OS: Linux → All
Hardware: PC → All

Comment 1

16 years ago
...And the same options in the context menu.
Source In Internal Viewer  could be View Source
Source In External Viewer  could be Edit Source

And, may be, there could be good if there were an option Edit Source With... also?

Comment 2

16 years ago
UI:D to get invalidated for useless UI
Assignee: doron → mpt
Component: ViewSource → User Interface Design
QA Contact: pmac → zach
This is a duplicate, by the way.
Whiteboard: DUPEME

Comment 4

15 years ago
seems to be a dupe of 151319, which is duped to 8589.  this isn't quite the same
though, as it requests UI to fiddle with how it works.

confirming, reassigning...
Assignee: mpt → netdemonz
Component: User Interface Design → ViewSource
Depends on: 8589
Ever confirmed: true
Whiteboard: DUPEME
Product: Browser → Seamonkey

Comment 5

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 6

8 years ago
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
Last Resolved: 8 years ago
Resolution: --- → EXPIRED


8 years ago
Component: View Source → View Source
Product: SeaMonkey → Core Graveyard
You need to log in before you can comment on or make changes to this bug.