27780 2015-01-07 15:06:15 +0000 [Custom]: "All Algorithms in One Diagram" 2015-07-06 08:16:04 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC All RESOLVED MOVED P2 normal --- 14968 1 annevk dglazkov mike public-webapps public-webapps-bugzilla oldest_to_newest 116891 0 annevk 2015-01-07 15:06:15 +0000 Per this diagram the prototype is changed after any callbacks are invoked but that is wrong per the prose. 116936 1 dglazkov 2015-01-08 19:19:14 +0000 Is this diagram useful, btw? I can't decide. My hesitation to remove it may be colored by hours I spent hand-coding it :P 116949 2 annevk 2015-01-09 06:57:26 +0000 I would love more diagrams in specifications and once I find a sensible way to generate them I would include them elsewhere too. It helps a lot with checking the overall flow or interdependencies. 116976 3 mike 2015-01-09 20:25:41 +0000 (In reply to Dimitri Glazkov from comment #1) > Is this diagram useful, btw? I can't decide. My hesitation to remove it may > be colored by hours I spent hand-coding it :P (In reply to Anne from comment #2) > I would love more diagrams in specifications Agreed with Anne here. I think in general spec readers/reviewers/implementors really appreciate and benefit from good diagrams, so trying to provide good ones is a great goal. (And I think diagrams are one of those things that users of the spec often end up just taking for granted when they have them; it's one of those many things that reviewers don't take time to make positive comments about. Instead, you're only going to hear from them when there's something wrong in the diagram. That suggests that if you want to measure whether a diagram is being used, you should put some easter-eggish error into it to see how many people notice and comment...) 121741 4 hayato 2015-07-06 08:16:04 +0000 Moved to https://github.com/w3c/webcomponents/issues/158