Is it only my machine?
Adding to viewport meta width="device-width" confuses too many hand-helds as cannot distinguish portrait vs. landscape. So this is about as far as meta can go, safely.
Then we get to the CSS disaster. Any absolute units anywhere in the style sheets, script, anything absolute on or attached to the page, causes IE to completely ignore any viewport measure applied to the page. IE Viewport will only tolerate 'rem' and 'percent' units. How are we going to style text-shadow? IE support for viewport is rock-bottom, but I am not giving up! Has Microsoft published an excuses page somewhere, because excuses could highlight the cause of failure, and therein point to solution (s)?
Partners Network engineer Amy Zhang advised me to take this problem here (she and her Research team are confused enough to state using 'em' units will fix everything for viewport), so I hope all who find this post can help. Is there a trick to get a Viewport dimensioned page to support absolute measures? When will Microsoft improve support for viewport in IE?
<!DOCTYPE html><head><html lang="en"><!-- or browser language you prefer --><meta name="viewport" content="initial-scale=1.0"><title> MY VIEWPORT TEST </title><style type="text/css>
body, * { font-size: 3vmin; }
@-ms-viewport { width: extend-to-zoom; zoom: 1.0; }
@viewport { width: extend-to-zoom; zoom: 1.0; }</style></head><body><h1>Viewport is Easy!</h1><p>What is a <strong>viewport</strong>?
Add your text here.</p></body></html>The closest I have got is with @media code using 'width=px' units. This use of absolute measure does not seem to disturb the viewport layout at all. But add a text-shadow to that @media and the Viewport crashes.
Important! There is something very fishy about the way W3 Candidate lumps together 'em' untis and 'rem' units.
http://www.w3.org/TR/css3-values/#font-relative-lengths
The former may be font-relative, but it is relevant to an assumed absolute font character measure (font "metric"). The latter refers to a "RELATIVE" extraction. Hence, 'rem' units and '%' units do not trash viewport, while 'em' units are a no-go. The entire hermeneutic of the W3 seems to be way off-base here. Hence the totally bizarre responses from Amy Zhang's Team.
Any ideas and resource links would be appreciated?
2015 WEB DESIGN... HTML5/CSS3... DOM development in code