EDGE fails to consider multiple @font-face rules

By design Issue #8769498

Details

Author
Richard B.
Created
Sep 6, 2016
Privacy
This issue is public.
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

If you have two separate CSS @font-face declaration blocks for the Same Font then EDGE reports a console error after only considering the first block. Then goes on to find a successful match from the second CSS block, but the error was already thrown.

All other browsers handle this successfully.

Two separate @font-face block declarations are required for the Same Font to overcome the IE6-8 font-face bug, where the first block just contains an EOT file, and the second block contains Data URI fonts.

See our example at:
https://living.video/vjsreduced.html

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

      Changed Assigned To to “Bogdan B.”

      Changed Status to “Won’t fix”

    • The common pattern we see on the web is specifying two src in the same rule, e.g. in your case:

       

      @font-face {
        font-family: VideoJS;
        src: url(“…/font/2.0.0/VideoJS.eot?#iefix”) format(“eot”); }
        src: /* woff, etc. */

      }

    • Microsoft Edge Team

      Changed Status from “Won’t fix” to “By design”

    You need to sign in to your Microsoft account to add a comment.

    Sign in