egOrgSelector's notion of a change event is eccentric
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
New
|
Wishlist
|
Unassigned |
Bug Description
As a result of commit 354988bf from bug 1642378, an onchange handler associated with an egOrgSelector is also called when the egOrgSelector is initialized... which means that a handler expecting a _change_ of value won't do the right thing. One consequence of this is that one can't do this to allow using an egOrgSelector to mark a form as dirty:
<eg-org-selector onchange=
It would be helpful if we could fix this so that onchange has more typical semantics (e.g., https:/
Evergreen master
Changed in evergreen: | |
milestone: | none → 3.0-alpha |
tags: | added: webstaffclient |
Changed in evergreen: | |
milestone: | 3.0-beta → 3.next |
importance: | Undecided → Wishlist |
tags: |
added: angular removed: webstaffclient |
Changed in evergreen: | |
milestone: | 3.next → none |
Should a sticky value, applied at page load time, fire the on-change?