- From: Myles C. Maxfield <mmaxfield@apple.com>
- Date: Tue, 09 Feb 2016 23:27:35 -0800
- To: Cameron McCormack <cam@mcc.id.au>
- Cc: www-style@w3.org
Yes, you're right. I retract this. --Myles > On Feb 5, 2016, at 8:49 PM, Cameron McCormack <cam@mcc.id.au> wrote: > > Myles C. Maxfield: >> When FontFaces are added to the Document's FontFaceSet, a layout may >> occur at any time which triggers these FontFaces to be load()ed. >> This layout uses the FontFace's attributes (family, weight, etc.) to >> discover which FontFaces need to be load()ed. However, during the >> load, script may change attributes of these FontFaces so that they no >> longer match what the layout requires. Instead, modifying FontFace's >> DOMString attributes should be a no-op (possibly additionally throwing >> an exception) after the FontFace has been load()ed. > > What’s the difference between modifying a non-CSS-connected FontFace > object’s descriptor attributes and modifying an @font-face rule’s > descriptors in a style sheet, while the font is loading? Since you can > make those changes to the @font-face rule (and you will see those > changed descriptor attributes on the corresponding CSS-connected > FontFace object) I don’t see a particular need to disallow this. > > -- > Cameron McCormack ≝ http://mcc.id.au/ >
Received on Wednesday, 10 February 2016 07:28:05 UTC