Closed Bug 71106 Opened 24 years ago Closed 23 years ago

[XUL Syntax] Change DOM "create" and "destroy" popup events and add new shown/hidden popup events

Categories

(Core :: XUL, defect)

x86
Other
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla0.9.4

People

(Reporter: hyatt, Assigned: hyatt)

References

Details

(Whiteboard: [xul1.0-layout-popup])

Attachments

(1 file)

The events for menu opening and closing are too generically named. They should be renamed to popupShowing and popupHiding. While I'm in here, the nsIDOMMenuLIstener file should be renamed to nsIDOMXULListener, and the associated event names should be cleaned up as well.
Blocks: 70753
Status: NEW → ASSIGNED
Whiteboard: [XUL1.0]
Target Milestone: --- → mozilla1.0
What's the rationale behind the change in name of the latter entity? You're going from "Menu" (very specific) to "XUL" (very general).
The menu listener contains all the XUL events. :) Go look at nsIDOMMenuListener.
This is a compliance issue for popups. Two new DOM events must also be added. This bug will cover both issues.
Summary: [XUL Syntax] Change DOM "create" and "destroy" events → [XUL Syntax] Change DOM "create" and "destroy" popup events and add new shown/hidden popup events
Whiteboard: [XUL1.0] → [xul1.0-layout-popup]
Target Milestone: mozilla1.0 → mozilla0.9.4
r=jag
Any reason to not make nsIDOMXULListener scriptable? And since it's named nsIDOMXUL... it should be moved into dom/public/idl/xul (if it's converted into XPIDL). Nits of the day, bad indentation at: +nsresult nsXBLXULHandler::PopupShown(nsIDOMEvent* aEvent) { - if (!mProtoHandler) + if (!mProtoHandler) return NS_ERROR_FAILURE; Same problem in nsXBLXULHandler::PopupHiding, nsXBLXULHandler::PopupHidden. Other than that, sr=jst
All of the DOM event listeners are grouped under coreEvents. None of them are scriptable. If we want to fix that, IMO, we should just do it for all the listeners at the same time, but it doesn't really matter, since you'd never use these classes in JS (you'd just hook up the functions using addEventListener). I also think the file is in the right place, since it is an event listener, and all other event listener files are in that directory.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Fixed.
Component: XP Toolkit/Widgets: Menus → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: