-
Notifications
You must be signed in to change notification settings - Fork 192
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
[Bug]: No tray behavior with sp-action-menu on Android #2575
Comments
@HenryPing have you been able to confirm this state in the context of an actual device? I'd be interested in knowing if this is failing on |
@Westbrook Yes, it is on the actual device. I used Vysor to mirror the device screen to my desktop to make it easier to take screen shot & video. My android device info: |
Shared this info to https://bugs.chromium.org/p/chromium/issues/detail?id=1384181 |
It seems like the bug was addressed per this comment on Friday. Perhaps we can test the latest version of Chromium on Android and see if this is still reproducible? @HenryPing |
Chromium/Android has since shipped updates that should normalize this delivery context. |
Code of conduct
Impacted component(s)
ProjectX
Expected behavior
On Mobile, sp-action-menu is supposed to display its menu items within in tray from the bottom of the screen.
Actual behavior
No tray, instead, sp-action-menu display its menu items within in popover style on Android as it does on desktop. This happens in both ProjectX shell app on Android and Chrome browser on Android.
More details/discussion can be seen at this Slack thread:
https://cclight.slack.com/archives/CESK60MQD/p1662762810680189
Screenshots
![Screen Shot 2022-09-12 at 3 29 55 PM](https://user-images.githubusercontent.com/1392203/189769878-7ac20a0a-fe82-4f1c-a02a-17d33f650d53.png)
![Uploading Screen Shot 2022-09-12 at 3.29.55 PM.png…]()What browsers are you seeing the problem in?
Chrome
How can we reproduce this issue?
There are 2 ways:
ProjectX on Android
Chrome on Android:
Sample code that illustrates the problem
No response
Logs taken while reproducing problem
No response
The text was updated successfully, but these errors were encountered: