Why access this tag?
This project was prompted by the need for high definition canvas rendering when css pixels do not match device pixels. To achieve HD rendering when the html is scaled up, the canvas element must rendered in at a larger size relative to the html scale factor. If HTML is scaled up by 2, the canvas should render contents at twice the size to prevent blurring when the browser presents the scaled canvas raster.
- Device: iPad3
- Device Resolution: 2048x1536
- Viewport Scale: 1
- Pixel Ratio: 2
- Logical Resolution: 1024x768
In this instance, the device resolution is much higher than the logical resolution that the webpage is being rendered with. The webpage will effectively be rendered at half resolution and the scaled up to fit the full screen. Any canvas element within the page will be scaled up post render, which causes normally sharp graphics to blur. To compensate, we should create the canvas at twice the size and then scale it down to fit within smaller page. If the viewport was 0.5 instead of 1, the effective page resolution would be 2048x1536 (matching the device). In this case, we do not want to create an oversized canvas and thus need to know what the viewport scale is.
Don't worry if this is over your head. It is just one use case.
Note that this demo might not have any effect on your desktop browser as viewport tags are only require for devices with pixel ratios other than 1 (most mobile devices). Follow the link below to see the demo.
Download the repo and copy the www/js/swevans/viewport-config-X.X.js file into your project.
The script must be loaded prior to using it within your code. ViewportConfig follows a static interface and exists in a the "swevans" namespace, and thus does not need to be instantiated. Use the class directly to get / set viewport tag content properties:
// Getting the initial-scale value var theInitialViewportScale = swevans.ViewportConfig.initialScale; // Setting the initial-scale value to some value // note this will change the scale on all supporting browsers swevans.ViewportConfig.initialScale = 5.1; // Clearing a property by setting to null swevans.ViewportConfig.initialScale = null;
Note that if no viewport tag is included in the page, one will be created when a property is set via ViewportConfig. If multiple viewport meta tags exist, the one appearing last in the document will be used by ViewportConfig.
ViewportConfig provides the following public interface:
// NOTE: all numerical values are rounded to 4 decimal places // NOTE: setting any property to null will remove it from the tag // gets and sets the initial-scale property as a number swevans.ViewportConfig.initialScale; // gets and sets the minimum-scale property as a number swevans.ViewportConfig.minimumScale; // gets and sets the maximum-scale property as a number swevans.ViewportConfig.maximumScale; // gets and sets the user-scalable property as a boolean // false=no, true=yes swevans.ViewportConfig.userScalable; // gets and sets the width property as a string swevans.ViewportConfig.width; // gets and sets the height property as a string swevans.ViewportConfig.height; // gets and sets the target-densitydpi property as a string swevans.ViewportConfig.targetDensityDPI; // gets the current device pixel ratio, 1 if undefined swevans.ViewportConfig.pixelRatioScale; // a bool indicating if the ViewportConfig tag is supported // false means that the tag is ignored or not required swevans.ViewportConfig.isSupported; // A helper function to update the viewport initial scale such // that css pixels will match hardward pixels in 1:1 ratio. swevans.ViewportConfig.matchDevice();
- The ViewportConfig class should work in all modern browsers (IE9+). IE10+ does not support the viewport tag, but also isn't relevant / needed on desktop (where most of IE is used?), so lack of support is moot.
- The viewport tag itself may not be as widely supported, and thus ViewportConfig changes would have no effect.
- Widespread browser testing hasn't been done yet, but the simple code should run on just about anything.
- Note that if more than one viewport meta tag is included in the html file, the tag appearing last (closer to the end of the document) will be accessed / manipulated.
- If no viewport tag is present in the dom, one will be added when a property is set via ViewportConfig.
- ViewportConfig does not attempt to read the 'current' viewport scale. We cannot reliably do so because the user scalable, zoom properties, or scrollbar measuring method of the users web view could throw off the reading.
- Note that the viewport meta tag is not W3C standard. The future of viewport support is leaning in the direction of using '@viewport' css rules to control the viewport configuration. This CSS rule is still not widely supported. The only known implementation is in IE10.
- Specify a single viewport meta tag at the top of your html files
- It is usually best to omit width, height, and target-densitydpi properties.
- The Accessibility Project recommends allowing user-scalable, be sure to manage your max and min scale appropriately.
- An example ideal viewport meta tag is:
- If you MUST know the current viewport scale, it is best to disallow user scaling and read the initial scale property
Known Issues and Considerations
- There is a known limitation that the viewport class rounds all numerical values to four decimal places, this is to avoid issues when converting numbers to and from strings.
- The userScalable property may not behave exactly as expected. On some devices pages won't actually become scalable until they are too large to fit on the users screen, no matter what the userScalable setting is set to. They may also become scalable regardless of the userScalable setting on some pages. These issues are mostly linked to android devices. This issue is systemic beyond this library.
- Viewport configuration might not even apply in some browsers (mostly desktop and IE10+).
- It would be nice to support the '@viewport' CSS rules in addition to the meta tag.
- In an ideal world we could figure out the current viewport scale
Compiling the typescript is not required to use the library. Should you decide to do so, run the compiler within the src directory. It should pickup the tsconfig.json configuration file and output to www/js/swevans/viewport-config-X.X.js.