| 16:33 | <annevk> | JakeA: https://github.com/annevk/orb/pull/1 |
| 16:34 | <JakeA> | Ohhh will take a look |
| 17:27 | <nox> | annevk: Like your new Twitter bio. :) |
| 17:37 | <shu> | annevk: ping |
| 17:38 | <annevk> | shu: heya |
| 17:38 | <shu> | annevk: hey, wondering if you got an opinion on [Unforgeable] |
| 17:38 | <shu> | annevk: is it a generally useful thing for the host to be able to do? i feel like it is, though outside of some legacy properties (document, etc) and trusted types i don't see much use |
| 17:39 | <annevk> | shu: we only have it for plugins, basically, to avoid them being lied to |
| 17:40 | <annevk> | shu: and I guess for Location it might also simplify some of the proxy setup since everything becomes an own property iirc |
| 17:40 | <shu> | annevk: ah ok |
| 17:40 | <shu> | annevk: so tl;dr: narrow scope, but still definitely useful for hosts to be able to express |
| 17:41 | <annevk> | shu: I don't see us getting rid of it before plugins and even after that it might be tricky |
| 17:41 | <shu> | annevk: expand a bit on why it might be tricky afterwards? |
| 17:41 | <annevk> | shu: also, it ought to be renamed to LegacyUnforgeable, we don't want new things using it |
| 17:42 | <annevk> | https://github.com/heycam/webidl/issues/350#issuecomment-335454404 |
| 17:42 | <annevk> | shu: well, we'd need something to express it being an own property I suspect for compat reasons |
| 17:43 | <shu> | annevk: makes sense, ok |
| 17:43 | <annevk> | shu: definitely Location would need something special |
| 17:46 | <shu> | annevk: why is Unforgeable legacy btw? non-configurable own props are just not how web apis are done? |
| 17:47 | <annevk> | shu: yeah, all the ones we have are rather out of place |
| 17:47 | <shu> | annevk: great, thanks a lot for the info |
| 17:48 | <annevk> | shu: and I think there were a few occasions where people wanted to use it to match some idea of precedent without that being okay |
| 17:48 | <annevk> | so best to discourage and then if it's really needed enshrine more legacy |
| 17:48 | <shu> | +1 |
| 18:10 | <annevk> | if you do `() => { new ReadableStream(...) }` why does that return undefined? |
| 19:10 | <andreubotella> | annevk, Domenic: Hi. May I poke you guys about https://github.com/whatwg/infra/pull/289 for a second? |
| 19:11 | <andreubotella> | Seems like both of you agree that, rather than defining code unit prefix and less-than as JS-string algorithms, their use of "length" should be changed and made clear. |
| 19:11 | <andreubotella> | Since that goes in quite a different direction than the PR, it'd be best to close it and open another for the same issue, right? |
| 19:34 | <Domenic> | andreubotella: that sounds reasonable to me! |
| 19:37 | <andreubotella> | ok, just wanted to make sure |
| 19:56 | <TabAtkins> | annevk: if you use {} for the body of the arrow func, it's a normal function body and needs `return` to return a value. |
| 20:41 | <annevk> | Thanks, yeah, bz pointed that out too |