Closed Bug 920377 Opened 12 years ago Closed 12 years ago

Get rid of legacy event class names (ns*Event)

Categories

(Core :: Widget, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla27

People

(Reporter: masayuki, Assigned: masayuki)

References

Details

Attachments

(33 files, 3 obsolete files)

12.45 KB, patch
roc
: review+
Details | Diff | Splinter Review
9.46 KB, patch
roc
: review+
Details | Diff | Splinter Review
12.90 KB, patch
roc
: review+
Details | Diff | Splinter Review
18.47 KB, patch
roc
: review+
Details | Diff | Splinter Review
9.84 KB, patch
roc
: review+
Details | Diff | Splinter Review
10.03 KB, patch
roc
: review+
Details | Diff | Splinter Review
13.70 KB, patch
roc
: review+
Details | Diff | Splinter Review
12.46 KB, patch
roc
: review+
Details | Diff | Splinter Review
6.79 KB, patch
roc
: review+
Details | Diff | Splinter Review
7.92 KB, patch
roc
: review+
Details | Diff | Splinter Review
6.75 KB, patch
roc
: review+
Details | Diff | Splinter Review
10.33 KB, patch
roc
: review+
Details | Diff | Splinter Review
60.81 KB, patch
roc
: review+
Details | Diff | Splinter Review
28.07 KB, patch
roc
: review+
Details | Diff | Splinter Review
12.04 KB, patch
roc
: review+
Details | Diff | Splinter Review
10.35 KB, patch
roc
: review+
Details | Diff | Splinter Review
100.99 KB, patch
roc
: review+
Details | Diff | Splinter Review
22.88 KB, patch
roc
: review+
Details | Diff | Splinter Review
2.67 KB, patch
roc
: review+
Details | Diff | Splinter Review
29.54 KB, patch
roc
: review+
Details | Diff | Splinter Review
32.46 KB, patch
roc
: review+
Details | Diff | Splinter Review
46.95 KB, patch
roc
: review+
Details | Diff | Splinter Review
58.15 KB, patch
roc
: review+
Details | Diff | Splinter Review
19.85 KB, patch
roc
: review+
Details | Diff | Splinter Review
10.29 KB, patch
roc
: review+
Details | Diff | Splinter Review
71.54 KB, patch
roc
: review+
Details | Diff | Splinter Review
18.01 KB, patch
roc
: review+
Details | Diff | Splinter Review
30.80 KB, patch
roc
: review+
Details | Diff | Splinter Review
9.73 KB, patch
roc
: review+
Details | Diff | Splinter Review
234.37 KB, patch
roc
: review+
Details | Diff | Splinter Review
157.00 KB, patch
roc
: review+
Details | Diff | Splinter Review
232.39 KB, patch
roc
: review+
Details | Diff | Splinter Review
60.80 KB, patch
roc
: review+
Details | Diff | Splinter Review
No description provided.
Assignee: nobody → masayuki
Status: NEW → ASSIGNED
Whiteboard: [leave open]
Attachment #809687 - Attachment is obsolete: true
Attachment #810478 - Flags: review?(roc)
Attachment #809717 - Attachment is obsolete: true
Attachment #810479 - Flags: review?(roc)
Attachment #810480 - Flags: review?(roc)
I'll create other patches...
Attachment #810492 - Flags: review?(roc)
Comment on attachment 810489 [details] [diff] [review] part.12 Get rid of nsScriptErrorEvent Review of attachment 810489 [details] [diff] [review]: ----------------------------------------------------------------- ::: dom/indexedDB/IDBRequest.cpp @@ +39,5 @@ > } // anonymous namespace > > USING_INDEXEDDB_NAMESPACE > using mozilla::dom::OwningIDBObjectStoreOrIDBIndexOrIDBCursor; > +using mozilla::InternalScriptErrorEvent; "using namespace mozilla;" instead.
Attachment #810489 - Flags: review?(roc) → review+
The name, nsQueryContentEventResult, is now strange, though.
Attachment #811606 - Flags: review?(roc)
roc: please ignore the new XXX comment. smaug: Could you check the XXX comment? If it's a bug or you have no idea for them for now, I'll file a bug for it. Otherwise, I'll remove the comment from this patch. According to the DOM Events spec, I think that the activate event should be dispatched as trusted event even if it's caused by an untrusted left click event. However, I'm not sure if DOMActivate is fired on other browsers too. If this is same behavior as other browsers, we shouldn't change it, though. Do you know this? If you don't know, I'll research other browsers' behavior.
Attachment #811611 - Flags: review?(roc)
Attachment #811611 - Flags: feedback?(bugs)
roc: Please ignore the new XXX comments. smaug: I found that some DOM event constructors don't use the most subclass for its argument. I think that we should change them with filing another bug. How about you?
Attachment #811612 - Flags: review?(roc)
Attachment #811612 - Flags: feedback?(bugs)
The remaining events are: nsEvent, nsGUIEvent, nsMouseEvent and mozilla::WheelEvent. The former 3 events are used in a lot of places, therefore, I'll land them separately later. If I rename mozilla::WheelEvent now, I'll break a patch which I'm reviewing. I'll work on this after the patch is landed (I hope it's soon).
Attachment #811615 - Flags: review?(roc)
/home/markus/mozilla-central/widget/gtk/nsDragService.cpp:1581:37: error: member access into incomplete type 'nsIContent' nsIFrame* frame = mDragPopup->GetPrimaryFrame(); ^ /home/markus/mozilla-central/widget/gtk/../xpwidgets/nsBaseDragService.h:22:7: note: forward declaration of 'nsIContent' class nsIContent; ^
diff --git a/widget/gtk/nsDragService.cpp b/widget/gtk/nsDragService.cpp index b00b79e033ea..423dd09ca3e3 100644 --- a/widget/gtk/nsDragService.cpp +++ b/widget/gtk/nsDragService.cpp @@ -34,6 +34,8 @@ #include "nsViewManager.h" #include "nsIFrame.h" #include "nsGtkUtils.h" +#include "nsIContent.h" + // This sets how opaque the drag image is #define DRAG_IMAGE_ALPHA_LEVEL 0.5
(In reply to Octoploid from comment #42) > /home/markus/mozilla-central/widget/gtk/nsDragService.cpp:1581:37: error: > member access into incomplete type 'nsIContent' > nsIFrame* frame = mDragPopup->GetPrimaryFrame(); > ^ > /home/markus/mozilla-central/widget/gtk/../xpwidgets/nsBaseDragService.h:22: > 7: note: forward declaration of 'nsIContent' > class nsIContent; > ^ What's your environment? No environments in tinderbox don't fail to build it.
(In reply to Masayuki Nakano (:masayuki) (Mozilla Japan) from comment #45) > (In reply to Octoploid from comment #42) > > /home/markus/mozilla-central/widget/gtk/nsDragService.cpp:1581:37: error: > > member access into incomplete type 'nsIContent' > > nsIFrame* frame = mDragPopup->GetPrimaryFrame(); > > ^ > > /home/markus/mozilla-central/widget/gtk/../xpwidgets/nsBaseDragService.h:22: > > 7: note: forward declaration of 'nsIContent' > > class nsIContent; > > ^ > > What's your environment? No environments in tinderbox don't fail to build it. Linux x86_64, clang trunk.
Whiteboard: [leave open]
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla27
Attachment #811611 - Flags: feedback?(bugs)
Comment on attachment 811612 [details] [diff] [review] part.26 Get rid of nsInputEvent This all has landed. Not sure feedback is needed.
Attachment #811612 - Flags: feedback?(bugs)
(In reply to Masayuki Nakano (:masayuki) (Mozilla Japan) from comment #32) > Created attachment 811612 [details] [diff] [review] > smaug: I found that some DOM event constructors don't use the most subclass > for its argument. I think that we should change them with filing another > bug. How about you? Sounds good.
(In reply to Masayuki Nakano (:masayuki) (Mozilla Japan) from comment #31) > smaug: Could you check the XXX comment? If it's a bug or you have no idea > for them for now, I'll file a bug for it. Otherwise, I'll remove the comment > from this patch. File a bug. Not sure what behavior we want there. > However, I'm not sure if DOMActivate is fired on other browsers too. If this > is same behavior as other browsers, we shouldn't change it, though. Do you > know this? If you don't know, I'll research other browsers' behavior. DOMActivate is a legacy thing from old versions of DOM Events spec. No browser has supported it properly. We should try to remove it at some point (but first warn about us of it).
(In reply to Olli Pettay [:smaug] from comment #52) > (In reply to Masayuki Nakano (:masayuki) (Mozilla Japan) from comment #32) > > Created attachment 811612 [details] [diff] [review] > > smaug: I found that some DOM event constructors don't use the most subclass > > for its argument. I think that we should change them with filing another > > bug. How about you? > Sounds good. I did it at bug 920425 :-) (In reply to Olli Pettay [:smaug] from comment #53) > (In reply to Masayuki Nakano (:masayuki) (Mozilla Japan) from comment #31) > > > smaug: Could you check the XXX comment? If it's a bug or you have no idea > > for them for now, I'll file a bug for it. Otherwise, I'll remove the comment > > from this patch. > File a bug. Not sure what behavior we want there. Bug 930843 > > However, I'm not sure if DOMActivate is fired on other browsers too. If this > > is same behavior as other browsers, we shouldn't change it, though. Do you > > know this? If you don't know, I'll research other browsers' behavior. > DOMActivate is a legacy thing from old versions of DOM Events spec. > No browser has supported it properly. We should try to remove it at some > point > (but first warn about us of it). Hmm, I'm afraid to remove it... Especially, I think that this event doesn't harm performance.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: