Closed Bug 21376 Opened 25 years ago Closed 25 years ago

command dispatcher not hooked up to html content

Categories

(Core :: XUL, defect, P3)

Product:
Core
Component:
XUL
Platform:
x86
Windows NT
Type:
defect

Tracking

()

Status:
VERIFIED DUPLICATE of bug 20471

People

(Reporter: buster, Assigned: hyatt)

References

Details

(Whiteboard: Awaiting saari's command dispatcher move.) 

2)<textarea> and <input> controllers are still not getting hooked up to the
command dispatcher.  Waterson had a plan for doing this.
Assignee: waterson → hyatt
i disown all command dispatching.
Status: NEW → ASSIGNED
Blocks: 21378
Whiteboard: needs triage by hyatt or saari.
cc saari.  one of you guys needs to triage this.
Target Milestone: M13
This has to be rethought.  The command dispatcher, being part of the chrome,
cannot be directly exposed to HTML content.
cc: self, since command updating in editor is also impacted.
Target Milestone: M13 → M14
Need to push this off to M14, since I'm waiting on other command dispatcher work
to be finished.
Whiteboard: needs triage by hyatt or saari. → Awaiting saari's command dispatcher move.
Dup of 20471.


*** This bug has been marked as a duplicate of 20471 ***
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
VERIFIED dupe
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.