pbakaus/viewporter sits at 592 stars on GitHub, written primarily in JavaScript. Meta viewport done right.
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
Viewporter is a open-source JavaScript project by Zynga to ease mobile viewport management. It specifically simplifies the part of setting up the right screen dimensions and removes the pain from handling the viewport meta tag manually.
What does it do?
When put into the header of a page and when running a mobile device, Viewporter will first try to scroll away any URL or debug bars to maximize the visible window, and then substracts the remaining chrome/UI height from the window, effectively removing ugly scrollbars along the way. It will also track orientationchange, thus, you will always have a maximized viewing experience.
How to use?
In v1, all you had to to was to put Viewporter into the head of the page. There's just a little bit more to do in v2, but it isn't painful:
Add the following meta viewport to the of your page:
Wrap your element with the viewporter wrapper div:
<body>
<div id="viewporter">
...
</div>
</body>
That's it, really! Feel free to have a look at the demo pages if something doesn't work as expected.
What's wrong with doing it manually?
You could of course try to set the viewport meta tag yourselves, as suggested in various places, usually something like <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1">. You will quickly recognize two apparent issues:
proportional device-height doesn't subtract the chrome height, so the window is always larger than the viewport when set, causing scrollbars even on empty pages
rotating the device will cause the page to zoom (as device-width isn't inverted on rotation)
even with a manually fixed viewport, there's a stupid gap at the bottom of the page (when using absolutely positioned elements)
Advantages of using Viewporter
So what's in it for you? There's a couple of automatic advantages for you when the Viewporter is running. Here's a list:
Maximized viewport (scrolling away unneeded UI)
Easy layouting
Easy layouting?
Yep. Take a <div>, position it absolutely, set its width and height to "50%", left and bottom to 0 and the background to any color. With Viewporter enabled, it will be placed at the bottom left corner of the window, and stretch to the middle of the window. Sounds obvious right? It isn't really, when you want a maximized window.
API
Viewporter is almost zero configuration. There's only one constant to check if Viewporter is in fact running, a convienience method to detect landscape orientation and a smart ready callback function. In addition, there's a couple of events you will likely want to use.
Options
viewporter.forceDetection (Boolean) - defaults to false, enabling it will cause the Viewporter not to use its profiles for devices (see devicepixel demo)
viewporter.preventPageScroll (Boolean) - defaults to false, enabling it will prevent scroll events on the body element. Use this option to cancel iOS overscroll effect, which causes the view to bounce back when scrolling exceeds the bounds. Additionally it will scroll back the pane if the user clicks the page after selecting the address bar on iOS.
Constants
viewporter.ACTIVE - true if the Viewporter is enabled and running (smartphones!), false if not (Desktop, non-touch device)
viewporter.READY - true when the viewportready function has already been fired. Useful if you're lazy loading initializing code
Methods
viewporter.isLandscape() - returns wether the device is rotated to landscape or not
viewporter.ready() - accepts a callback and fires it when the viewporter has been successfully executed
viewporter.refresh() - refreshes the viewport. This is eg. useful when the browser displays an inline confirmations such as the geolocation alert on Android. Hint: Listen for resize events and then call this method.
Events
All events fire as native events on the window object.
viewportready - fires as soon as the Viewporter has been executed for the first time
viewportchange - fires when the viewport changes, i.e. the device is rotated, and after Viewporter has been executed again
TopGit's last sync did not record any GitHub topics for pbakaus/viewporter. GitHub topics appear in the right sidebar of a repository page; that's the authoritative place to check.
How active is development on pbakaus/viewporter?
The most recent commit recorded on pbakaus/viewporter was 13.5 years ago, based on the GitHub push timestamp. The repository has 45 forks — one of the better signals of community interest.
How many stars does pbakaus/viewporter have?
pbakaus/viewporter has 592 GitHub stars — refresh the page for the live number, or check github.com/pbakaus/viewporter. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
What language is pbakaus/viewporter written in?
pbakaus/viewporter is written primarily in JavaScript. GitHub's language field is based on the largest share of bytes in the default branch.
Where do I read more about pbakaus/viewporter?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/pbakaus/viewporter is the definitive source.
Read full README in the tab above.
Curious whether viewporter is right for you?
Let ChatGPT, Claude, or Perplexity look into it — click below and see what AI actually says about viewporter.
/viewporter