| 04:19 | <caitp|away> | and for that matter, why is it referencing [[Class]] |
| 06:21 | <annevk> | mounir: am now |
| 06:22 | <annevk> | caitp: https://www.w3.org/Bugs/Public/show_bug.cgi?id=28389 |
| 06:24 | <annevk> | jgraham: in IDL you could use sequence<Element> |
| 06:24 | <annevk> | jgraham: however, if you do things at the ES-level you need to handle all of them, though you could still use the iterator protocol I suppose, but just gets a little wordier |
| 06:25 | <annevk> | (and harder) |
| 08:21 | <tobie> | I'm trying to help people visualize different proposals for the generic sensor api and I'm not too sure how to go about it. |
| 08:22 | <tobie> | Examples help, but don't really give an idea of how the different pieces fit together. |
| 08:22 | <tobie> | I was wondering if UML-ish class diagrams would help, and if so, if they were some good tools to turn WebIDL into such diagrams. |
| 11:11 | <Ms2ger> | assert_equals(window.matchMedia('(device-aspect-ratio: 1280/800)').matches, true, "Expected value for device-aspect-ratio is 1280/800"); |
| 11:11 | <Ms2ger> | What? Why? |