| 01:30 | Krinkle | spent way too much time reading the DOM spec only to realise jQuery was at fault all along – https://bugs.chromium.org/p/chromium/issues/detail?id=1010363 |
| 05:12 | <TimothyGu> | Krinkle: does that mean the bug should be closed? |
| 05:24 | <Krinkle> | TimothyGu: yep, can't do that myself it seems, though |
| 05:28 | <TimothyGu> | Krinkle: done |
| 06:59 | <hsivonen> | MikeSmith, annevk: Actually updating the Java side of the HTML parser to the Encoding Standard is still a TODO item. :-( |
| 07:00 | <hsivonen> | Using encoding_rs via JNI would probably be the easiest solutions but not the acceptable Java culture solution that would keep the parser reusable by others |
| 07:09 | <MikeSmith> | hsivonen: Ah, so the Gecko parser doesn't use that encoding code at all? |
| 09:43 | <hsivonen> | MikeSmith: it doesn't |
| 14:51 | <JakeA> | https://wicg.github.io/contact-api/spec/#contactsmanager - this API takes a sequence of an enum type. Due to WebIDL, this means it'll throw if an unrecognised type is provided. This feels inconsistent with dictionary types which ignore additional keys. Is there any prior art here? Should the API take a sequence of DOM strings instead and filter manually? |
| 15:07 | <Ms2ger> | JakeA, you means ContactsManager.select()? Note that it rejects anyway if you pass anything but a subset of ContactsManager.getAvailableContactProperties() |
| 15:09 | <JakeA> | Ms2ger: yeah, that's the behaviour I'm questioning. It does it in the prose, but IDL will be doing it anyway. It feels unlike how we usually design APIs, but I'm looking for a second opinion (or some prior art) |
| 15:10 | <Ms2ger> | I'm not aware of any prior art |
| 16:48 | <lgrahl> | o/ Hey folks, I'm currently testing the StorageManager API and I'm confused... navigator.storage.persist does not ask for a permission in Chrome (it does in Firefox) and just rejects it. I can't find anything in the interwebz about that problem. Any hints? |
| 16:55 | <Mek> | lgrahl: https://developers.google.com/web/updates/2016/06/persistent-storage explains some of chromes behavior (assuming it hasn't changed since then). I.e. it auto-grants in some conditions, and auto-denies in other conditions, but we'll never show a prompt. |
| 16:57 | <lgrahl> | Tried bookmarking it and it didn't work :/ |
| 16:57 | <lgrahl> | I'll try the home screen thing |
| 17:03 | <lgrahl> | Guess I'll call it a day and fiddle with it tomorrow. Thanks, Mek! |