Keep running into issues where browser engineers write spec IDL that violates the IDL spec in whatever ways their binding implementation does not enforce. If we're lucky a second implementor, with a binding implementation with different holes, tries to implement before it ships
-
-
Oh, I see. Well, this IDL did get synced, and is invalid, and idlharness apparently did not complain. Off to file some bugs...
- End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.