Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter lenvo

    (@lenvo)

    Any suggestions?

    Thread Starter lenvo

    (@lenvo)

    I made a mistake in my CSS. Problem resolved!

    Thread Starter lenvo

    (@lenvo)

    Hello,

    For 2 days I try to resolve this problem, I really hope someone can provide me some help.

    in IE browsers @font-face “dashicons” is not working on my website. Icons are not visible on my website. In other browsers @font-face “dashicons” works well.

    WordPress 4.4.2 – Llorix One theme
    Website

    Debugger report Explorer:
    CSS3113 “@font-face mismatch between document origin and EOT root string”

    Any suggestions how to fix this @font-face error?

    Thread Starter lenvo

    (@lenvo)

    Thanks for your reply Andrew. ??

    I found the page of Dashicons:
    Dashicons
    I checked Dashicons CSS and font files in my template, but so far my knowledge goes configuration seems ok. I searched for more information about Dashicon browser issues but unfortunately not found a answer to this particular problem.

    Unfortunately I did not found out how to fix the missing dashicons icons in IE/Edge browsers. The debugger messages does not make me much wiser.

    Best regards,

    Lennart

    Thread Starter lenvo

    (@lenvo)

    Any suggestions? Hope someone could help me out on this!

    Thread Starter lenvo

    (@lenvo)

    Thanks for your reply.

    When I check font in Edge debugger I see many questionmarks ?? in dashicons.eot.

    Here is the link to my website:
    Website

    Best regards,

    Lennart

    Thread Starter lenvo

    (@lenvo)

    Anyone can help me out on this?

    Debugger Edge messages:

    CSS3120: No fonts available

    CSS3113
    "@font-face mismatch between document origin and EOT root string"
    The font cannot be used because the URL(rootstring) in the "Embedded OpenType font (EOT)" does not match the domain of the document using the font.
    The URL checksum in the "EOT" rootstring might be incorrect, indicating a corrupt or altered URL for the font. Ensure that the font is licensed or has permissions for the website where the fonts are being used.
Viewing 7 replies - 1 through 7 (of 7 total)