Closed
Bug 291725
Opened 20 years ago
Closed 19 years ago
Change NS_POPUP_EVENT to NS_POPUPBLOCKED_EVENT
Categories
(Core :: DOM: Events, defect, P2)
Core
DOM: Events
Tracking
()
RESOLVED
FIXED
mozilla1.8beta4
People
(Reporter: ilya.konstantinov+future, Assigned: dbaron)
References
Details
(Whiteboard: [patch])
Attachments
(1 file)
9.49 KB,
patch
|
jst
:
review+
bzbarsky
:
superreview+
benjamin
:
approval1.8b4+
|
Details | Diff | Splinter Review |
From a short LXR search, it looks like all popup blocked events are now
generated with mEvent->eventStructType == NS_POPUPBLOCKED_EVENT, so both
content/events/src/nsDOMUIEvent.cpp and
content/events/src/nsEventListenerManager.cpp should be changed not to refer to
NS_POPUP_EVENT anymore.
(I don't have a building Mozilla tree right now, so this bug is just for
reference and a reminder till I find time to post a tested patch.)
Comment 1•20 years ago
|
||
*** Bug 292543 has been marked as a duplicate of this bug. ***
Comment 2•20 years ago
|
||
We shouldn't ship 1.8 with this issue....
Note also that it looks like NS_POPUP_EVENT can be removed altogether.
Flags: blocking1.8b3?
Comment 3•20 years ago
|
||
Boris, does this really block the release?
Flags: blocking1.8b3?
Flags: blocking1.8b3-
Flags: blocking-aviary1.1?
Assignee | ||
Comment 4•20 years ago
|
||
I think so; it's a bunch of core regressions from a change we took in the 1.8
cycle that broke many things to do with popupblocked events and probably some to
do with popup events as well.
Updated•20 years ago
|
Flags: blocking1.8b4+
Flags: blocking-aviary1.1?
Flags: blocking-aviary1.1+
Comment 5•19 years ago
|
||
dbaron, would you be able to take a pass at resolving this?
/cb
Assignee: events → dbaron
Assignee | ||
Comment 6•19 years ago
|
||
OK, some notes, before I forget:
NS_POPUP_EVENT is for popupshowing, popupshown, popuphiding, and popuphidden.
This should be an nsDOMUIEvent. The group is "PopupEvents". See bug 112286 and
bug 133426 for some history.
NS_POPUPBLOCKED_EVENT is for DOMPopupBlocked. This should be an
nsPopupBlockedEvent. See bug 199705.
Assignee | ||
Comment 7•19 years ago
|
||
Sorry, the popup events should be nsDOMMouseEvent, since they have coordinates.
Assignee | ||
Comment 8•19 years ago
|
||
Currently untested.
The event code really needs to stop storing data in the form of code,
especially code spread out in many different places.
Assignee | ||
Comment 9•19 years ago
|
||
Comment on attachment 190781 [details] [diff] [review]
patch #1
Not really sure how to test this, but requesting reviews...
Attachment #190781 -
Flags: superreview?(bzbarsky)
Attachment #190781 -
Flags: review?(jst)
Comment 10•19 years ago
|
||
Comment on attachment 190781 [details] [diff] [review]
patch #1
I see what you mean about data in code... :(
Attachment #190781 -
Flags: superreview?(bzbarsky) → superreview+
Assignee | ||
Updated•19 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P2
Hardware: PC → All
Whiteboard: [patch]
Target Milestone: --- → mozilla1.8beta4
Comment 11•19 years ago
|
||
Comment on attachment 190781 [details] [diff] [review]
patch #1
r=jst
Attachment #190781 -
Flags: review?(jst) → review+
Assignee | ||
Updated•19 years ago
|
Attachment #190781 -
Flags: approval1.8b4?
Updated•19 years ago
|
Attachment #190781 -
Flags: approval1.8b4? → approval1.8b4+
Assignee | ||
Comment 12•19 years ago
|
||
Fix checked in to trunk, 2005-08-02 13:18/38 -0700.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•