On Tue, Dec 3, 2013 at 4:48 AM, Jonas Sicking <jonas@sicking.cc> wrote: > As I understand it, the main use case for putting orientation in the > manifest is to enable the UA to launch the app in the correct > orientation from the get-go. It seems very hard for an implementation > to do that with this solution. You would have to inspect the cached > HTML and CSS to figure out what the initial orientation will be. If > there is any HTML/CSS cached. If it's loaded from the server or a > service worker you're completely out of luck. > Assuming @viewport is included in inline CSS in the <head> (which it needs to be anyway, so the preload scanner can evaluate media attributes and responsive images), then the UA will parse the @viewport before it starts painting anything. Is there any benefit to the UA knowing the orientation before it starts painting the page?
Received on Tuesday, 3 December 2013 11:03:46 UTC