- From: Marcos Caceres <w3c@marcosc.com>
- Date: Mon, 30 Jan 2012 22:45:22 +1000
- To: Robin Berjon <robin@berjon.com>
- Cc: Kenneth Rohde Christiansen <kenneth.christiansen@gmail.com>, WebApps WG <public-webapps@w3.org>, Mounir Lamouri <mounir@lamouri.fr>, Dean Jackson <dino@apple.com>, Paul Bakaus <pbakaus@zynga.com>, Jonas Sicking <jonas@sicking.cc>
On Monday, 30 January 2012 at 22:22, Robin Berjon wrote: > Hi, > > On Jan 30, 2012, at 12:43 , Kenneth Rohde Christiansen wrote: > > Orientation lock is already part of the CSS Device Adaption spec as part of the viewport meta tag > > > > Sorry, I should indeed have mentioned that as part of the background. The problem with specifying orientation as part of the viewport at rule is that it leads to circular dependencies (you can set an orientation inside a media query that changes the viewport and triggers and endless loop). The spec tries (meekly) to defend against that, but I find it difficult not to get the impression that this leads to a tangled mess and that it will confuse developers (it certainly confuses me when I try to make sense of the circularity avoidance recommendations made in the specification itself). This could be solved if it were only to appear in meta elements, but right now that's not the case and the section on meta elements in CSS DA isn't normative. For fun, can you show how that happens with the meta tags? I was the one that originally proposed the orientation locking using the meta tag, so I'm interested to hear what happened (or send me pointer). Apologies that I have not followed the discussion.
Received on Monday, 30 January 2012 12:46:08 UTC