- From: <piranna@gmail.com>
- Date: Wed, 18 Sep 2013 14:42:19 +0200
- To: Anne van Kesteren <annevk@annevk.nl>
- Cc: Ian Hickson <ian@hixie.ch>, WebApps WG <public-webapps@w3.org>
> Ian, was it ever the intent that these methods affect the way Fetch > works? Either way, this could use some tightening up as the current > language is quite vague. I think we should only let them affect the > navigate algorithm. Either way, we should clarify where the URL > translation happens as that will affect Service Workers (latest name > of Navigation Controller). > I find the fact of being able to use custom protocols on <img> and <script> tags a cool feature instead of a bug, so I would not let them only to be used just for navigation purposes. Also, after reading about Service Workers, I think that a combination of both can lead to really interesting things. At least for my own personal use case (web surfing on a WebRTC DataChannels-based P2P network, translating the request using a custom protocol to the real location of the resources) would be the best solution, and also would lead to other interesting use cases (web servers inside the browsers... :-P ). -- "Si quieres viajar alrededor del mundo y ser invitado a hablar en un monton de sitios diferentes, simplemente escribe un sistema operativo Unix." – Linus Tordvals, creador del sistema operativo Linux
Received on Wednesday, 18 September 2013 12:43:07 UTC