-
Notifications
You must be signed in to change notification settings - Fork 12
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
Questions about UA-provided controls (<map controls>) #88
Comments
We haven't done developer surveys, if that's what you mean. On the other hand, I think it's safe to assume that the UA-provided controls would not be adequate for all use cases, and would likely need to be customizable, somehow. Initially I had anticipated that we would allow the dev to turn them all off, or all on, via the controls boolean attribute. They could then re-create all the controls they wanted via methods similar (I believed) to what was the standard way for
Good question. Needs discussion.
I don't think so.
I don't think so, but, they should be replaceable though, and the replacements would have to be styleable in the usual way. I was thinking we could specify another attribute for that would "freeze" it (so it wouldn't pan or zoom). The user could put custom controls in that layer if they wished, using CSS grid or something like that. The controls would have to be able to listen for map and layer events, I suppose like any other HTML elements. In this way, the user agent wouldn't necessarily be on the hook to implement every last control that is conceivable, or specific to a particular layer type, and so on. |
There is a WICG issue about potentially enabling customizing default controls for video. But relying on the ControlsList API as currently defined may be insufficient (as ControlsList doesn't deal with positioning of controls). It should be noted that there are vendor-prefixed CSS pseudo-elements that allow for styling the default controls for I think it'd make most sense to authors and implementers that whatever method the web platform ends up with that would enable (true) customization for |
I think we can quite confidently say at least:
These controls are expected, and can be removed from the exposed UI using the Controls to pan may be important for users who cannot perform drag/swipe gestures (see WCAG Understanding Success Criterion 2.5.1: Pointer Gestures & technique G215 for more info), however it seems most frameworks do not provide this by default, likely due to the fact that they'd take up a lot of real estate in the map viewer (would require separate buttons to pan in each direction). |
Is there any indication about whether web developers would be satisfied with using UA-provided controls for maps? Which controls are UAs expected to provide? Should these be stylable? Can they be extended?
It might be worth investigating lessons learnt from
video
.The text was updated successfully, but these errors were encountered: