| 00:42 | <Kaiido> | That would be super old, but it was indeed discussed back when svg:video was proposed: https://lists.w3.org/Archives/Public/www-svg/2003May/0005.html |
| 05:28 | <annevk> | Lea Verou: not sure, but HTML should probably define some of it eventually. |
| 14:40 | <annevk> | Meghan Denny: thanks for dealing with the spam! |
| 14:43 | <annevk> | Luke Warlow: did you consider giving ReflectEnum all the values needed instead? ReflectEnum=(enumToUse, "anonymous", "anonymous", null) or some such (probably incorrect example). |
| 14:48 | <Luke Warlow> | Hmm I hadn't actually, would require slightly funky grammar but that's not insurmountable. Could also just have multiple extended attributes but still put those on the idl attribute. Problem then is you duplicate the values between usages of the same enum (fetch priority, cross origin) |
| 14:49 | <annevk> | Oh yeah, hmm. |
| 14:50 | <annevk> | Okay, so turning an enum into not-quite-an-enum still looks like the best course of action. |
| 14:57 | <Luke Warlow> | The grammar to annotate the enum values is a trivial change (updated my parser easily enough), so provided we can work the prose out I think that design is probably best |
| 15:06 | <annevk> | Luke Warlow: I thought you determined that didn't make much sense? Or is the idea that we either annotate a value or annotate the enum? And when we annotate the enum it signifies null or some such? |
| 15:09 | <Luke Warlow> | Luke Warlow: I thought you determined that didn't make much sense? Or is the idea that we either annotate a value or annotate the enum? And when we annotate the enum it signifies null or some such? |
| 15:11 | <Luke Warlow> | Perhaps my current syntax is what ends up being optimal but if we want the other one it is doable |
| 15:20 | <annevk> | Looking at this again "no state" seems weird. I wonder if we can get rid of that eventually. But ignoring that, putting it always on the enum is probably the least confusing, even if it's a tad more verbose. |
| 15:22 | <annevk> | And I guess they can always take a string that is either one of the enum values or a new state that cannot be expressed as keyword. |
| 15:23 | <annevk> | Lol, we also have an actual "No state" (it's different). |
| 15:24 | <annevk> | The as attribute does indeed use the "no state", but could also have used a "Default state" or some such and branched on that. |
| 15:24 | <annevk> | And the as attribute might be the only attribute that builds on that oddity? Seems ripe for removal. |
| 19:56 | <Meghan Denny> | np! happy to help out where i can :) |