On Mon, Jun 23, 2014 at 5:02 PM, Cameron McCormack <c...@mcc.id.au> wrote: > On 24/06/14 06:30, Jonas Sicking wrote: >> >> Has the [MapClass] issue been resolved yet? > > No. There's a note in the spec that says [SetClass] will be removed in > favour of members on the interface that feel like a Set, but there's nothing > concrete in there yet. I'm proceeding with something simple for the moment > (add, has, delete methods plus a length attribute and an indexed getter) and > I'll something similar on www-style.
I don't understand why anyone would want to key gets and sets using FontFace instances. I.e. why would you want to ever call fontFaceSet.has(myFontFace). That returning false doesn't really tell you anything about what fonts are or are not loaded. For get() operations (including has()) you likely want to pass in a url-string or a family name as key. For delete() operations passing in a FontFace object might make sense, but passing in a url-string or a family name is probably as commonly useful. If family names are required to be unique, then maybe keying on family name for both get() and delete() operations is the way to go. Either way, these are the things that would be great to sort out. Right now it feels to me like everyone is acting like the spec is done, when in fact a good chunk of the API surface is still missing. / Jonas _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
