Support » Theme: Twenty Twelve » Bug in Twenty Twelve and Chrome 31

  • When visiting a site using Twenty Twelve in Google Chrome 31, the following annoying bug is present:

    First visit everything is correct, but when you click on “Home” navigation link, then the font size is zoomed and much bigger then it should be. Then if you click on “Reload” button in Chrome, the font size is back to normal, but only until you click on any navigation link again, then the font size is zoomed and much bigger again.

    It does not have to be the “Home” navigation link. You can also click on any blog post in the page, and the font size is zoomed to be much bigger again. The font size will stay big until you click on “Reload” button in Chrome.

    This only started in Chrome 31, it was not like this in Chrome 30.

    Does anybody know what we can change in the theme to fix this?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Ok. I figured it out. Here is the fix: Find these lines in style.css:

    body.custom-font-enabled {
    	font-family: "Open Sans", Helvetica, Arial, sans-serif;
    }

    Add the new line font-size: 14px; so it will become like this:

    body.custom-font-enabled {
    	font-size: 14px;
    	font-family: "Open Sans", Helvetica, Arial, sans-serif;
    }

    (If you also add font-size: 1rem;, then it will not work.)

    Thanks for the css! I added it to my child theme and it worked fine. But I hope they fix the bug.

    At that same location, here is something more for Linux from the Tiny Forge version of Twenty Twelve:

    body { font-size: 14px; font-size: 1rem;
    /* Improving font rendering in Linux, in case default Open Sans font is disabled */
    	font-family: Helvetica, Arial, "Nimbus Sans L", sans-serif;
    	text-rendering: optimizeLegibility; color: #444; }
    body.custom-font-enabled { font-size: 14px; /* stop Chrome 31 font zoom */
    /* Improving font fallback in Linux */
    	font-family: "Open Sans", Helvetica, Arial, "Nimbus Sans L", sans-serif; }

    Thanks, aommundsen, that worked for me!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Bug in Twenty Twelve and Chrome 31’ is closed to new replies.