Closed Bug 66305 Opened 24 years ago Closed 22 years ago

[embed] eliminate XUL dependencies - command dispatching

Categories

(Core :: DOM: Editor, defect, P1)

Product:
Core
Component:
DOM: Editor
Type:
defect

Tracking

()

Status:
VERIFIED FIXED
Milestone:
mozilla1.2beta

People

(Reporter: rubydoo123, Assigned: Brade)

References

Details

(Keywords: embed, topembed-)

task: eliminate XUL dependencies - command dispatching
Blocks: 34477
Keywords: embed
Priority: -- → P1
Target Milestone: --- → mozilla0.9
Filed bug 74927 on the command params mechanism
Status: NEW → ASSIGNED
Depends on: 74927
-> 0.9.1
Target Milestone: mozilla0.9 → mozilla0.9.1
Blocks: 77421
move 9.2
Target Milestone: mozilla0.9.1 → mozilla0.9.2
-> mozilla 1.0
Target Milestone: mozilla0.9.2 → mozilla1.0
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 (you can query for this string to delete spam or retrieve the list of bugs I've moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
don't move bugs that are in the 1.0 dependency tree. sorry.
Target Milestone: mozilla1.0.1 → mozilla1.0
-> mjudge
Assignee: sfraser → mjudge
Status: ASSIGNED → NEW
Keywords: topembed
Keywords: mozilla1.0+
removing myself from the cc list
Target Milestone: mozilla1.0 → mozilla1.0.1
minusing to topembed- as per edt triage. not related to a particular embedding customer.
Keywords: topembed → topembed-
Keywords: mozilla1.0+ → mozilla1.0-
Blocks: edembed
To be clear, this bug is for eliminating the XUL dependencies in the Composer app, and not XUL dependencies for a 3rd party embeddor, correct?
core prerequisite for many things including bug 66296. I believe we need this to get composer itself to use the embedded editor code.
Status: NEW → ASSIGNED
-->brade
Assignee: mjudge → brade
Status: ASSIGNED → NEW
OS: Windows 98 → All
Target Milestone: mozilla1.0.1 → mozilla1.2beta
this was fixed with a checkin from a week ago or so
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
rs vrfy.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.