-
Notifications
You must be signed in to change notification settings - Fork 16
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
Temporarily suspend interactivity if layer is not "on top" #391
Comments
I think this would be a bit unfortunate though as it'd be quite limiting on both authors and users. e.g. if the author wants to display 2 sets of layers with markers I assume only 1 set of markers would be interactive even if both sets are visible. Users would have to toggle layers to be able to interact with the otherwise non-interactive markers. And maybe that's fine in a polyfill, or it's expected of us to solve things like this... With the risk of complicating things - my specialty - I wonder if we can hack this using .mapml-layer {
mix-blend-mode: multiply;
} No
|
In the PR instead of only making the top layer interactive, it just checks for a queryable layer on top, if it has one then the layer losses intractability, if not then it remains interactive even if there are other layers on top, as long as the feature is visible and clicked it'll follow the feature link rules. |
When adding templated layer of whatever type, layers with vector data lower in the z-order currently retain their interactivity, such as links and popups.
This issue is to discuss how to handle interactivity in lower (non-top) layers.
I think it would add coherence to the product if we applied the "only the top layer can be queryable OR interactive" rule, so that only the top most layer can be interactive, regardless of whether it's feature data or queryable imagery.
In a native code implementation, we'll hopefully see, perhaps interactivity could be determined at the graphics level: whatever layer rendered the final topmost value of a pixel could get to make that pixel interactive.
The text was updated successfully, but these errors were encountered: