Mapping in HTML – A Proposal for a New Element • Hacker News Board

Mapping in HTML – A Proposal for a New Element

#1

Post by ateesdalejr » Thu, Oct 26, 2017, 9:12 PM UTC

Mapping in HTML – A Proposal for a New Element
shkspr.mobi

Re: Mapping in HTML – A Proposal for a New Element

#2

Post by Operyl » Thu, Oct 26, 2017, 9:43 PM UTC

Ok, so you’re forcing the browser to use their own implementation of it. But google charges for their mapping APIs, and I doubt they’d want to use something like the various open source map tiles in chrome.

Re: Mapping in HTML – A Proposal for a New Element

#3

Post by ricardobeat » Thu, Oct 26, 2017, 9:43 PM UTC

This is the exact use case for web components, except it doesn’t require browsers shipping their own implementation and updates - it’s all in userland.

Example: https://www.webcomponents.org/element/keanulee/good-map

Re: Mapping in HTML – A Proposal for a New Element

#4

Post by dang » Thu, Oct 26, 2017, 10:03 PM UTC

Please don't put Show HN on blog posts or things you didn't make.

https://news.ycombinator.com/showhn.html

Re: Mapping in HTML – A Proposal for a New Element

#5

Post by j4ybee » Thu, Oct 26, 2017, 10:13 PM UTC

A long time ago, in a galaxy far, far away, I worked with some guys who put together an incredible proposal to ICANN for a new .geo TLD: http://www.ai.sri.com/dotgeo/

The proposal was not accepted, but .aero and .museum were, and we all now how those have since utterly revolutionized the internet.

Re: Mapping in HTML – A Proposal for a New Element

#6

Post by aphextron » Thu, Oct 26, 2017, 10:14 PM UTC

ricardobeat wrote: post #3

This is the exact use case for web components, except it doesn’t require browsers shipping their own implementation and updates - it’s all in userland. Example: https://www.webcomponents.org/element/keanulee/good-map

Agreed. There should (and probably will) never be another new element added to the spec after HTML5.

Re: Mapping in HTML – A Proposal for a New Element

#7

Post by betenoire » Thu, Oct 26, 2017, 10:18 PM UTC

If this is just "contact us" style maps, I couldn't agree more.

But what good is a map that I can't customize to my use cases, to make it useful in my web app? How would I say, suggest restaurants nearby?

Re: Mapping in HTML – A Proposal for a New Element

#8

Post by shabbyrobe » Thu, Oct 26, 2017, 10:21 PM UTC

j4ybee wrote: post #5

A long time ago, in a galaxy far, far away, I worked with some guys who put together an incredible proposal to ICANN for a new .geo TLD: http://www.ai.sri.com/dotgeo/ The proposal was not accepted, but .aero and .museum were, and we all now how those have since utterly revolutionized the internet.

Neat! Speaking of galaxy far, far away, the executive summary only mentions other planets in passing. I couldn't quite grok from scanning how you might access cells from the moon with this TLD.

.aero may be questionable, but surely the boundless usefulness of .ninja or .moe isn't in dispute?

Re: Mapping in HTML – A Proposal for a New Element

#9

Post by maxerickson » Thu, Oct 26, 2017, 10:22 PM UTC

aphextron wrote: post #6

ricardobeat wrote: post #3

This is the exact use case for web components, except it doesn’t require browsers shipping their own implementation and updates - it’s all in userland. Example: https://www.webcomponents.org/element/keanulee/good-map

Agreed. There should (and probably will) never be another new element added to the spec after HTML5.

Is the living standard aspect of WHATWG dead then?

Re: Mapping in HTML – A Proposal for a New Element

#10

Post by maxerickson » Thu, Oct 26, 2017, 10:23 PM UTC

betenoire wrote: post #7

If this is just "contact us" style maps, I couldn't agree more. But what good is a map that I can't customize to my use cases, to make it useful in my web app? How would I say, suggest restaurants nearby?

Presumably by dynamically adding (and styling) markers.