Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

@-ms-viewport { width: device-width } #119

Closed
jonathantneal opened this Issue Aug 29, 2012 · 9 comments

Comments

Projects
None yet
6 participants
Contributor

jonathantneal commented Aug 29, 2012

IE10 will use CSS to handle device adaptation:

http://blogs.msdn.com/b/ie/archive/2012/06/19/adapting-your-site-to-different-window-sizes.aspx

http://hammerspace.co.uk/2012/04/responsive-design-in-internet-explorer-10-windows-8

Following this spec:

http://www.w3.org/TR/css-device-adapt/

Since this would normally be handled with <meta name="viewport"> the issue of normalization is icky. Both HTML and CSS would be required for normalization. Therefore, I am neither in favor or out of favor to add this into normalize, but I want it tracked and discussed.

Owner

necolas commented Aug 30, 2012

Yeah, I'm not convinced that there is a default to normalize. But happy to leave this open and see where the future ends up.

Thanks for opening a thread about this. Handling viewport in CSS makes more sense to me than handling it with an HTML tag because it's strictly a presentational concept. But to your point @jonathantneal, I don't know how widely supported @viewport is yet, so I don't know if it's a little early to add this to normalize.css or if it's worth waiting until other vendors join the party.

Owner

necolas commented Aug 31, 2012

While handling viewport in CSS does seem to make more sense, that doesn't necessarily mean that it is something Normalize.css can or should try to tackle. And Opera were the ones who first introduced this feature, with -o- prefix.

Do you have any rules of thumb you usually use to decide whether or not Normalize.css should address a particular browser discrepancy?

It would only make sense if normalize.css is coming with predefined MQs - And that is, by now, not the case. I think that would be the first reason to not include this in normalize.css.

Owner

necolas commented Jan 19, 2013

Going to pass on this. I think it has some significant consequences (quite aside from the existing IE 10 bugs with @viewport) that mean it's not appropriate to modify all browser defaults like this. Thanks :)

@necolas necolas closed this Jan 19, 2013

Volker-E commented May 1, 2013

First of all, excuse me for adding this here, but it's rather an addition to that issue than a completely new one.
Doesn't http://timkadlec.com/2012/10/ie10-snap-mode-and-responsive-design/ bring in a new argument to add viewport { width: device-width; } to normalize.css?
So the question to me is, is width: device-width; only best practice or a normalization?

I originally discussed this as a fix for IE10 snap mode in http://hammerspace.co.uk/2012/04/responsive-design-in-internet-explorer-10-windows-8
It would have been a viable candidate for inclusion in normalize if it wasn't for a bug in Windows Phone 8 (IE10) where the width was rendered as device pixels instead of CSS pixels.
It is preferable to have mobile users (who have no choice) get a better experience than the (rare) Win 8 snapped users, so this doesn't belong in Normalize right now.

Volker-E commented May 1, 2013

Thanks for clarification!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment