- From: Ian Kilpatrick <notifications@github.com>
- Date: Tue, 15 Aug 2017 09:41:54 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/140/322520819@github.com>
> w3c/css-houdini-drafts#361 was filed to add an example with ES5 class syntax, but it's so far had negative reaction from @domenic Fixed. > the issue of paintWorklet being on Window is covered by w3c/css-houdini-drafts#350 (and w3c/css-houdini-drafts#330) but hasn't yet been edited into the spec Fixed & Fixed. > I wonder if the spec should actually mention border-image-outset in a comment somewhere (as was mentioned in w3ctag#140 (comment)) given that it seems likely to be a common question, although it's not an entirely satisfactory answer given the 9-slice mess you'd have to go through I just pushed an additional example using border-image to the spec. https://drafts.css-houdini.org/css-paint-api/#example-5 It's not *that* bad, but would be nice to have a property as simple as background-image to do this. Might be worth exploring a background-image-outset property within css to do this. I expect we'll also have folks wanting a foreground-image in the future as well. > w3c/css-houdini-drafts#339 is not yet resolved Fixed. > not sure if more discussion is needed on stability of canvas and its references Not sure either. > there doesn't seem to be an issue open covering the comments about filters in w3ctag#140 (comment) Marked https://github.com/w3c/css-houdini-drafts/issues/398 as level 2. As a more meta-comment I think we are lacking a JS representation of filters used in various areas of the platform, as for any sufficiently complex filter, you need to fallback to svg, e.g. ```js ctx.filter = 'svg(#ref)'; // instead of ctx.filter = CSS.filterSet([ CSS.blur(2, 'px'), CSS.halfTone(...)]); // note above is a terrible api, but you get the idea. ``` > conic gradient example still isn't edited in The "arcs" example replaces this now. https://drafts.css-houdini.org/css-paint-api/#example-3 > I don't see an open issue representing the future work on CSSFontFaceValue mentioned in w3ctag#140 (comment) I've marked https://github.com/w3c/css-houdini-drafts/issues/399 as level 2. I think we need the typedOM to settle down a bit, before tackling this. > w3c/css-houdini-drafts#362 is still open Closed. > w3c/css-houdini-drafts#326 is still open Closed. > w3c/css-houdini-drafts#327 is still open Closed. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/140#issuecomment-322520819
Received on Tuesday, 15 August 2017 16:42:16 UTC