- From: Alex Russell <notifications@github.com>
- Date: Mon, 09 Mar 2015 23:01:32 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Message-ID: <w3c/manifest/issues/326/78000401@github.com>
These are my proposals, so I feel I should chime in with a few points: 1.) I don't think this is anything more than crappy-header de-crufting. This stuff is already in the web. This lets us move it out of precious `<head>` bytes and into a single location. Doing prefixed stuff inside the manifest hardly helps 2.) part of the goal is to put the slam-door prompting that @marcosc and I hate in (more tasteful) UA-controlled UI. This will help us de-cruft the web as webmaster advice can ever-more-forcefully require that they use the "supported" mechanism instead of ad-hoc slam-doors. The second point can't be over emphasized. I think everyone wants to get rid of crappy full-page prompts and this will help. For instance, once developers move to it, the Chrome mechanism for showing the prompt will use the same engagement criteria for the web page as the offer for the web app will use: never on the first visit, only once a user re-visits a few times in a week, and not again for some months once swept away. Regarding contents of the list, I'm open to pretty much anything that works. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/326#issuecomment-78000401
Received on Tuesday, 10 March 2015 06:02:01 UTC