Re: [blink-dev] Re: Intent to deprecate: SMIL

Thanks Lorand for updating the MDN page in this commit <https://github.com/mdn/content/commit/b68049936ef4d1328e07065eafc87e3e43e826af> . On Wednesday, December 20, 2023 at 1:14:48 PM UTC-8 Philip Rogers wrote: > I'll see if I can get the MDN page updated. > > SMIL usage h

Re: [blink-dev] Re: Intent to deprecate: SMIL

rd for the SVG > animations so for who builds projects with it, it's very important to have > no worries about a possible future deprecation. > > Thank you. > Andrea Monzini > > [1] https://caniuse.com/svg-smil > [2] https://www.chromestatus.com/metrics/feature/timeline/popular

[blink-dev] Web-Facing Change PSA: Improved CSS masking for SVG

Contact email...@opera.com Specificationhttps://drafts.fxtf.org/css-masking/#positioned-masks Summary This is a follow-on to the improved CSS mask support in chromium 120 ( https://chromestatus.com/feature/5839739127332864) and adds new mask support to SVG (multiple masks, as well as mask-mode,

Re: [blink-dev] Intent to Ship: CSS masking

On Wednesday, October 25, 2023 at 7:24:34 AM UTC-7 Mike Taylor wrote: On 10/25/23 10:00 AM, Philip Rogers wrote: Contact emails p...@chromium.org, tca...@chromium.org, yo...@chromium.org, f...@opera.com Explainer None Specification https://drafts.fxtf.org/css-masking/#positioned-masks

[blink-dev] Intent to Ship: CSS masking

Contact emails...@chromium.org, tcap...@chromium.org, yo...@chromium.org, f...@opera.com ExplainerNone Specificationhttps://drafts.fxtf.org/css-masking/#positioned-masks Design docshttps://developer.mozilla.org/en-US/docs/Web/CSS/mask Summary CSS mask, and related properties such as

[blink-dev] Intent to Prototype: CSS Masking

Contact emails...@chromium.org, tcap...@chromium.org, yo...@chromium.org Specificationhttps://www.w3.org/TR/css-masking-1 Design docs https://developer.mozilla.org/en-US/docs/Web/CSS/mask Summary CSS mask, and related properties such as mask-image, mask-mode, etc, are used to hide an element

Re: [blink-dev] Intent to Prototype and Ship: Clip-path xywh() and rect() values

On Friday, September 15, 2023 at 1:19:06 PM UTC-7 Mike Taylor wrote: On 9/11/23 7:18 PM, Philip Rogers wrote: Contact emails p...@chromium.org Explainer None Specification https://www.w3.org/TR/css-shapes/#supported-basic-shapes Summary Support the xywh() and rect() values on clip-path

[blink-dev] Re: Intent to Prototype and Ship: Clip-path xywh() and rect() values

Thank you 一丝! I will update the chromestatus entry to reflect WebKit's implementation. On Tue, Sep 12, 2023 at 2:01 AM 一丝 wrote: > WebKit has been implemented here: > - rect() https://github.com/WebKit/WebKit/pull/17619 > - xywh() https://github.com/WebKit/WebKit/pull/17087 > > 在2023年9月12日星期二

[blink-dev] Intent to Prototype and Ship: Clip-path xywh() and rect() values

Contact emails...@chromium.org ExplainerNone Specificationhttps://www.w3.org/TR/css-shapes/#supported-basic-shapes Summary Support the xywh() and rect() values on clip-path, which make it easier to specify rectangular or rounded-rectangular clips. Blink componentBlink>Paint

[blink-dev] Intent to Prototype and Ship: Clip-path geometry-box values

Contact emails...@chromium.org ExplainerNone Specificationhttps://drafts.fxtf.org/css-masking/#the-clip-path Summary Clip-path supports values to control the clip's reference box, making clip-path easier to use. These box values can be used alongside basic shapes (for example, clip-path:

[blink-dev] Re: Compositing Reasons

use the Compositing Reasons; > but for my use case I need these layers to be specifically identifiable, so > I was using the attribute. > > On Monday, November 14, 2022 at 1:49:15 PM UTC-8 Philip Rogers wrote: > >> Would it work to just add "will-change: tr

[blink-dev] Re: Compositing Reasons

Would it work to just add "will-change: transform;" (either in the html, or as an implementation detail in blink itself)? This can change paint order because it causes a stacking context, but it's the simplest way to ensure a cc::Layer is created that it set up for moving content. On Monday,

Re: [blink-dev] Intent to Prototype and Ship: Snap border, outline and column-rule widths before layout

On Thursday, September 29, 2022 at 12:17:10 PM UTC-7 Chris Harrelson wrote: > On Thu, Sep 29, 2022 at 12:15 PM Mike Taylor wrote: > >> On 9/28/22 3:01 PM, Traian Captan wrote: >> >> Contact emails >> >> tca...@chromium.org >> >> Explainer >> >> Though not a formal explainer, Emilio has an

Re: [blink-dev] A quick survey on setting up fuzzy match rules to identify resolvable flaky web tests

How much of a problem is flakiness caused by minor pixel differences compared to overall flakiness? I looked at the top 10 flaky tests here and none of them were minor pixel

Re: [blink-dev] Question on getting pixels from blink/renderer/modules/accessibility.

eates a PaintArtifact for a Node out of DraggedNodeImageBuilder and into a helper. This helper could include a comment about how the painting starts from the containing stacking context. > > Best, > Ramin > > On Tue, Jan 11, 2022 at 6:58 PM Philip Rogers wrote: > >> &g

Re: [blink-dev] Question on getting pixels from blink/renderer/modules/accessibility.

alog box? > That's correct: the full-page-crop approach will include content on top of the target content, will not include the target if it is scrolled offscreen, etc. > > On Mon, Jan 10, 2022 at 8:29 PM Philip Rogers wrote: > >> >> >> On Mon, Jan 10, 2022 at

Re: [blink-dev] Question on getting pixels from blink/renderer/modules/accessibility.

t/html,hello world The drag image for the div will only contain white and transparent pixels, and will not be blurred. If you want the purple background too, you'll want to do the full-page-paint+crop approach. > > Best, > Ramin > > On Fri, Jan 7, 2022 at 11:06 PM Philip Rogers w

Re: [blink-dev] Question on getting pixels from blink/renderer/modules/accessibility.

This is a deceptively difficult problem in general. Our paint system uses the CSS definition of paint order which starts painting at stacking contexts and it is challenging to exclude non-stacked siblings of a non-stacked target element. Some other complications are whether ancestor effects/clips