Boundary* entry_exit,nit: Variable 'entry_exit' is unclear; consider a more descriptive name like 'entry_end' to match 'active_end' and the member variable 'entry_range_end_'. (Blink Style Guide: Naming)
To keep this interaction as brief and non-intrusive as possible, please consider responding with one of following options:
**Done** | **OK But Won't Fix**: reason | **Later**: b/<bug_id> | **Invalid:** reason
_This comment was generated by [Experimental Blink C++ Code Review Agent](http://go/blink-c++-code-review-agent)._
_AI reviews can sometimes be inaccurate; We appreciate your 🙏 feedback 🙏 to help us improve._
_[File a bug](http://go/blink-c++-code-review-agent-feedback) | [Provide feedback on chat](https://chat.google.com/room/AAQA0zhQHe0?cls=4) | [Opt-out](https://ganpati2.corp.google.com/group/peep-genai-blink-agent-optout.prod)_
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
nit: Variable 'entry_exit' is unclear; consider a more descriptive name like 'entry_end' to match 'active_end' and the member variable 'entry_range_end_'. (Blink Style Guide: Naming)
To keep this interaction as brief and non-intrusive as possible, please consider responding with one of following options:
**Done** | **OK But Won't Fix**: reason | **Later**: b/<bug_id> | **Invalid:** reason
_This comment was generated by [Experimental Blink C++ Code Review Agent](http://go/blink-c++-code-review-agent)._
_AI reviews can sometimes be inaccurate; We appreciate your 🙏 feedback 🙏 to help us improve._
_[File a bug](http://go/blink-c++-code-review-agent-feedback) | [Provide feedback on chat](https://chat.google.com/room/AAQA0zhQHe0?cls=4) | [Opt-out](https://ganpati2.corp.google.com/group/peep-genai-blink-agent-optout.prod)_
Done
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
entryRangeEnd: `${TRIGGER_END_PX}px`Does it work if you just set activeRange? Can you make the test do this?
Per the discussion the intention is that developers will just set the active range unless they specifically want to narrow the entry range. See https://github.com/w3c/csswg-drafts/issues/13174#:~:text=primary%20thing%20author%20wants%20to%20set%20is%20active%20range%2C%20don%27t%20want%20to%20set%20an%20entry%20rannge%2C%20then%20entry%20range%20is%20a%20narrowing%20of%20the%20primary%20thing%20they%27re%20setting
primary thing author wants to set is active range, don't want to set an entry rannge, then entry range is a narrowing of the primary thing they're setting
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
// Both are undefined: normal auto.I suppose another option is to leave "auto" in the realm of CSS. I.e. "auto" would only be valid as a CSS value as a way of setting the value of the underlying object `TimelineTrigger` object whose only valid values are the same as `Animation.rangeStart`.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
entryRangeEnd: `${TRIGGER_END_PX}px`Does it work if you just set activeRange? Can you make the test do this?
Per the discussion the intention is that developers will just set the active range unless they specifically want to narrow the entry range. See https://github.com/w3c/csswg-drafts/issues/13174#:~:text=primary%20thing%20author%20wants%20to%20set%20is%20active%20range%2C%20don%27t%20want%20to%20set%20an%20entry%20rannge%2C%20then%20entry%20range%20is%20a%20narrowing%20of%20the%20primary%20thing%20they%27re%20setting
primary thing author wants to set is active range, don't want to set an entry rannge, then entry range is a narrowing of the primary thing they're setting
| Code-Review | +1 |
use_active_range=false) {Personally I think it's better to just ensure you have at least one explicit test that directly tests each type of trigger rather than trying to test every combination of options with parameterization. I.e. given that setting one range implicitly sets the other, other than ensuring that this happens all of the extra assertions are redundant.
entryRangeEnd: `${TRIGGER_END_PX}px`David AwogbemilaDoes it work if you just set activeRange? Can you make the test do this?
Per the discussion the intention is that developers will just set the active range unless they specifically want to narrow the entry range. See https://github.com/w3c/csswg-drafts/issues/13174#:~:text=primary%20thing%20author%20wants%20to%20set%20is%20active%20range%2C%20don%27t%20want%20to%20set%20an%20entry%20rannge%2C%20then%20entry%20range%20is%20a%20narrowing%20of%20the%20primary%20thing%20they%27re%20setting
primary thing author wants to set is active range, don't want to set an entry rannge, then entry range is a narrowing of the primary thing they're setting
Added a test case for this now.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +2 |
Personally I think it's better to just ensure you have at least one explicit test that directly tests each type of trigger rather than trying to test every combination of options with parameterization. I.e. given that setting one range implicitly sets the other, other than ensuring that this happens all of the extra assertions are redundant.
Okay, I think that makes the tests added to `TimelineTrigger/constructor.html` sufficient. I've reverted this change.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Commit-Queue | +2 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Exportable changes to web-platform-tests were detected in this CL and a pull request in the upstream repo has been made: https://github.com/web-platform-tests/wpt/pull/57156.
When this CL lands, the bot will automatically merge the PR on GitHub if the required GitHub checks pass; otherwise, ecosystem-infra@ team will triage the failures and may contact you.
WPT Export docs:
https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md#Automatic-export-process
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[animation-trigger] Rename range boundaries of TimelineTrigger IDLs
This is the last part of the rename resolved[1] on.
[1] https://github.com/w3c/csswg-drafts/issues/13174
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
The WPT PR for this CL has been merged upstream! https://github.com/web-platform-tests/wpt/pull/57156
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |