Malvoz ( Robert Linder )

issue commentMaps4HTML/HTML-Map-Element-UseCases-Requirements

Capability: Animate the re-centering of the map view

@NickFitz It's not possible to close PRs from within an issue, only from other PRs. 😃 Here's the keywords and syntax: https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword

Malvoz

comment created time in 3 hours

pull request commentMaps4HTML/HTML-Map-Element-UseCases-Requirements

Capabilities wip

In the "Related specs" section, I believe we should reference the CSS primitive proposal of "per-element panning and zooming": https://github.com/w3c/csswg-drafts/issues/5275.

NickFitz

comment created time in 3 hours

issue openedMaps4HTML/MapML

Would it be feasible to (re-)use the HTML width and height attributes on the <extent> element:

<extent width="" height="">
  ...
</extent>

as opposed to:

<extent>
  <input type="width" ...>
  <input type="height" ...>
   ...
</extent>

?

created time in 11 hours

startedeeeps/responsive-image-client-hints

started time in 13 hours

PublicEvent

issue openedMaps4HTML/chat

Web map tools accessibility evaluation

I have manually evaluated the accessibility support of the reviewed web map tools. While I don't consider the evaluation report complete, my intention is to open bug reports to get the attention of the web map tools' authors. I'm not an accessibility expert, though I have studied WAI-ARIA for some time, and have read the WCAG Evaluation Methodology. It hasn't been an easy task to interpret all the WCAG documentation, so I'd appreciate any feedback.

Here it is: web-maps-wcag-evaluation.

/cc @Maps4HTML/contributors

created time in a day

Pull request review commentMaps4HTML/Web-Map-Custom-Element

Extends the <map> api and adds a context menu to map which makes use of the api

   border-top: 1px solid transparent;   border-bottom: 1px solid transparent;   cursor: default;-  outline: none;

It should be possible to make it a popup submenu...

<details><summary>I think</summary>

<style>
.mapml-contextmenu {
  position: absolute;
  width: 150px;
  left: 150px;
}

.mapml-contextmenu details[open] .mapml-submenu {
  position: absolute;
  top: 0;
  width: 120px;
  transform: translate(-120px, 0);
}

/* Remove default disclosure widget (https://developer.mozilla.org/en-US/docs/Web/HTML/Element/details#Customizing_the_disclosure_widget) */
.mapml-contextmenu summary {
  display: inline-block;
  list-style: none;
}
.mapml-contextmenu ::-webkit-details-marker {
  display: none;
}

/* Presentational, ignore these. */
map {
  contain: content;
  display: inline-block;
  overflow: hidden;
  height: 150px;
  width: 300px;
  border-width: 2px;
  border-style: inset;
}
.mapml-contextmenu,
.mapml-submenu {
  border: 2px dotted black;
}
.mapml-contextmenu-item {
  color: #222;
  cursor: default;
  text-decoration: none;
}
</style>
<map>
  <div class="mapml-contextmenu">
    <a class="mapml-contextmenu-item" href="#" role="button">item 1</a>
    <details class="mapml-contextmenu-item has-mapml-submenu">
      <summary>item 2</summary>
      <div class="mapml-submenu">
        <a class="mapml-contextmenu-item" href="#" role="button">item 2.1</a>
      </div>
    </details>
    <a class="mapml-contextmenu-item" href="#" role="button">item 3</a>
  </div>
</map>

</details>

<details> is just nice because it has built in accessibility. Otherwise, the WAI-ARIA Authoring Practices has a set of established patterns, such as buttons (i.e. the menu items <a role="button">) and their recommended keyboard interactions, and menu button (i.e. the menu items which opens submenus) which might be helpful.

ahmadayubi

comment created time in a day

push eventMalvoz/Web-Map-Custom-Element

Peter Rushforth

commit sha 2edf1b110ab81d7b67c896a8ee7344a3f4ec3dd6

Migrate to travis-ci.com (#123)