On 17/01/2021 22:54, Philip Gladstone wrote:
I found the failing commit in openlayers:
git show 886ca26c6ae5
Good digging.
Rather alarmingly it includes the following new section in the README.md
## Supported Browsers
OpenLayers runs on all modern browsers that support
[HTML5](https://html.spec.whatwg.org/multipage/) and [ECMAScript
5](http://www.ecma-international.org/ecma-262/5.1/). This includes Chrome,
Firefox, Safari and Edge.
For older browsers and platforms (Internet Explorer, Android 4.x, iOS v12 and
older, Safari v12 and older), polyfills may be needed for the following browser
features:
* [`requestAnimationFrame`](https://caniuse.com/#feat=requestanimationframe):
Available from [polyfill.io](https://polyfill.io/).
FF23
* [`element.prototype.classList`
(`add`/`remove`)](https://caniuse.com/#feat=classlist): Available from
[polyfill.io](https://polyfill.io/).
FF49 for full support
* [`URL` API](https://caniuse.com/#feat=url): Available from
[polyfill.io](https://polyfill.io/).
* [Pointer events](https://caniuse.com/#feat=pointer): Use
[elm-pep](https://npmjs.com/package/elm-pep) (lightweight) or
[@openlayers/pepjs](https://npmjs.com/package/pepjs) (for really, really old
browsers).
>
Adding the line:
<script src="https://unpkg.com/elm-pep";></script>
to the web page makes seamonkey work. However, I thought that seamonkey was a
reasonably modern browser, so it might be interesting to understand why I need
this polyfill ...
Firefox 59 was the first version that supported the Pointer events
extension
<https://developer.mozilla.org/en-US/docs/Web/API/Pointer_events> and
that's less than 2 years old, or two ESRs behind the current ESR.
As discussed earlier in the thread, SM 2.5.3 is based on slightly
earlier code, but I think it still counts as reasonably modern.
caniuse.com says that even now less than 75% of active browsers support
the extension. I certainly wouldn't want to use it without providing a
polyfill. Whether that's the responsibility of the site or openlayers is
moot but at least the requirement is made clear - up to a point.
Saying that the browser must support HTML5 and quoting the latest WHATWG
"specification" ...
> OpenLayers runs on all modern browsers that support
[HTML5](https://html.spec.whatwg.org/multipage/) ...
... is a meaningless requirement since it's a "living document" that
changes with no versioning, and so the meaning of the statement depends
on when you visit the URL ("the lunatics have taken over the asylum").
If you want to quote that in a spec, you need to use a GitHub commit or
a Web Archive URL. But no-one does that: they just say "use the latest
Firefox, Chrome, Safari, or Edge", so essentially "use one of these two
browsers".
>... and [ECMAScript
5](http://www.ecma-international.org/ecma-262/5.1/). This includes
Chrome, Firefox, Safari and Edge.
Even if true regarding JS language syntax (ES 5.1: 2011), this is a
little misleading since DOM APIs (eg, Pointer event) that are defined in
some later version of the WHATWG, and in the W3C Pointer Events spec (V1
April 2015) are required.
/df
--
London
UK
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
