Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(codegen): slider support #29087

Merged
merged 2 commits into from
Feb 1, 2024

Conversation

ruifigueira
Copy link
Contributor

This PR adds support for range slider inputs.

It handles the special case of webkit, which triggers a click event with the body element as target when sliding the input element. For that reason, I skip the click handling event if the hovered element is a range input, without consuming it.

In my first approach (#28767) I was naive and assumed that click events should have the same target element as the current hovered element, and that caused the regression reported in #29067. Sorry about that 😔

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

@ruifigueira ruifigueira force-pushed the feat/record-slider branch 2 times, most recently from a3bff1d to 3da9702 Compare January 23, 2024 23:15

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This handles scenarios where the current hovered element in recorder may not correspond to the event target.

See: microsoft#29067 (comment)
Copy link
Contributor

github-actions bot commented Feb 1, 2024

Test results for "tests 1"

1 failed
❌ [playwright-test] › watch.spec.ts:564:5 › should run CT on changed deps

2 flaky ⚠️ [chromium] › library/tracing.spec.ts:243:5 › should not include trace resources from the previous chunks
⚠️ [webkit] › library/tracing.spec.ts:243:5 › should not include trace resources from the previous chunks

21250 passed, 577 skipped
✔️✔️✔️

Merge workflow run.

@pavelfeldman pavelfeldman merged commit b88a008 into microsoft:main Feb 1, 2024
29 of 30 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants