[wp-trac] [WordPress Trac] #49066: Twenty Twenty: Font characters rendered as symbols

[WordPress Trac]

#49066: Twenty Twenty: Font characters rendered as symbols
---------------------------+--------------------------------
 Reporter:  pikta          |       Owner:  (none)
     Type:  defect (bug)   |      Status:  closed
 Priority:  normal         |   Milestone:
Component:  Bundled Theme  |     Version:  5.3
 Severity:  critical       |  Resolution:  reported-upstream
 Keywords:                 |     Focuses:
---------------------------+--------------------------------
Changes (by desrosj):

 * status:  reopened => closed
 * resolution:   => reported-upstream


Comment:

 Just wanted to note that `invalid` is the "catch all" default resolution
 in this Trac instance that is unfortunately named. It sometimes can be
 quite harsh and inapporpiate, especially when an issue is totally valid
 but there are just no actions that can be taken within the WordPress Core
 software. Moving forward, there is an
 [https://make.wordpress.org/core/2020/06/24/proposal-rename-invalid-
 worksforme-and-wontfix-ticket-resolutions/ active proposal to change]
 `invalid` to use more appropriate and less offensive terminology.


 Reading through the discussion on the
 [https://bugs.chromium.org/p/chromium/issues/detail?id=1036250 previously
 linked Chromium ticket], it seems that there was both a change in the
 macOS API as well as a change in Chrome's routine to match typefaces that
 was causing this issue in Chrome 79. There was a lot of difficulty
 reproducing the issue reliably, which makes it difficult to pinpoint the
 exact change that needs to be made.

 According to the
 [https://bugs.chromium.org/p/chromium/issues/detail?id=1036250#c43 last
 comment on that ticket], it also seems completely unreproducible on Chrome
 80 (which was [https://www.chromium.org/developers/calendar publicly
 released on February 4, 2020]). Chrome is now on version 85 and the
 Chromium ticket remains closed as fixed without any additional reports
 about of this problem.

 With all this in mind, closing this ticket in favor of the Chromium one
 was the correct action (though the `reported-upstream` resolution may have
 been a bit better), especially when 2-3 experienced WordPress contributors
 were taking the time to test and follow the discussion on that ticket. I
 hope this you helps understand the process that was followed @jemcbade.

 If anyone is still experiencing this issue, please add additional details
 to the Chromium ticket so that their team can investigate further.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49066#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform