Viewing 13 replies - 1 through 13 (of 13 total)
  • Moderator James Huff

    (@macmanx)

    Chrome 45 has a rendering bug. There is a ticket open on Chrome’s bug tracker about this issue, hopefully they will fix it soon: https://code.google.com/p/chromium/issues/detail?id=509179

    In the meantime, here is a workaround to eliminate the issue in Chrome.

    Go to chrome://flags/#disable-slimming-paint
    Enable the “Disable slimming paint” option.
    Ensure that the “Enable slimming paint” option below it is not turned on.
    Relaunch Chrome.
    When you’re done, the final result should look like this:
    https://cloudup.com/cddYghY8fBd

    This will disable the problem code in Chrome and allow the menus to render normally.

    Thread Starter david2112

    (@david2112)

    Great answer, thank you…

    I personally won’t fiddle with Chrome’s internal flags anymore…

    Until then I’ll edit in FF.

    I have linked this answer from my SO question so that others can find it.

    Happened to me while doing a training,

    Hopefully my client wasn’t looking too closely at tabs i showed him, Chrome engine is known for large flows like:

    – being slow
    – fiddle support for Google Fonts; and in general font rendering
    – intense cpu use while at 20 + tabs

    I hope these things while be fixed some day,

    Moderator James Huff

    (@macmanx)

    You’re welcome, and thanks for linking in your SO thread! ??

    Thank you James, no bunch, thank you for all the great work…

    Clearly a bug in WordPress. I’ll wait for an update as opposed to messing about in my browser settings – like I have time for that!

    I don’t even imagine how difficult it can be to clear a bug in WordPress.. It sometimes takes me a week with simple html/css stuff. With a different focus, but damn.

    Moderator James Huff

    (@macmanx)

    kendhal, did you read the Chrome bug report that was linked to, or really any of the thread? It’s clearly a bug in Chrome, because it is a bug in Chrome.

    There won’t be any update to WordPress to fix this because it’s not a WordPress bug. The Chrome developers will fix it, or you can apply the work-around above, or use a different browser like Firefox.

    Moderator Samuel Wood (Otto)

    (@otto42)

    www.remarpro.com Admin

    kendhal: It’s a bug in Chrome, not WordPress. WordPress works fine in every other browser. Chrome released an update, and it is not just WordPress showing these layout problems. Chrome will fix it, however, disabling this browser setting is a workaround until they do so.

    A question though, how is that possible it only affects Chrome on some OSes while most browsers are based upon chromium now? (Chrome, Safari, Gecko, Firefox..)? On-top code?

    For instance, i dont see this glitch in left-hand menu in Firefox.

    Thanks for answers and follow-up,

    Moderator Samuel Wood (Otto)

    (@otto42)

    www.remarpro.com Admin

    how is that possible it only affects Chrome on some OSes while most browsers are based upon chromium now

    Two things:

    a) It affects Chrome on all platforms where version 45 got auto-updated a few days ago (Windows, Mac, and Linux)

    b) Other browsers that use the webkit/blink engine have not updated to the version with the problem yet.

    The problem is confirmed to a Chrome issue, and it is being tracked in their bug tracker system. It will very likely get fixed before it affects other browsers.

    Wow, thank you very much for answer, now I can see auto update also affects that kind of things in a different time for each client, so on..

    Thank you,

    Moderator James Huff

    (@macmanx)

    while most browsers are based upon chromium now? (Chrome, Safari, Gecko, Firefox..)?

    Further clarification, of that list, only Chrome is based on Chromium. Safari and Chromium/Chrome are based on WebKit/Blink as their rendering engine, which as Otto mentioned, Safari is rather behind on. Gecko is actually the rendering engine that Firefox is based on.

    Chromium is a fully functional browser, not a rendering engine, and is essentially nothing more than Chrome without the Google parts.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Bug – broken dashboard layout :(’ is closed to new replies.