| 07:59 | <Domenic> | jyasskin: functions don't have relevant settings objects |
| 07:59 | <Domenic> | but in some loose sense, that's basically true |
| 08:00 | <Domenic> | (functions have [[Realm]] slots, which could be said to be their relevant realm if you wanted) |
| 14:03 | <zcorpan> | <link rel="icon" href="c:\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\fakepath\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\cupcakes.jpg" type="image/gif"/> |
| 14:05 | <MikeSmith> | 👍 |
| 14:11 | <annevk> | zcorpan: where was your utility to go from code point to longer name to put in a spec? |
| 14:12 | <zcorpan> | annevk: https://simon.html5.org/tools/js/unicodeize/ |
| 14:13 | <zcorpan> | annevk: there's also http://software.hixie.ch/utilities/cgi/unicode-decoder/character-identifier |
| 14:20 | <annevk> | zcorpan: thanks, trying to figure out a consistent style to use in Infra (and then everywhere else) |
| 14:20 | <annevk> | zcorpan: I think I'm going with U+xxxx NAME IF IT CANNOT BE RENDERED or U+xxxx (RENDERED) |
| 14:21 | <annevk> | that way it's both brief and clear |
| 14:22 | <zcorpan> | annevk: and if it's several characters, just "foobar" ? |
| 14:23 | <annevk> | zcorpan: yeah, we'll keep that for strings and byte sequences |
| 14:23 | <annevk> | zcorpan: we already do that all over actually |
| 14:23 | <zcorpan> | SGTM |
| 14:27 | <annevk> | Are there any standardized names for byte values? Just like we have them for code points? |
| 17:38 | <smaug> | it would be nice to have one code indexing tool for all the open source browser engines |
| 17:39 | smaug | would suggest tool similar to searchfox.org |
| 17:39 | <smaug> | such tool would help with reverse engineering and such |
| 17:42 | <annevk> | smaug: not exactly reverse engineering if you just look at the code |
| 17:42 | <smaug> | true |
| 17:42 | <annevk> | Chromium has such a tool as well |
| 17:42 | <smaug> | oh, sure |
| 17:42 | <annevk> | https://cs.chromium.org/ |
| 17:42 | <smaug> | but there are different tools |
| 17:43 | <smaug> | and certain tools a bit better than others ;) |
| 17:43 | <annevk> | and I guess WebKit has https://trac.webkit.org/ |
| 17:43 | <annevk> | Yeah |
| 17:43 | <smaug> | trac is horrible |
| 17:43 | <annevk> | I'm not a fan either |
| 17:43 | <annevk> | Someone could create a mashup I suppose |
| 18:02 | <wanderview> | smaug: we could always host webkit and chromium in our search tool... i think freebsd used to do this for the linux kernel |
| 18:03 | <smaug> | need to ask billm if that was doable |
| 18:03 | <wanderview> | ah, they still do: http://fxr.watson.org/fxr/source/?v=HEAD |
| 18:03 | <smaug> | we used to have webkit or blink in mxr |
| 18:03 | <wanderview> | maybe not updated |
| 19:28 | <smaug> | jgraham: hmm, wpt doesn't have a way to dispatch trusted key events, right? |
| 19:29 | <jgraham> | smaug: No :( |
| 19:29 | <jgraham> | smaug: We want that to happen but so far no one did the work |
| 19:29 | <smaug> | yeah, would be nice |
| 19:29 | <smaug> | but ok, mochitest it is then |
| 22:06 | <jyasskin> | smaug: https://github.com/w3c/testharness.js/issues/142 tracks user gestures, which Chrome uses trusted key events to implement. |
| 22:06 | <gsnedders> | I still feel like testharnessreport.js is the wrong place to put this |
| 22:07 | <smaug> | jyasskin: how does that help with dispatching UA initiated events? |
| 22:08 | <jyasskin> | smaug: If you really need the key events, it doesn't. On the other hand, if we had the key events, we could use them to fix #142. |
| 22:09 | <smaug> | yeah, that way it would work |
| 22:09 | <smaug> | one often needs UA initiated events |
| 22:09 | <smaug> | in tests |
| 22:09 | <gsnedders> | jyasskin: why doesn't it help with dispatching UA initiated events? |
| 22:09 | <gsnedders> | am I missing something obvious here? |
| 22:10 | <jyasskin> | gsnedders: If we fix #142 literally, "Add a user-gesture helper function", then you can't get an arbitrary UA-initiated event given just a function to enable the user-gesture bit. |
| 22:11 | <gsnedders> | jyasskin: oh, rihght |
| 22:12 | <jyasskin> | I definitely wouldn't object if #142 were dup'ed against a bug in the right repository to add full trusted event dispatch. |
| 22:16 | <gsnedders> | jyasskin: I think NavidZ is working on that, hence #250/251 |
| 22:16 | <jyasskin> | \o/ |