Bug Tracker

Changes between Initial Version and Version 1 of Ticket #6911, comment 23


Ignore:
Timestamp:
Feb 18, 2011, 12:44:12 PM (8 years ago)
Author:
danheberden
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6911, comment 23

    initial v1  
    1 While at first glance "currentTarget" sounds like a reasonable fix, it isn't.
    2 
    3 The firing event is still the element that is NOT disabled. So this fix would involve checking every click events parents for an element that's disabled. That isn't reasonable, as you can imagine.
    4 
    5 So while we can easily check if event.target.disabled, checking the parent just in case isn't as easy. I mean easy as in not penalizing non-disabled actions with a crap load of work.
    6 
    7 In this context, if you plan on attaching to elements that might be children of disabled elements then by all means, place that check in your own code.
     1actually, just might got it fixed