-
Notifications
You must be signed in to change notification settings - Fork 235
chore(picker): fix for overlaid picker in mobile #3835
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
Conversation
Tachometer resultsChromeaction-menu permalink
picker permalink
split-button permalink
Firefoxaction-menu permalink
picker permalink
split-button permalink
|
|
https://96f1ac07a365f3271d6365f89114585a--spectrum-web-components.netlify.app/review/ This is an unexpected failure. We should confirm that your change didn’t cause this or if there’s a change to the timing of the test/element that is needed. |
03929b6 to
639d30d
Compare
I dont think this is failing due to change in type. I verified in a test PR. I can see the same VRT failures |
packages/picker/src/Picker.ts
Outdated
| public placement: Placement = 'bottom-start'; | ||
|
|
||
| @property() | ||
| public overlayType: OverlayTypes = 'auto'; |
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.
Should we update documentation somewhere on this property? I feel like the isMobile check where it changes to modal is a potential surprise to consumers. Can we also add/update any documentation for this property to communicate what it does?
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.
I wasn’t clear about what I was hoping with this. I do not believe the user should have any control over this value.
However, we should be binding it to the sp-overlay as a property .type=${…} now that is dynamic so that it does not request paint/layout when changing unless required.
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.
Adding as .type=${this.isMobile.matches ? 'modal' : 'auto'}
|
Please share why you think the change I referred to is not caused by this PR. |
@Westbrook I dont find any visual differences on the first load of PR storybook and PROD storybook Also I see all pass on the local VRT test on my branch for Picker. Seems like the VRT test is not picking up the hover state on picker items on CI |
e1ff6eb to
cfd5c6d
Compare
|
@Westbrook Mission Accomplished!! |
Westbrook
left a comment
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.
Love it! Thanks for digging in on this one. ![]()
* chore(picker): fix for overlaid picker in mobile * chore: updated golden image cache * chore(picker): fix for overlaid picker in mobile * chore: updated golden image cache * chore(picker): added property for type * chore(picker): added type as a property * chore(picker): removing overlay type as a property * chore(picker): added triiger open decorator for custom picker * chore(picker): reverting golden hash --------- Co-authored-by: Rajdeep Chandra <rajdeepc@adobe.com>
* chore(picker): fix for overlaid picker in mobile * chore: updated golden image cache * chore(picker): fix for overlaid picker in mobile * chore: updated golden image cache * chore(picker): added property for type * chore(picker): added type as a property * chore(picker): removing overlay type as a property * chore(picker): added triiger open decorator for custom picker * chore(picker): reverting golden hash --------- Co-authored-by: Rajdeep Chandra <rajdeepc@adobe.com>

Description
type=autowas taking up the root dialog component as its parent and rendering thesp-trayconsidering dialog as its root instead of the DOM.Related issue(s)
Motivation and context
How has this been tested?
Do this:
picker.stories.tsand try to emulate it in a iphone simulatorwithxcode.Screenshots (if appropriate)
Before Fix:
After Fix:

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.