| 00:00 | <tobie> | annevk: We could tweak the UI to make that clearer. |
| 00:00 | <tobie> | annevk: LMK |
| 00:01 | <tobie> | smaug____: internal slots proposal ^ |
| 04:33 | <annevk> | SimonSapin: did you see http://ucsx.org/? |
| 04:33 | <SimonSapin> | annevk: I did |
| 04:35 | <SimonSapin> | annevk: I think it’s interesting as "solving a math problem". For character encodings though: I’m not convinced we’re gonna need to go beyond U+10FFFF or a very long time 2. if we do, we should pick one extension not 9 |
| 04:35 | <SimonSapin> | for* a very long time |
| 04:35 | <annevk> | Yeah |
| 04:35 | <SimonSapin> | (I want to say "ever", but this kind of prediction tends to be wrong) |
| 04:36 | <annevk> | Gonna need something bigger than a couple emoji each year |
| 04:39 | <othermaciej_> | lol, UCS-∞ |
| 04:58 | <SimonSapin> | the most code-space-consuming thing I imaging we might want to do (regardless of how feasible it is now) is undoing Han unification, but even that is like 3× it most? |
| 04:58 | <SimonSapin> | and Unicode 10.0 is at ~8% |
| 05:03 | <SimonSapin> | also interesting that in 16-bit variants, UCSX encodes new values as sequences that are unpaired surrogates in UTF-16, so it’s unclear how that would work in WTF-16 systems like JS |
| 05:14 | <annevk> | JS would need a new string type basically |
| 05:22 | <othermaciej_> | maybe the new string type could be one of the UTF-8 based variants, then |
| 14:35 | <tobie> | This is probably a question I should have the answer to, but where do I find how the object that implements an interface with the [Global] extended attribute is initialized? |
| 14:37 | <tobie> | Does it simply follow the |steps| defined in the algorithm in https://heycam.github.io/webidl/#interface-object ? |
| 14:39 | <tobie> | I'm trying to ES-ify the exposition of attributes, constants and operations (see: https://pr-preview.s3.amazonaws.com/tobie/webidl/pull/494.html#es-constants). |
| 14:41 | <tobie> | And I'm having trouble with how to expose those "on the single object that implements the interface, when an interface is declared with the [Global] extended attribute." |
| 14:41 | <tobie> | Domenic, annevk: ^ |
| 15:25 | <Ms2ger> | tobie, do you have any algorithm for creating platform objects? |
| 15:27 | <tobie> | Ms2ger: yes, |steps| in the algorithm found in https://heycam.github.io/webidl/#interface-object is the closest I can think of. |
| 15:28 | <Ms2ger> | No, that's the interface objects |
| 15:29 | <Ms2ger> | I think it makes most sense to have an algoritm to create instances, and then define the constants and whatever there, depending on its interface being marked with [Global] |
| 15:32 | <tobie> | Ms2ger: I;m talking about the value of the steps variable within that algorithm |
| 15:33 | <Ms2ger> | Oh, you're right |
| 15:34 | <tobie> | Ms2ger: maybe it should be it's own algorithm. |
| 15:34 | <tobie> | :D |
| 15:34 | <tobie> | its |
| 15:35 | <Ms2ger> | Or in https://heycam.github.io/webidl/#es-interface ... But you have to make sure that you don't create multiple JS objects for one IDL object... |
| 15:35 | <Ms2ger> | Not sure |
| 16:09 | <annevk> | FYI: https://blog.whatwg.org/working-mode-changes |
| 16:12 | <nox> | PogChamp |
| 16:35 | <gsnedders> | annevk: Wow. There's a part of me amazed it's finally happened. |
| 16:38 | <wanderview> | annevk++ |
| 17:02 | <Domenic> | The real question is which of our fine individual contributors is going to be the first to sign the new agreement thingy. (And hopefully not break my code.) |
| 17:03 | <annevk> | Sounds like a challenge |
| 17:29 | <Domenic> | I wonder if anyone even realizes that the blog has a comments feature anymore. |
| 17:34 | <annevk> | Domenic: there was a spammy comment I trashed (since not sure if actually spam) |
| 17:37 | <Domenic> | We have a winner! domfarolino in https://github.com/whatwg/participant-data/commit/c3e0d4f4d6d1bbddd406f5ddb8b29928a0ab46ab . Nothing seems to have broken! |
| 17:37 | <gsnedders> | Domenic: Can I do a Philip`? |
| 17:38 | <gsnedders> | (i.e., try obscure Unicode characters likely to break things) |
| 17:38 | <Domenic> | gsnedders: hmm, since clearing crap from the database is a bit annoying, let me set up a staging server/data repo for that first. I need to do that anyway to test any changes. |
| 17:41 | <gsnedders> | Domenic: I was (mostly) joking. |
| 17:41 | <gsnedders> | I tend not to do such things with legal forms |
| 17:42 | <Domenic> | It's a good idea though. |
| 18:17 | <domfarolino> | Domenic: \o/ |
| 18:29 | <domfarolino> | Domenic: annevk: So if I understand this correctly, only the Work Stream editors (editors officially approved/appointed by SG) appear in the WorkStream.md file in whatwg/sg (and are responsible for all Living Standards in a Work Stream), and deputy editors and other contributors to Living Standards appear in the ACKs of said standards? |
| 18:31 | <Domenic> | domfarolino: that's the idea. Workstream Editors are the ones "on the hook" for any process. Whereas there can be many editors or deputy editors or whatever for a given standard. |
| 18:31 | <Domenic> | Workstream Editor is mostly a service role, not necessarily "senior" or "most involved" or anything. |
| 18:34 | <wanderview> | after today's announcement, does anything change with how html spec is being edited in both whatwg and w3c? I've seen some tweet that maybe it has, but it seems like its up to w3c to make that decision |
| 18:35 | <domfarolino> | Domenic: Excellent thanks! |
| 18:35 | <annevk> | wanderview: yeah, that'd be up to the W3C |
| 18:36 | <annevk> | wanderview: though I suspect browsers have less incentive to contribute there now |
| 18:37 | <wanderview> | annevk: I was just curious because of discussion at TPAC about moving workers back into w3c html and w3c html spec getting a new editor |
| 19:16 | <annevk> | kochi: happy to move to two days if that's better for the F2F |
| 19:16 | <annevk> | kochi: I suspect I'll be around for a few more days though to make it worth the length of the trip |
| 19:35 | <Domenic> | tobie: I think those are the steps for now. The last paragraph of https://github.com/heycam/webidl/issues/467 seems relevant too. |
| 19:40 | <tobie> | Domenic: basically I need a hook to define props directly on the instance for [Global] and unforgeable. |
| 19:40 | <Domenic> | tobie: I see. For [Unforgeable] I guess it's part of "create an X object" which is still undefined |
| 19:41 | <Domenic> | For globals maybe we need a separate algorithm for creating the global instances, yeah. |
| 19:41 | <Domenic> | Seems OK to leave those imprecise with a big TODO/warning in the spec that they are not in the imperative algorithm yet, just to chunk up the work. |
| 19:43 | <annevk> | Oooh, we're gonna define allocating objects? Yay |
| 19:43 | <Domenic> | It's always been the plan |
| 19:44 | <annevk> | Now I remember why I wanted typed slots |
| 19:44 | <annevk> | So that when you allocate a Document, IDL could take of allocating the DOMImplementation object |
| 19:44 | <annevk> | take care* |
| 19:44 | <annevk> | And also take care of the global for that and such |
| 19:45 | <annevk> | Basically for any kind of tear-off setup it's nice when IDL can take over stuff |
| 19:45 | <annevk> | But maybe we should just have something dedicated for that |
| 19:45 | <tobie> | As a matter of fact, slots "allocation" also needs to happen somewhere there |
| 19:46 | <annevk> | Yeah that's nice, that way you can't change slots later on |
| 19:46 | <annevk> | (you can still change their values of course) |
| 19:46 | <annevk> | (but not the object layout) |
| 19:46 | <TabAtkins> | Domenic: Y'all are gonna want some boilerplate changes for WHATWG stuff, yeah? |
| 19:47 | <annevk> | TabAtkins: aye, though it need not be completed today and I think mostly depends on us doing some work |
| 19:48 | <TabAtkins> | I can at least get y'all's copyright in order, I guess. |
| 19:48 | <annevk> | TabAtkins: well, even that we manage manually today |
| 19:48 | <annevk> | TabAtkins: so would have to be paired with changes against all standards using Bikeshed |
| 19:48 | <TabAtkins> | I'll leave the Review Drafts boilerplate until someone actually needs one. |
| 19:49 | <annevk> | Anyway, I should let Domenic coordinate this since I'm about to land |
| 20:17 | <Domenic> | TabAtkins: my plan is to give it another go at templating all our stuff now that you added metadata generation and ordering. |
| 20:17 | <TabAtkins> | +1 |
| 20:17 | <TabAtkins> | Stress test the thing and file issues if anything seems wrong or insufficient, as always. |
| 20:51 | <tobie> | Alright, added a TL;DR to the slots proposal: https://github.com/heycam/webidl/pull/495 |
| 21:01 | <othermaciej> | Yay, our first post-launch PR for the policy documents (ok, not a very big one, but still glad to be working in the open on this kind of stuff) |
| 21:01 | <othermaciej> | https://github.com/whatwg/sg/pull/43 |
| 22:45 | <TabAtkins> | Hehehe |