22942 2013-08-13 20:45:45 +0000 We should fire onopen and onclose when <details> is opened and closed. 2013-11-06 19:13:27 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#attr-details-open P3 normal Unsorted 1 contributor ian d ian mathias mike contributor oldest_to_newest 92007 0 contributor 2013-08-13 20:45:45 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/ Multipage: http://www.whatwg.org/C#attr-details-open Complete: http://www.whatwg.org/c#attr-details-open Referrer: http://xn--74h.damowmow.com/ Comment: We should fire onopen and onclose when <details> is opened and closed. Posted from: 2620:0:1000:167c:55e0:acbd:8909:3cd8 by ian@hixie.ch User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/30.0.1588.0 Safari/537.36 92998 1 d 2013-09-04 18:36:51 +0000 I don't have a strong opinion on this, but after consulting with a coworker he prefers one event instead of two. The rationale being that it's easier to bind to a single event with existing client-side frameworks (e.g. Backbone), and then use the boolean value it would give you to e.g. toggle classes: Backbone.View.extend({ events: { 'toggle details.my-details': function (ev) { this.$('.related-thing-to-toggle').toggleClass('active', ev.target.open); } } }); 92999 2 ian 2013-09-04 19:08:26 +0000 So a single event, but fire it after the state has changed. That makes sense. ontoggle="" is ok, but not ideal. Anyone got a better colour for this shed? 95876 3 ian 2013-11-06 18:11:43 +0000 I went with 'toggle' as suggested. Checked in as WHATWG revision r8251. Check-in comment: <details ontoggle=''> for when you open or close a <dialog>. http://html5.org/tools/web-apps-tracker?from=8250&to=8251 95878 4 contributor 2013-11-06 19:13:27 +0000 Checked in as WHATWG revision r8252. Check-in comment: ack for last checkin http://html5.org/tools/web-apps-tracker?from=8251&to=8252