Status

--
enhancement
RESOLVED EXPIRED
19 years ago
8 years ago

People

(Reporter: CodeMachine, Unassigned)

Tracking

({helpwanted})

Trunk
helpwanted
Bug Flags:
blocking-seamonkey2.0.4 -
blocking-seamonkey2.0.5 -
blocking-seamonkey2.1a1 -

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
This is a request to add a page DOM editor to the editing modes of the
editor.  The UI of changing between modes was discussed in bug #11140.

The idea is that this editing view would work in the manner of a tree of tags
and attributes.  It is similar in idea to the new DOM viewer, and might leverage
the work done on it.

Ideally this editor could be initially designed at least to work with any XML in
preparation to having an arbitrary XML editor in Mozilla.
(Reporter)

Updated

19 years ago
Assignee: buster → nobody
(Reporter)

Comment 1

19 years ago
Reassigning to nobody and adding a possible interested party as per Mozillazine
comment.

Updated

19 years ago
Priority: P3 → P5
Target Milestone: M20
(Reporter)

Updated

19 years ago
Summary: Page DOM editor → [HELP WANTED]Page DOM editor
(Reporter)

Comment 2

19 years ago
Authoring Tool Accessibility Guidelines W3C Working Draft 3 September 1999
7.6 Enable editing of the structure of the document.
(Reporter)

Updated

19 years ago
Blocks: 16397

Updated

19 years ago
Keywords: helpwanted

Comment 3

19 years ago
Assigning all open "nobody@mozilla.org" bugs to "leger@netscape.com" to weed 
thru.
Assignee: nobody → leger

Updated

19 years ago
Summary: [HELP WANTED]Page DOM editor → Page DOM editor

Comment 4

19 years ago
Updating Assignee for this component.
Assignee: leger → beppe

Updated

19 years ago
Status: NEW → ASSIGNED

Comment 5

18 years ago
moving to future milestone
Target Milestone: M20 → Future

Comment 6

17 years ago
-->cmanske
Assignee: beppe → cmanske
Status: ASSIGNED → NEW

Comment 7

17 years ago
spam composer change
Component: Editor: Core → Editor: Composer
Product: Browser → Seamonkey
Assignee: cmanske → nobody
Priority: P5 → --
QA Contact: sujay → composer
Target Milestone: Future → ---

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

Comment 14

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

Updated

8 years ago
Flags: wanted1.8.1.x?
Flags: wanted-seamonkey2.1?
Flags: in-testsuite?
Flags: in-litmus?
Flags: blocking1.9.0.19?
Flags: blocking1.8.1.next?
Flags: blocking-seamonkey2.1a1?
Flags: blocking-seamonkey2.0.5?
Flags: blocking-seamonkey2.0.4?

Updated

8 years ago
Flags: wanted1.8.1.x?
Flags: wanted-seamonkey2.1?
Flags: in-testsuite?
Flags: in-litmus?
Flags: blocking1.9.0.19?
Flags: blocking1.8.1.next?
Flags: blocking-seamonkey2.1a1?
Flags: blocking-seamonkey2.1a1-
Flags: blocking-seamonkey2.0.5?
Flags: blocking-seamonkey2.0.5-
Flags: blocking-seamonkey2.0.4?
Flags: blocking-seamonkey2.0.4-

Comment 15

8 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: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.