WordPress.org

Making WordPress.org

Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#1245 closed defect (invalid)

Open Sans on Trac not rendering in Chrome

Reported by: morganestes Owned by:
Milestone: Priority: low
Component: Trac Keywords:
Cc:

Description

Not sure where the bug is, but figured I'd report it here since this is where I'm seeing it.

In Chrome 45 on OS X, Open Sans isn't rendering properly in Trac; this is most noticeable in the up/down arrows on the links to threaded comments on tickets. Instead of a regular arrow, the image is a square with both up and down arrows. Changing the font to 'sans-serif' displays the correct arrows and typeface in the rest of the page.

I've looked up this issue and it seems like it usually affects both Chrome and Safari, but Safari is rendering it without any problems. I also have Open Sans installed as a system font through Typekit, in case that becomes an issue during troubleshooting.

Attachments (2)

screencapture-20150922T220319.png (8.4 KB) - added by morganestes 4 years ago.
Open Sans not rendering
screencapture-20150922T220332.png (8.0 KB) - added by morganestes 4 years ago.
Font rendered as sans-serif

Download all attachments as: .zip

Change History (10)

@morganestes
4 years ago

Open Sans not rendering

@morganestes
4 years ago

Font rendered as sans-serif

#1 @netweb
4 years ago

Not seeing this using Chrome Dev Version 47.0.2503.0 dev (64-bit)

All the elements comment:11 in reply to: ↑ 1 ; follow-ups: ↓ 12 ↓ 15 ↓ 1 via Example via #29792#comment:11 are rendered using Open Sans


https://cldup.com/Z60WLBOFXr.png

@morganestes Got a link tho that same comment you used for your example?

#2 @morganestes
4 years ago

@netweb It's happening on this page, too, but my initial examples came from https://core.trac.wordpress.org/ticket/33165#comment:10.

#3 @netweb
4 years ago

I cannot see that extra glyph you have in your first image and here's the screenshot of how I see that same comment you've:

https://cldup.com/CQojRday-6.png

#4 @morganestes
4 years ago

  • Keywords close added
  • Resolution set to invalid
  • Status changed from new to closed

Thanks for checking it out. It certainly seems like it's something screwy with my browser; I'm on my phone and it's showing up just fine. I'll keep trying to figure out why it's happening and close this out.

#5 @morganestes
4 years ago

  • Keywords close removed

#6 @netweb
4 years ago

I've recently had issues with EFF's privacy badger plugin in that an option I didn't add or tweak would block assets, usually my own fault, so maybe a Chrome extension of some sort is messing with you ;)

#7 follow-up: @morganestes
4 years ago

I removed the Typekit version from my computer and the font renders just fine on the site now. I suspect there's enough variation between the two versions (the one loading from Google for Web and Typekit for desktop) that they just don't play well together. Bummer.

#8 in reply to: ↑ 7 @netweb
4 years ago

Replying to morganestes:

I removed the Typekit version from my computer and the font renders just fine on the site now. I suspect there's enough variation between the two versions (the one loading from Google for Web and Typekit for desktop) that they just don't play well together. Bummer.

Well that's just plain annoying :(

Note: See TracTickets for help on using tickets.