01:58 | <sideshowbarker> | Can anybody think of an existing implemented WebIDL interface that has no members? |
02:02 | <sideshowbarker> | I’m aware of the FragmentDirective interface from the scroll-to-text-fragment spec https://wicg.github.io/scroll-to-text-fragment/#feature-detectability and I’ve been trying to figure out how to implement it from the C++ side — and have been failing so far. So it would help if there were some existing no-members IDL interface that’s been implemented, and I could look at the corresponding C++ source. |
07:51 | <zcorpan> | sideshowbarker: HTMLUnknownElement (though it inherits from HTMLElement) |
07:56 | <zcorpan> | sideshowbarker: CDATASection |
07:58 | <sideshowbarker> | ah yeah I had looked at some corresponding C++ source for that, and in that case also, it inherits (from Text) |
07:59 | <sideshowbarker> | this FragmentDirective thing is a really odd case — an interface that exposes nothing, and inherits from nothing |
08:00 | <sideshowbarker> | apparently it only exists for the purpose of feature detection, and for possible future use for other things |
08:00 | <zcorpan> | sideshowbarker: https://www.w3.org/TR/media-source-2/#mediasourcehandle |
08:00 | sideshowbarker | looks |
08:01 | <zcorpan> | sideshowbarker: https://html.spec.whatwg.org/#workletglobalscope |
08:01 | <sideshowbarker> | hot diggity dog, that looks more like it |
08:02 | <zcorpan> | sideshowbarker: https://www.w3.org/TR/webnn/#api-mlgraph |
08:03 | <zcorpan> | sideshowbarker: https://registry.khronos.org/webgl/extensions/OES_texture_float/ |
08:04 | <zcorpan> | sideshowbarker: If you wonder how I found these, git grep "{\s*};" in wpt/interfaces :) |
08:06 | <sideshowbarker> | d’oh yeah I hadn’t thought to grep through those (instead just browser sources) |
15:47 | <sefeng> | annevk: I made some additional changes to the ORB PR to align with what Firefox has implemented. I'd like to close https://github.com/whatwg/fetch/pull/1442 and open a new one because I don't think I can push to annevk/orb directly , Is that ok? |
23:32 | <Eric Portis (he/him)> | Any examples of how specs turn floats into integers? I'm specifying a thing (https://github.com/WICG/responsive-image-client-hints/issues/34) where Chrome currently implements ceil(), though arguably the use case would be slightly better served by round(), although it doesn't really matter... mostly want to specify it in a precise way that isn't "do the equivalent of Javascript’s Math.ceil()" |