{"action":"closed","issue":{"url":"https://api.github.com/repos/mundschenk-at/wp-typography/issues/27","repository_url":"https://api.github.com/repos/mundschenk-at/wp-typography","labels_url":"https://api.github.com/repos/mundschenk-at/wp-typography/issues/27/labels{/name}","comments_url":"https://api.github.com/repos/mundschenk-at/wp-typography/issues/27/comments","events_url":"https://api.github.com/repos/mundschenk-at/wp-typography/issues/27/events","html_url":"https://github.com/mundschenk-at/wp-typography/issues/27","id":135087831,"number":27,"title":"Workaround for safari hyphenation bug causes wrong rendering in Chrome on initial page loads after link clicks, disappears after redraw","user":{"login":"cmeeren","id":7766733,"avatar_url":"https://avatars.githubusercontent.com/u/7766733?v=3","gravatar_id":"","url":"https://api.github.com/users/cmeeren","html_url":"https://github.com/cmeeren","followers_url":"https://api.github.com/users/cmeeren/followers","following_url":"https://api.github.com/users/cmeeren/following{/other_user}","gists_url":"https://api.github.com/users/cmeeren/gists{/gist_id}","starred_url":"https://api.github.com/users/cmeeren/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cmeeren/subscriptions","organizations_url":"https://api.github.com/users/cmeeren/orgs","repos_url":"https://api.github.com/users/cmeeren/repos","events_url":"https://api.github.com/users/cmeeren/events{/privacy}","received_events_url":"https://api.github.com/users/cmeeren/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/mundschenk-at/wp-typography/labels/question","name":"question","color":"cc317c"}],"state":"closed","locked":false,"assignee":{"login":"mundschenk-at","id":6943905,"avatar_url":"https://avatars.githubusercontent.com/u/6943905?v=3","gravatar_id":"","url":"https://api.github.com/users/mundschenk-at","html_url":"https://github.com/mundschenk-at","followers_url":"https://api.github.com/users/mundschenk-at/followers","following_url":"https://api.github.com/users/mundschenk-at/following{/other_user}","gists_url":"https://api.github.com/users/mundschenk-at/gists{/gist_id}","starred_url":"https://api.github.com/users/mundschenk-at/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mundschenk-at/subscriptions","organizations_url":"https://api.github.com/users/mundschenk-at/orgs","repos_url":"https://api.github.com/users/mundschenk-at/repos","events_url":"https://api.github.com/users/mundschenk-at/events{/privacy}","received_events_url":"https://api.github.com/users/mundschenk-at/received_events","type":"User","site_admin":false},"milestone":null,"comments":8,"created_at":"2016-02-20T15:36:17Z","updated_at":"2016-03-19T18:09:45Z","closed_at":"2016-03-19T18:09:45Z","body":"* wp-typography 3.1.3\r\n* Chromium 48.0 and Chrome for Android 48.0\r\n\r\nThe \"Add workaround for Safari hyphenation bug\" is causing trouble in Chrome, both for desktop and Android. See the following screenshot:\r\n\r\n![screenshot from 2016-02-20 16 24 12](https://cloud.githubusercontent.com/assets/7766733/13197463/71af536a-d7ee-11e5-90e0-fbb0e4cf4531.png)\r\n\r\nThe words apparently set in a \"lighter\" font are the hyphenated words (where `&shy;` has been added by wp-typography), and they're shown in the correct font (Raleway). I'm unsure which font the rest of the words are in. It's not the default theme font (Merriweather). It might be the default font in the browser.\r\n\r\nHere's how it's supposed to look:\r\n\r\n![screenshot from 2016-02-20 16 27 32](https://cloud.githubusercontent.com/assets/7766733/13197474/dd5b5050-d7ee-11e5-9ef8-1233eb295d36.png)\r\n\r\nI have turned off the \"Safari workaround\" setting on the live website now, but I can turn it on again if you want to do live debugging.\r\n\r\nTo reproduce this bug, I went to http://www.relativisticramblings.com (my blog). The bug does not appear on the front page initially. If I clicked on a post the error appeared on the post page. Furthermore, if I clicked the logo to get back to the front page, the error was visible there now.\r\n\r\nAny kind of redraw seems to get rid of the error. This includes reloading a problematic page, entering responsive view in the Chrome developer tools, changing any CSS rules in the developer tools, or hitting a break point while resizing the window.\r\n\r\nIn other words, the error only seems to appear when you land on a page by clicking on a link.\r\n\r\nThe error doesn't appear in Firefox. I haven't tested other browsers."}}