22426 2013-06-23 13:14:05 +0000 [Custom]: attributeChangedCallback should provide name of the attribute 2013-07-19 23:11:26 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC Linux RESOLVED FIXED P2 normal --- 14968 1 dominicc dglazkov public-webapps-bugzilla oldest_to_newest 89729 0 dominicc 2013-06-23 13:14:05 +0000 "when the attribute is modified with setAttribute, setAttributeNS, removeAttribute, or removeAttributeNS methods of the custom element, as well as setting the value property of the custom element's attribute, the callback must be invoked immediately." I think remove (called on the attribute's value text node) this affects attribute values, (I *think*, but the spec is a little abstract.) Maybe others. In Blink textContent, appendChild, etc. affect attribute values. But apparently that is contrary to the DOM spec. 89843 1 dglazkov 2013-06-25 20:20:14 +0000 I am leaning toward explicitly defining callback-queue-draining points in the spec and using these points universally for all callbacks. My naive hypothesis is that if we do this right, then if setAttribute() invokes lifecycle callbacks, the only callbacks in the queue would be attributeChanged callback queued by this setAttribute. 89863 2 dominicc 2013-06-26 02:23:27 +0000 (In reply to comment #1) > I am leaning toward explicitly defining callback-queue-draining points in > the spec and using these points universally for all callbacks. I think this is a bad idea. I am explaining my view on bug 22459. I would love to know what rafaelw thinks about this. 90316 3 dominicc 2013-07-04 02:14:22 +0000 There is some discussion of attributes on https://www.w3.org/Bugs/Public/show_bug.cgi?id=22459#c10, #c11, #c12 that probably should be here. Basically--what is the type of attributeChanged? It looks like this pleases most people: callback void (DOMString name, DOMString? oldValue, DOMString? newValue) If an attribute is added, oldValue is null. If an attribute is removed, newValue is null. If an attribute is changed, the values of oldValue and newValue are the values of the attribute before and after the change (ie when the callback is queued. Because of callback delivery, what you get from getAttribute may be different.) 91030 4 dglazkov 2013-07-19 23:11:26 +0000 https://dvcs.w3.org/hg/webcomponents/rev/8d2ad875c8e6