| 00:04 | <Ehsan Azari> | Is there any movement on Contact Picker API? And, is there any shim/polyfill for Contact Picker API that works in all browsers? Or any alternative approach? |
| 02:05 | <Dominic Farolino> | Domenic: Just want to clarify what you mean by "blow up", in https://github.com/whatwg/html/issues/9488#issuecomment-1650858581. The spec wouldn't crash, right? I think we'd just a get a network error because we'd enter #create-navigation-params-by-fetching, right? |
| 02:06 | <Domenic> | I admit I was typing that on my phone without looking at the spec, let me try harder |
| 02:07 | <Dominic Farolino> | Np. I think regardless of whether we decide to use "is" or "matches", we end up with a network error and an error document in the document state. |
| 02:09 | <Dominic Farolino> | Unrelated: why is https://html.spec.whatwg.org/#concept-document-salvageable italicized (in dfn and all refs). Seems random? |
| 02:10 | <Domenic> | Hmm yeah you're right, it'd end up trying to fetch it. Srcdoc processing is keyed on documentResource not URL (in the spec) |
| 02:10 | <Dominic Farolino> | Right. Its just that Chrome has this open bug where we still allow it to resolve in some cases |
| 02:10 | <Domenic> | And using "is" is probably better to keep those in sync |
| 02:11 | <Dominic Farolino> | (I believe Arthur was trying to remove that behavior and match the spec, but ran into some difficulty) |
| 02:11 | <Dominic Farolino> | Cool, thanks for taking a look so quickly |
| 02:14 | <Dominic Farolino> | Now I'm trying to think through if it ever matters what's in the error document state's "origin" field in that scenario... |