-
Notifications
You must be signed in to change notification settings - Fork 235
Open
Labels
APIIssues or PRs involving API changesIssues or PRs involving API changesComponent: OverlayDocumentationIssues or PRs involving changes to documentation or documentation websiteIssues or PRs involving changes to documentation or documentation websiteSEV missingNeeds severity classificationNeeds severity classification
Description
Code of conduct
- I agree to follow this project's code of conduct.To pick up a draggable item, press the space bar. While dragging, use the arrow keys to move the item. Press space again to drop the item in its new position, or press escape to cancel.
Impacted component(s)
overlay-trigger
Expected behavior
I can listen to sp-closed on overlay-trigger and only get close events for that trigger
Actual behavior
If I use sp-action-menu or sp-picker in the overlay rendered by overlay-trigger, closing these menus also triggers sp-closed for the outer menu. It does look like I can match the event.target to the original trigger button, but I could see this really throwing people for a loop.
How can we reproduce this issue?
I can look at getting a simpler reproduction when I have a bit more time.
Metadata
Metadata
Assignees
Labels
APIIssues or PRs involving API changesIssues or PRs involving API changesComponent: OverlayDocumentationIssues or PRs involving changes to documentation or documentation websiteIssues or PRs involving changes to documentation or documentation websiteSEV missingNeeds severity classificationNeeds severity classification
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
adixon-adobe commentedon Apr 12, 2024
I'm not really sure if another event or better documentation is the right approach here, but it was tricky to figure this out, and I'm curious how this would work for manually triggered overlays as well.
adixon-adobe commentedon Apr 12, 2024
As I think about this more, I think what I'm really asking for is an event that doesn't bubble. I just want to know if this overlay opened or closed. Using the same (bubbling) event that the overlay system gets confusing because it's less common, and surprising when you run into it.
So ideally there's be another event that doesn't bubble, which when documented should make the difference in behavior very clear. And all that said, I won't be too offended if you decide it's just simpler to improve the documentation. Just pointing out that this can be a real surprising gotcha.
Westbrook commentedon Apr 12, 2024
Some quick documentation points:
overlayproperty on these eventsnajikahalsema commentedon May 22, 2024
@adixon-adobe Does the above comment from Westbrook give you a path forward?