-
Notifications
You must be signed in to change notification settings - Fork 205
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
chore(picker): added a new interaction strategy #4396
Conversation
Tachometer resultsChromeaction-menu permalinktest-basic
test-directive permalink
test-lazy permalink
test-open-close-directive permalink
test-open-close permalink
combobox permalinkbasic-test
light-dom-test permalink
menu permalinktest-basic
picker permalinkbasic-test
split-button permalinkbasic-test
Firefoxaction-menu permalinktest-basic
test-directive permalink
test-lazy permalink
test-open-close-directive permalink
test-open-close permalink
combobox permalinkbasic-test
light-dom-test permalink
menu permalinktest-basic
picker permalinkbasic-test
split-button permalinkbasic-test
|
a5d671b
to
106aa6c
Compare
106aa6c
to
757b90e
Compare
Lighthouse scores
What is this?Lighthouse scores comparing the documentation site built from the PR ("Branch") to that of the production documentation site ("Latest") and the build currently on Transfer Size
Request Count
|
814916d
to
28a86be
Compare
@spdev3000 Need your eyes on these failing tests as I'm trying to separate out the interaction strategy from the |
I can only see that in the Storybook the Picker opens twice after the first loading and usage. Can you also pls add 2 new stories to the tests, testing each (desktop and mobile) use case? Is this somehow possible with test framework? |
It appears that the issue may be caused by a race condition related to the Could you please perform a thorough review of this branch on your local setup to help identify and resolve the issue? Thank you! |
I debugged into the issue and as far as I can see the problem seems to be that at second (and any further) calls to
so that function could look like:
|
c895143
to
f3e64e9
Compare
68641bd
to
aaef850
Compare
aaef850
to
b163d0c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
bcc18dd
bcc18dd
to
7f051a3
Compare
* chore: testing a click controller strategy for picker component * chore: testing a new interaction strategy for picker * fix: separated interaction strategy for picker * chore: updated the strategy to include the dependency controller * chore: updated open condition in interactioncontroller * chore(picker): removed double event handling from action menu * chore: added slottable-request handling in interactionController * chore: change trigger button for split-button * chore: updated split-button test * chore: fixed conflicts after merging main * chore: updated action-group test to remove flakiness * chore: refractored interaction controller code * chore: added delay for click event tests * chore: added hacky mobile tests for mobilecontroller picker * chore: removed unexpected only from picker responsive test * chore: updated menu interaction model * chore: don't dispatch synthetic click event on menu selection * chore: removed split-button tests cz its deprecated --------- Co-authored-by: Michael Jordan <mijordan@adobe.com>
* chore: testing a click controller strategy for picker component * chore: testing a new interaction strategy for picker * fix: separated interaction strategy for picker * chore: updated the strategy to include the dependency controller * chore: updated open condition in interactioncontroller * chore(picker): removed double event handling from action menu * chore: added slottable-request handling in interactionController * chore: change trigger button for split-button * chore: updated split-button test * chore: fixed conflicts after merging main * chore: updated action-group test to remove flakiness * chore: refractored interaction controller code * chore: added delay for click event tests * chore: added hacky mobile tests for mobilecontroller picker * chore: removed unexpected only from picker responsive test * chore: updated menu interaction model * chore: don't dispatch synthetic click event on menu selection * chore: removed split-button tests cz its deprecated --------- Co-authored-by: Michael Jordan <mijordan@adobe.com>
* chore: testing a click controller strategy for picker component * chore: testing a new interaction strategy for picker * fix: separated interaction strategy for picker * chore: updated the strategy to include the dependency controller * chore: updated open condition in interactioncontroller * chore(picker): removed double event handling from action menu * chore: added slottable-request handling in interactionController * chore: change trigger button for split-button * chore: updated split-button test * chore: fixed conflicts after merging main * chore: updated action-group test to remove flakiness * chore: refractored interaction controller code * chore: added delay for click event tests * chore: added hacky mobile tests for mobilecontroller picker * chore: removed unexpected only from picker responsive test * chore: updated menu interaction model * chore: don't dispatch synthetic click event on menu selection * chore: removed split-button tests cz its deprecated --------- Co-authored-by: Michael Jordan <mijordan@adobe.com>
Abstracted a new interaction strategy for Picker. This will allow our picker to be stateless and handle all the interactions through a separate
mobile
anddesktop
controllers instead.Related issue(s)
Motivation and context
How has this been tested?
Screenshots (if appropriate)
Types of changes
Checklist
Best practices
This repository uses conventional commit syntax for each commit message; note that the GitHub UI does not use this by default so be cautious when accepting suggested changes. Avoid the "Update branch" button on the pull request and opt instead for rebasing your branch against
main
.