Path to v1.0.0?

[Malvoz]

Do we have any certain expectations for a v1.0.0? Do users? (see https://semver.org/#how-do-i-know-when-to-release-100)

Would the following list be a reasonable goal?

• Fix bugs
• Ensure Web Platform Compatibility
  • w3c-tag-advice-for-polyfill-authors.md
  • w3c-tag-guidelines-web-compatible-components.md
• Accessibility and inclusivity (especially pan and zoom, feature navigation)
• Meet i18n requirements
• Note on which browsers are supported (from which version). Here's a nice example (we can use https://github.com/alrra/browser-logos).

Maybe we could ask in the Gitter chat for feedback?

[prushforth]

I had thought to capture the path to 1.0.0 as a project, would be interested in your views.

Ideally a 1.0.0 release would be the polyfill, with associated WPT that could be submitted as a PR to WHATWG HTML spec.

I was trying to express the features that I thought should be in a 1.0.0 polyfill in that project, but I am willing to negotiate :-).

[Malvoz]

BTW, we don't have the capability to add map markers without <map><area>, correct? Is that an issue? 😅

[prushforth]

I believe <feature><geometry><point>... should work. But it is not a great implementation as yet anyway, even if it "works".

[prushforth]

@Malvoz you made me curious to see if it was working still, and sure enough, bugs. I'll log an issue. Shouldn't be hard to fix.

[prushforth]

I created a 1.0.0 milestone. Let's discuss what should be assigned to 1.0.0 here, and we can update the description as required.

[prushforth]

We probably need intermediate release milestones FWIW.

[prushforth]

We probably need intermediate release milestones FWIW.

I believe that to get to 1.0, we need to refactor the vocabulary to be fully implemented as custom elements. As a first step, I think we should do that without trying to add functionality - simply refactor both the code and the tests, potentially adding tests to implement a DOM API.

Having achieved that, I think we'll be in a position to create Web Platform Tests. WPT, as I understand them, test browser interoperability for a given vocabulary, without delving into the internal representations (which in the case of our custom elements are Leaflet internal abstractions).

Once there, we could go in any direction, I think: add new abstractions and functionality, pursue HTML Standard integration, or iterate again, promote widespread usage etc.

With that in mind, I had created another milestone, Implement MapML vocabulary as custom elements, which I think we should focus on to the extent possible in Winter 2023.

Notwithstanding the above, we can add stuff to 1.0 here as required.