What a 130% System Font Size Does to a Browser Game

My phone has run a 130% system font size for a year, mostly because I read on it more than I play on it. Last week I set it back to 100% for an hour and every H5 game felt like a different product.

The top bar breaks first. Score, timer and pause icon usually share one measured row, so at 130% the pause icon slides off the edge or the score wraps onto two lines. In one quiet tap game I could not see my score.

Self-drawn dialogs are the second problem. When a game sizes a confirm box in fixed pixels, the label grows and the box does not, so a restart button reads “Restart 1” on a narrow Android screen.

Some pages handle this by letting the text container grow and pushing everything else down. Two H5 entries I open often, dan777 and h5.tt789, keep the score in a flexible span and shrink the numeral instead of the frame.

The opposite failure is worse: a game that measures text once at load and never again. Rotate the phone, or change the size while the tab sits in the background, and the canvas keeps the old metrics until a hard reload.

Install pages share the trap. On qtgame apk the size and permission list fold from two columns to one; on csx 8888 the button stays one line tall while its caption wraps underneath it.

The cheapest fix is boring. Test at 100% and 130%, in portrait, on a phone that is not the newest one, and keep a note like the one I made for h5.cv777.

None of this is about graphics. A game that only looks right at default text size assumed a screen it never checked.