- From: Matt Giuca <notifications@github.com>
- Date: Mon, 26 Jun 2017 21:01:30 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 27 June 2017 04:02:57 UTC
I don't think those are valid simplifications. * You need to specify the icon size in the manifest so the UA doesn't have to download them all to find out which one matches the desired size. "In time of streaming of 4K videos it should not be a big deal." isn't a useful argument; I should not require a connection capable of streaming 4K videos in order to visit a web page. On bad connections, it's vital that we download as little as possible when the user is simply browsing from page to page. Kilobytes matter. * User agents can scale icons but the best results will be achieved when the app specifies its own icons at the right sizes. User agents won't be confused; they'll just choose the best size and scale if necessary. I take your point, though, that developers will be confused about what sizes to include. Right now we aren't very clear on this. I'd like us to come to a standard set of icons that are recommended (across all browsers, not by each individual browser vendor). That recommendation could change or expand in the future but it would be helpful to have one. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/587#issuecomment-311246770
Received on Tuesday, 27 June 2017 04:02:57 UTC