Changes between Initial Version and Version 1 of Ticket #17213, comment 18


Ignore:
Timestamp:
Apr 24, 2014, 8:48:43 AM (5 years ago)
Author:
bill
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #17213, comment 18

    initial v1  
    11I can see why you're disappointed, but it doesn't make sense to change this now, for two big reasons:
    22
    3 1. The only way to remove the auto-mapping yet maintain backwards compatibility is to add explicit custom setters to _WidgetBase for every existing DOM property (ex: draggable, value, min, max, etc.).   Then we basically end up in the same situation we're in now, where widget properties are unwantedly mapped to the DOM node.
     31. The only way to remove the auto-mapping yet maintain backwards compatibility is to add explicit custom setters to _WidgetBase for every existing DOM property / attribute (ex: draggable, value, min, max, aria-labelledby, aria-label, role, etc.).   Then we basically end up in the same situation we're in now, where widget properties are unwantedly mapped to the DOM node.
    44
    552. 2.0 will work the same way that dijit does now.  Since in 2.0 the Widget == the DOM node, setting a property on the widget is literally the same thing as setting a property on the DOM node, and therefore unfortunately named widget properties (ex: draggable) will run into trouble.