-
Notifications
You must be signed in to change notification settings - Fork 193
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
[Popup] If a fragment anchor is located inside a popup, should it open upon navigation? #315
Comments
This use-case came up in a conversation about popups, and I think that's useful. I can imagine linking to a specific menu-item, for example. But I think the pattern becomes even more useful when applied to more persistent elements like a |
Another similar issue, which might deserve its own issue, was brought up at today's OpenUI meeting: should Find in Page be able to discover the content of a hidden Similar issues are being tackled for |
I agree with @mirisuzanne and think it is useful for popups, An example in the wild: on the WAI Website we have a script that checks if the URL has a fragment identifier and opens the relevant |
I think this issue is fully covered/subsumed by #344. I'm going to close this one. |
For example, here:
Should navigating to the
#foo
or#bar
fragments automatically open the popup?With that behavior, some of the use cases listed in #311 could be declaratively achieved, without needing an
open
attribute.Some corner cases that might be interesting:
==> should navigating to
#anchor
open the popup?==> should only the innermost popup be shown? The issue here is that it won't be visible - it is nested inside another non-shown
<popup>
, which isdisplay:none
.I think the popup stack behavior is pretty clear in this case: navigating to a fragment anchor like this should behave as if
.show()
was called on the relevant popup. So if there's already another popup showing when the navigation happens, the existing popup is closed.@flackr @mirisuzanne @stubbornella
The text was updated successfully, but these errors were encountered: