Closed
Bug 993329
Opened 10 years ago
Closed 10 years ago
Remove inline event handlers in newTab.xul
Categories
(Firefox :: Tabbed Browser, defect)
Firefox
Tabbed Browser
Tracking
()
VERIFIED
FIXED
Firefox 31
People
(Reporter: ttaubert, Assigned: mzhilyaev)
References
(Blocks 1 open bug, )
Details
(Whiteboard: p=2 s=it-31c-30a-29b.2 [qa-])
Attachments
(1 file)
1.79 KB,
patch
|
adw
:
review+
|
Details | Diff | Splinter Review |
When landing bug 974745 we introduced inline event handlers to newTab.xul, which we really shouldn't use anymore because they're bad style. Please always use .addEventListener() etc. for event handling.
Flags: firefox-backlog?
Comment 1•10 years ago
|
||
I don't follow. By inline event handlers you mean addEventListener(event, event => {}); instead of addEventListener(event, this); ... handleEvent: function (event) {}? Why is that bad style? Re: always using .addEventListener() for event handling, what other than addEventListener do you use to handle events?
Updated•10 years ago
|
Flags: needinfo?(ttaubert)
Reporter | ||
Comment 2•10 years ago
|
||
No, I was talking about onclick="foo.bar()" or onsubmit="foo.baz()". Inline like in "inline styles", not sure if that's the correct term.
Flags: needinfo?(ttaubert)
Comment 3•10 years ago
|
||
Gotcha, thanks.
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → mzhilyaev
Updated•10 years ago
|
Flags: firefox-backlog? → firefox-backlog+
Updated•10 years ago
|
Whiteboard: p=2
Comment 4•10 years ago
|
||
Attachment #8405078 -
Flags: review?(adw)
Updated•10 years ago
|
Attachment #8405078 -
Flags: review?(adw) → review+
Comment 5•10 years ago
|
||
https://hg.mozilla.org/integration/fx-team/rev/040440348215 qa- for already covered by automated tests
Whiteboard: p=2 → p=2 s=it-31c-30a-29b.2 [qa-]
Updated•10 years ago
|
Status: NEW → ASSIGNED
Comment 6•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/040440348215
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 31
Updated•10 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•