| 01:25 | <MikeSmith> | devsnek: what if the user doesn’t want all navigations to that to open in the same tab |
| 01:26 | <devsnek> | MIkeSmith: i dunno |
| 01:26 | <devsnek> | i think the general point is that it would improve the quality of use of the app |
| 01:28 | <MikeSmith> | I wonder how it would work on mobile |
| 01:33 | <devsnek> | MikeSmith: same way it does on desktop? |
| 01:35 | <MikeSmith> | devsnek: mobile doesn’t really have a tabbed UI, does it? |
| 01:35 | <devsnek> | MikeSmith: well i think in most cases this would result in fewer tabs |
| 01:35 | <MikeSmith> | ah |
| 01:36 | <devsnek> | i'm thinking of like |
| 01:36 | <MikeSmith> | yeah that would be useful |
| 01:36 | <devsnek> | how native apps can register protocol handlers e.g. spotify:// |
| 01:36 | <MikeSmith> | right |
| 01:36 | <devsnek> | where it doesn't open a new instance of the app each time |
| 01:36 | <devsnek> | it just triggers a callback in the open app |
| 01:36 | <MikeSmith> | yup |
| 01:36 | <devsnek> | same thing but for web apps |
| 01:37 | <devsnek> | and using origin instead of protocol |
| 01:37 | <MikeSmith> | yeah still though it seems like this could just be handled by a user pref in the browser preferences |
| 01:38 | <MikeSmith> | for users who want that behavior |
| 01:38 | <devsnek> | how |
| 01:38 | <devsnek> | like the website needs to handle it somehow |
| 01:39 | <devsnek> | i mean it would make sense to prompt the user "website wants to handle all these urls" like asking for notification access |
| 03:30 | <TimothyGu> | devsnek: tbh I think URL prefix is better than origin, but that's semantics |
| 07:06 | <annevk> | Web manifest has something like that, but it's not sorted all the way through |
| 07:52 | <Domenic> | I think this is mostly a browser UI thing? E.g. Chrome is trying to do it for installed PWAs? |
| 08:02 | <MikeSmith> | Domenic: seems like that to me too, but maybe I’m missing something |
| 08:22 | <annevk> | Domenic: MikeSmith: seems to me you'd want an event for an incoming navigation as well so you can update content rather than replace the whole document |
| 08:32 | <MikeSmith> | oh, I didn’t realize “update content rather than replace the whole document” was a requirement |
| 08:34 | <annevk> | Well, that seems like a logical extension to me; not sure who determines the requirements though |
| 08:52 | <Ms2ger> | annevk, ping https://github.com/heycam/webidl/pull/577 |
| 08:55 | <annevk> | Ms2ger: ta |
| 09:03 | <annevk> | Ms2ger: done |
| 09:04 | <Ms2ger> | annevk, bedankt |
| 12:13 | <annevk> | JakeA: we have some interested in moving further with CORB |
| 12:13 | <annevk> | JakeA: just so you know |
| 12:14 | <annevk> | JakeA: I pinged https://github.com/whatwg/fetch/issues/681#issuecomment-423159300 about getting the sniffing bits defined in detail |
| 16:28 | <MikeSmith> | https://stackoverflow.com/questions/52422662/how-to-get-file-upload-progress-with-fetch-and-whatwg-streams |
| 16:30 | <MikeSmith> | is there an example anywhere of how you would observe file-upload progress for a fetch+PUT request? |
| 16:56 | <annevk> | MikeSmith: nobody implements "upload streams" |
| 18:08 | <TabAtkins> | devsnek: I like the idea fine, so long as only "normal" navigations get intercepted; if you explicitly Ctrl-click or right-click=>open in new tab, it should skip the intercept and just open a new window. |
| 18:08 | <devsnek> | TabAtkins: sounds good to me |