You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know that font-face rule declarations have calmed down a bit in the last year or two, but I just ran into an issue parsing some generated font-face styles that I thought might crop up for other people as well:
Here are the results of using the online parser. You'll notice that the first src gets overridden by the second. I recognize that this is logical and likely even desirable behavior, but it's giving me some trouble in IE when I use the rule.toString and/or rule.cssText without that first src included.
It's simple enough for me to work around this by declaring my font-face rule differently, but when thrown into the wild, I'd like to be able to accomodate all kinds of wonky font-face declarations.
UPDATE: I apologize for not making the connection earlier, but this seems no different than #16. I'll check out #53
The text was updated successfully, but these errors were encountered:
I know that
font-face
rule declarations have calmed down a bit in the last year or two, but I just ran into an issue parsing some generatedfont-face
styles that I thought might crop up for other people as well:Here are the results of using the online parser. You'll notice that the first
src
gets overridden by the second. I recognize that this is logical and likely even desirable behavior, but it's giving me some trouble in IE when I use therule.toString
and/orrule.cssText
without that firstsrc
included.It's simple enough for me to work around this by declaring my font-face rule differently, but when thrown into the wild, I'd like to be able to accomodate all kinds of wonky font-face declarations.
UPDATE: I apologize for not making the connection earlier, but this seems no different than #16. I'll check out #53
The text was updated successfully, but these errors were encountered: