Re: [blink-dev] Intent to Ship: ContentVisibilityAutoStateChanged event

['Vladimir Levin' via blink-dev]

Hi all,

CSSWG resolved on renaming this event to be in the present tense:
ContentVisibilityAutoStateChangeEvent instead of
ContentVisibilityAutoStateChangedEvent
(https://github.com/w3c/csswg-drafts/issues/7603#issuecomment-1309133575)

This is currently in the Beta channel (m108). According to
https://chromestatus.com/metrics/feature/popularity#ContentVisibilityAutoStateChangedHandlerRegistered
there's 0.0191% usage of this (event handler being registered), although
the timeline view doesn't show any data.

I would like to rename the event, and attempt to merge this to beta. I will
also reach out to partners that we worked with for this event to ensure
they are aware of this change.

Please let me know if there are concerns with this plan.

Thanks,
Vlad

On Wed, Aug 31, 2022 at 11:39 AM Philip Jägenstedt 
wrote:

> LGTM3 on the assumption that the spec discussion will be sorted out and
> spec fixed by the time this rolls out to stable.
>
> On Wed, Aug 31, 2022 at 3:47 PM Yoav Weiss  wrote:
>
>> LGTM2 conditional on driving the discussion on the Mozilla position
>> thread to completion and making sure the spec text properly reflects it.
>>
>> On Thu, Aug 11, 2022 at 12:48 AM slightlyoff via Chromestatus <
>> admin+slightly...@cr-status.appspotmail.com> wrote:
>>
>>> LGTM1
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "blink-dev" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to blink-dev+unsubscr...@chromium.org.
>>> To view this discussion on the web visit
>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/5788c005e5ead850%40google.com
>>> 
>>> .
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "blink-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to blink-dev+unsubscr...@chromium.org.
>> To view this discussion on the web visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfU%3DV6M7KXYdwwWm_RFyzH7APA8pymm3_eno3ep7SCNgCg%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to blink-dev+unsubscr...@chromium.org.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYfUH%2B2XfktP%2BzOPyL5Q6CMP82Q4dTPG6BqHuDWbTTkHxQ%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADsXd2NjwAVNVGdtoyJ2q0hru0acBnfa2T8POaHK2pK1gwgOUA%40mail.gmail.com.

Re: [blink-dev] Intent to Ship: ContentVisibilityAutoStateChanged event

[Philip Jägenstedt]

LGTM3 on the assumption that the spec discussion will be sorted out and
spec fixed by the time this rolls out to stable.

On Wed, Aug 31, 2022 at 3:47 PM Yoav Weiss  wrote:

> LGTM2 conditional on driving the discussion on the Mozilla position thread
> to completion and making sure the spec text properly reflects it.
>
> On Thu, Aug 11, 2022 at 12:48 AM slightlyoff via Chromestatus <
> admin+slightly...@cr-status.appspotmail.com> wrote:
>
>> LGTM1
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "blink-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to blink-dev+unsubscr...@chromium.org.
>> To view this discussion on the web visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/5788c005e5ead850%40google.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to blink-dev+unsubscr...@chromium.org.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfU%3DV6M7KXYdwwWm_RFyzH7APA8pymm3_eno3ep7SCNgCg%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYfUH%2B2XfktP%2BzOPyL5Q6CMP82Q4dTPG6BqHuDWbTTkHxQ%40mail.gmail.com.

Re: [blink-dev] Intent to Ship: ContentVisibilityAutoStateChanged event

[Yoav Weiss]

LGTM2 conditional on driving the discussion on the Mozilla position thread
to completion and making sure the spec text properly reflects it.

On Thu, Aug 11, 2022 at 12:48 AM slightlyoff via Chromestatus <
admin+slightly...@cr-status.appspotmail.com> wrote:

> LGTM1
>
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to blink-dev+unsubscr...@chromium.org.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/5788c005e5ead850%40google.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfU%3DV6M7KXYdwwWm_RFyzH7APA8pymm3_eno3ep7SCNgCg%40mail.gmail.com.

Re: [blink-dev] Intent to Ship: ContentVisibilityAutoStateChanged event

[slightlyoff via Chromestatus]

LGTM1

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/5788c005e5ead850%40google.com.

Re: [blink-dev] Intent to Ship: ContentVisibilityAutoStateChanged event

[Vladimir Levin]

Thanks for pointing this out. I've updated the explainer to reflect the
discussion we had on a11y.

Thanks,
Vlad

On Wed, Aug 10, 2022 at 8:57 AM Manuel Rego Casasnovas 
wrote:

>
> On 08/08/2022 20:48, Vladimir Levin wrote:
> > Explainer
> >
> >
> https://github.com/vmpstr/web-proposals/blob/main/explainers/cv-auto-event.md
> > <
> https://github.com/vmpstr/web-proposals/blob/main/explainers/cv-auto-event.md
> >
>
> Should we update the explainer to update on the a11y concerns raised at
> https://github.com/w3c/csswg-drafts/issues/7384#issuecomment-1189938042
>
> The explainer explicitly mentions:
> "For example, the developer may want to stop React updates in a subtree
> that is not rendered by the user-agent."
>
> Which seems not a good idea according to the discussion linked above.
>
> Cheers,
>   Rego
>
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to blink-dev+unsubscr...@chromium.org.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/93e41d83-a388-44f4-4456-77aeb87f3821%40igalia.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADsXd2M1uUZbxiLoc5TcNQMO-o75mc8UhjuW4YCuJQcz6nc4qw%40mail.gmail.com.

Re: [blink-dev] Intent to Ship: ContentVisibilityAutoStateChanged event

[Manuel Rego Casasnovas]

On 08/08/2022 20:48, Vladimir Levin wrote:
> Explainer
> 
> https://github.com/vmpstr/web-proposals/blob/main/explainers/cv-auto-event.md
> 

Should we update the explainer to update on the a11y concerns raised at
https://github.com/w3c/csswg-drafts/issues/7384#issuecomment-1189938042

The explainer explicitly mentions:
"For example, the developer may want to stop React updates in a subtree
that is not rendered by the user-agent."

Which seems not a good idea according to the discussion linked above.

Cheers,
  Rego

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/93e41d83-a388-44f4-4456-77aeb87f3821%40igalia.com.

[blink-dev] Intent to Ship: ContentVisibilityAutoStateChanged event

[Vladimir Levin]

Contact emailsvmp...@chromium.org

Explainer
https://github.com/vmpstr/web-proposals/blob/main/explainers/cv-auto-event.md

Specification
https://drafts.csswg.org/css-contain-2/#content-visibility-auto-state-changed

Summary

This proposal is to add an event that would fire on a content-visibility:
auto element when the rendering state of the element changes due to any of
the attributes that make the element relevant to the user (
https://www.w3.org/TR/css-contain-2/#relevant-to-the-user)

Blink componentBlink


TAG reviewhttps://github.com/w3ctag/design-reviews/issues/756

TAG review statusIssues addressed

Risks


Interoperability and Compatibility

This is a new feature that enhances `content-visibility: auto` use. It
poses minimal interop and compat risks, and can be feature detected and
polyfilled


*Gecko*: Under consideration (
https://github.com/mozilla/standards-positions/issues/664)

*WebKit*: No signal (https://github.com/WebKit/standards-positions/issues/33
)

*Web developers*: Positive (
https://github.com/w3c/csswg-drafts/issues/7384#issuecomment-1182039257)

*Other signals*:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that
it has potentially high risk for Android WebView-based applications?

No


Debuggability

This feature can be debugged similarly to other events


Will this feature be supported on all six Blink platforms (Windows, Mac,
Linux, Chrome OS, Android, and Android WebView)?Yes

Is this feature fully tested by web-platform-tests

?Yes

Flag nameContentVisibilityAutoStateChangedEvent

Requires code in //chrome?False

Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1343432

MeasurementContentVisibilityAutoStateChangedHandlerRegistered use counter
(patch in progress)

Non-OSS dependencies

Does the feature depend on any code or APIs outside the Chromium open
source repository and its open-source dependencies to function?
No

Estimated milestones

106

Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5179553291436032

Links to previous Intent discussionsIntent to prototype:
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADsXd2NdBBy0u5mfoErwy5FOUetVAmAXWB%2B1EmjNnFwZ0QH8%2Bw%40mail.gmail.com



This intent message was generated by Chrome Platform Status
.

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADsXd2P4sAKcbyx9UFUxKkzcucKw5MMEtPw0gDn0x49WxcSQUg%40mail.gmail.com.