- From: Keith Clark via GitHub <sysbot+gh@w3.org>
- Date: Tue, 22 Jan 2019 00:41:11 +0000
- To: public-css-archive@w3.org
keithclark has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-fonts] Clarification on behaviour when modifying @font-face rules == I'd like some clarification on how fonts should be handled if the `@font-face` block that describes them is modified after the document has loaded. Using any of the methods below, my expectation (which could be wrong) is that the browser should stop rendering text using a custom font: * Invalidating the `@font-face` rule by renaming it to something like `@-disabled-font-face` * Changing the `font-family` value in a `@font-face` rule but not updating the `font-family` elsewhere * Changing the `src` value in a `@font-face` rule * Disabling a stylesheet containing an `@font-face` rule * Deleting a stylesheet containing an `@font-face` rule However, Safari, Chrome and Firefox all continue to render text using the font. Is this the expected behaviour? If so, could somebody point me to the part of the spec that defines it? Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3542 using your GitHub account
Received on Tuesday, 22 January 2019 00:41:12 UTC