Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Capability: Get the bounds of a map #60

Open
NickFitz opened this issue Jun 14, 2019 · 2 comments
Open

Capability: Get the bounds of a map #60

NickFitz opened this issue Jun 14, 2019 · 2 comments
Labels
discussion: capability a specific capability or feature: should it be included? what details? should it be a requirement? section: client-side API Capabilities & use cases for client-side APIs status: placeholder there's a matching section heading / some text in the report, but it's far from complete

Comments

@NickFitz
Copy link
Contributor

NickFitz commented Jun 14, 2019 •
edited
Loading

This issue is for discussion of the required API capability “Get the bounds of a map”.
@NickFitz NickFitz added discussion: capability a specific capability or feature: should it be included? what details? should it be a requirement? status: placeholder there's a matching section heading / some text in the report, but it's far from complete section: client-side API Capabilities & use cases for client-side APIs labels Jun 14, 2019
@prushforth
Copy link
Member

prushforth commented Jun 24, 2020 •
edited
Loading

The bounds of a map would likely be the union of the bounds of its layers. We're talking about how to provide a read-only <layer> extent property.

@prushforth prushforth mentioned this issue Jun 24, 2020
Closed
@prushforth prushforth changed the title Capability: Get the bounds of a map Capability: Get the extent of a map Jul 16, 2020
@prushforth prushforth changed the title Capability: Get the extent of a map Capability: Get the bounds of a map Jul 16, 2020
@prushforth
Copy link
Member

prushforth commented Jul 16, 2020 •
edited
Loading

Sorry shouldn't have changed the name of someone else's issue, so I changed it back. We are interpreting "bounds" in a particular way / meaning in the polyfill work, and we are returning <layer->.extent property, which has semantics defined by us.

This was referenced Jul 22, 2020
Open
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion: capability a specific capability or feature: should it be included? what details? should it be a requirement? section: client-side API Capabilities & use cases for client-side APIs status: placeholder there's a matching section heading / some text in the report, but it's far from complete
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@NickFitz @prushforth