Closed Bug 16400 Opened 25 years ago Closed 24 years ago

Read-only page source and page DOM in editor.

Categories

(Core :: DOM: Editor, enhancement, P3)

Product:
Core
Component:
DOM: Editor
Type:
enhancement

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: CodeMachine, Assigned: cmanske)

Details

Now that the new tabbed modes are here, it'd be really nice to use them.  The
page source editor (bug #14526) and the page dom editor (bug #14527) are not
going to appear any time soon, but it would be great to have read-only versions
of these as an "editing" modes.  View source should be particularly easy to hook
up as such.
Assignee: buster → cmanske
reassign to cmanske@netscape.com for consideration/scheduling
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
If we add those other modes, of course I will add a tab to access them.
We don't need another bug for that

*** This bug has been marked as a duplicate of 14526 ***
Status: RESOLVED → VERIFIED
verified in 10/14 build.
Erm, this was asking for read-only versions only.  Bug #14526 is about an
editor.
Status: VERIFIED → REOPENED
Yea, you're right, the read-only version should be considered separately.
Status: REOPENED → ASSIGNED
Target Milestone: M15
Resolution: DUPLICATE → ---
The DOM part of this might be dependant on bug #14968.  This links to bug
#12111, which is to make the browser move towards modes similar to the tabbed
modes of the editor (which might involve a similar sort of architecture
code-wise).
We will implement a tag editor and edit source in M16 as 'tabbed' modes,
but this still might be a good idea to do. DOM source might be a good thing
to put in sidebar.
Target Milestone: M15 → M17
We have decided to use the HTML Source editor to display source. This solves
the problem that the read-only "View | Page Source" used by the browser 
gets content from the URL, which won't work for the editor (we must use 
currently-edited content). 
The "Show All Tags" mode is a new tag-based editor that fullfils the DOM editor
request. A hierarchical DOM tree might be a nice enhancement in a future
version -- puttin that in the sidebar would be a good idea. Please submit
a new enhancement bug if that feature is desired.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 24 years ago
Resolution: --- → FIXED
verified in 5/17 build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.