Make WordPress Core

Opened 8 years ago

Last modified 5 years ago

#37665 new defect (bug)

Font Natively: Google maps can change the active font

Reported by: clorith's profile Clorith Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 4.6
Component: General Keywords: has-patch needs-refresh
Focuses: ui Cc:

Description

Because of the font stack ordering, Roboto has a high priority.

This is also the font used by Google Maps, so adding google maps embeds will change the font in use in the admin when viewing post pages.

Reported at https://wordpress.org/support/topic/system-fonts-easily-overridden-by-google-maps-api?replies=3&view=all

Attachments (2)

37665-roboto-lower.diff (9.6 KB) - added by stephenharris 8 years ago.
Move Roboto below Ubuntu
37665-ubnutu-higher.diff (9.6 KB) - added by stephenharris 8 years ago.
Move Ubuntu above Roboto

Download all attachments as: .zip

Change History (10)

This ticket was mentioned in Slack in #core by ocean90. View the logs.


8 years ago

This ticket was mentioned in Slack in #core by ocean90. View the logs.


8 years ago

#3 @NateWr
8 years ago

I've read the discussion in Slack, where questions were raised about where in the admin the map is getting loaded and why it's not in an iframe.

  1. I'm reporting the effect from seeing it on the admin bar on the frontend, although the effect is the same if a map is loaded in the admin outside of TinyMCE. You can see an example of this with the [Event Organiser](https://wordpress.org/plugins/event-organiser/) plugin if you provide an address for a venue (Events > Venues > Add New).
  1. Version 3 of the Google Maps API uses the HTML5 canvas element to render maps. I believe the iframe is only a fallback for browsers that do not support canvas.

#4 @stephenharris
8 years ago

This seems likely to be an issue specific to Linux distributions.

I've tested this on a mac and, as expected, the native system font is used. On Windows it uses Segoe UI. Both of these have a higher priority than Roboto.

On Ubuntu, however, the native system font is lower in priority than Roboto. I would suggesting moving Ubuntu above Roboto (or Roboto below Ubuntu, if we want to keep Oxygen-Sans in a relatively high position).

In either case it will provide a consistent experience for Linux users.

@stephenharris
8 years ago

Move Roboto below Ubuntu

@stephenharris
8 years ago

Move Ubuntu above Roboto

#5 @stephenharris
8 years ago

  • Keywords has-patch added

This ticket was mentioned in Slack in #core by ocean90. View the logs.


8 years ago

#7 @mattmiklic
7 years ago

On Ubuntu, however, the native system font is lower in priority than Roboto. I would suggesting moving Ubuntu above Roboto (or Roboto below Ubuntu, if we want to keep Oxygen-Sans in a relatively high position).

I don't think it would hurt to move Roboto to the very end of the font stack (before the generic fallback). It's probably the one font most likely to be self-installed by designers/developers, and the devices that we want to use it (Android, ChromeOS) are least likely to have any of the other fonts installed. Some testing would be in order, though.

#8 @desrosj
5 years ago

  • Keywords needs-refresh added

The patches need to be refreshed to apply to trunk.

Note: See TracTickets for help on using tickets.