Title: Device Display
Last modified: September 1, 2021

---

# Device Display

 *  Resolved Anonymous User 16052280
 * (@anonymized-16052280)
 * [4 years, 9 months ago](https://wordpress.org/support/topic/device-display/)
 * Hi guys,
 * Your option **Device Display** does not work on my side. Whether I set it on **
   Only Desktop** or **Only Mobile Devices** it will show on both of them.
 * I’m testing it with a simple font preload. It preloads on all devices with no
   regard of the selected option.
    `<link rel="preload" href="some-font.woff" as
   ="font" type="font/woff" crossorigin>`
 * Could you provide some feedback, please?
 * Thank you,
    Andrei

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Thread Starter Anonymous User 16052280
 * (@anonymized-16052280)
 * [4 years, 9 months ago](https://wordpress.org/support/topic/device-display/#post-14833578)
 * **UPDATE**
 * I only see this issue in Chrome.
    In Firefox this seems to be working fine.
 *  Plugin Author [99robots](https://wordpress.org/support/users/99robots/)
 * (@99robots)
 * [4 years, 9 months ago](https://wordpress.org/support/topic/device-display/#post-14851261)
 * @andrei0luca – we looked into this but since it does work in all browsers and
   not in Chrome, our thought is that it is definitely due to how Chrome handles
   preloading of fonts. It’s unrelated to our plugin.
 * Some web searching found this gem:
    a) [https://stackoverflow.com/questions/42616709/preloading-fonts-in-chrome-with-preload-link-directive](https://stackoverflow.com/questions/42616709/preloading-fonts-in-chrome-with-preload-link-directive)
   b) [https://www.freecodecamp.org/news/web-fonts-in-2018-f191a48367e8/](https://www.freecodecamp.org/news/web-fonts-in-2018-f191a48367e8/)
   c) [https://developer.mozilla.org/en-US/docs/Web/HTML/Link_types/preload](https://developer.mozilla.org/en-US/docs/Web/HTML/Link_types/preload)
   d) [https://drafts.csswg.org/css-fonts/#font-fetching-requirements](https://drafts.csswg.org/css-fonts/#font-fetching-requirements)
 * Notice that there are 2 points discussed in that thread:
    1) font-face 2) crossorigin
   attribution
 * See if variations of including that change your result for Chrome. For now, I
   will mark this as resolved since it’s not really a plugin related question. Though,
   feel free to reply back if you find otherwise after attempting to solve based
   on the findings in that threads above.
 * Thank you.
    -  This reply was modified 4 years, 9 months ago by [99robots](https://wordpress.org/support/users/99robots/).

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Device Display’ is closed to new replies.

 * ![](https://ps.w.org/header-footer-code-manager/assets/icon-256x256.png?rev=2681303)
 * [Header Footer Code Manager](https://wordpress.org/plugins/header-footer-code-manager/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/header-footer-code-manager/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/header-footer-code-manager/)
 * [Active Topics](https://wordpress.org/support/plugin/header-footer-code-manager/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/header-footer-code-manager/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/header-footer-code-manager/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [99robots](https://wordpress.org/support/users/99robots/)
 * Last activity: [4 years, 9 months ago](https://wordpress.org/support/topic/device-display/#post-14851261)
 * Status: resolved