- From: <bugzilla@jessica.w3.org>
- Date: Sat, 20 Dec 2014 13:29:52 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20713
--- Comment #8 from Olli Pettay <bugs@pettay.fi> ---
(In reply to Anne from comment #7)
> (In reply to Philip Jägenstedt from comment #6)
> > Event.srcElement is around 20%:
> > https://www.chromestatus.com/metrics/feature/timeline/popularity/343
> >
> > It's just an alias of target, so adding that seems like the only way to go.
>
> This seems very similar to the isSameNode() situation as Mozilla never added
> it. If Mozilla wants to add this, we should probably define it, along with
> window.event as I believe they cannot be decoupled.
I haven't heard recently anyone asking us to add window.event or
Event.srcElement.
I'd expect adding window.event to actually break things (when using Gecko),
since at least at some point there were pages doing
if (window.event) {
// some more IE-style stuff
}
Not sure how blink copes with that.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Saturday, 20 December 2014 13:29:54 UTC