3 ms·

Here are some Safari-specific issues I have met when developing a website in the past two years: * font being displayed way bigger than in the other browsers

by me_bx 3y ago

Here are some Safari-specific issues I have met when developing a website in the past two years: * font being displayed way bigger than in the other browsers - had to add normalization rules specific of Safari * Parsing dates in the format "YYYY-MM-DD HH:MI:SS" not working, had to convert to ISO-8601 using a regex (the dates in original format were received from a third-party website). * Interactions in maps not working using leaflet library (version 1.7 at the time). Fixed by switching to maplibre, which turned out to be a great move for other reasons. * HTML in SVGs (via ForeignObject) are always displayed on top of the SVG content, making it impossible to annotate HTML with SVG markup (arrows, circling stuff). Plus some issues with `backdrop-filter:blur`, although this CSS is also problematic elsewhere. All in all, it felt like having to deal with Internet Explorer 10+ years ago: the other browsers work well out of the box, and tricks and workarounds need to be identified for the bad browser.

jddj 3y ago
> maplibre, which turned out to be a great move for other reasons Would you care to elaborate a little?
- me_bx 3y ago
  Finding maplibre 'better' was more valid at the time than today, and is also subjective. The creators and maintainers of both libraries have done some great work (and are still doing so). Back in January 2022, the stable version of leaflet, v1.7.1, was from September 2020, and was affected by some small bugs degrading the user experience. Although the release of following version seemed close, there was no clear schedule for it, and I had concerns about how maintained the library would remain. As of today, the bug from 2015 where there is some white space between map tiles on fractional zoom levels [0] is still open. Also, leaflet was a pain to integrate in Svelte Kit framework, because it depended on `window` and-or `document`, not available at server side. Maplibre, on the other hands, with a feature set roughly equivalent to Leaflet, benefited from much more frequent releases, and seemed more stable across browsers and devices. It was also easier to make it work in Svelte kit. [0]: https://github.com/Leaflet/Leaflet/issues/3575 https://github.com/Leaflet/Leaflet/issues/3575
  - jddj 3y ago
    Thanks. For my usecase leaflet is great, but was wondering if I was missing something. I use some intermediate stuff (vue2leaflet) that is starting to rot a bit but that's less of a concern than the map lib itself.

by me_bx 3y ago

jddj 3y ago

> maplibre, which turned out to be a great move for other reasons Would you care to elaborate a little?

me_bx 3y ago
Finding maplibre 'better' was more valid at the time than today, and is also subjective. The creators and maintainers of both libraries have done some great work (and are still doing so). Back in January 2022, the stable version of leaflet, v1.7.1, was from September 2020, and was affected by some small bugs degrading the user experience. Although the release of following version seemed close, there was no clear schedule for it, and I had concerns about how maintained the library would remain. As of today, the bug from 2015 where there is some white space between map tiles on fractional zoom levels [0] is still open. Also, leaflet was a pain to integrate in Svelte Kit framework, because it depended on `window` and-or `document`, not available at server side. Maplibre, on the other hands, with a feature set roughly equivalent to Leaflet, benefited from much more frequent releases, and seemed more stable across browsers and devices. It was also easier to make it work in Svelte kit. [0]: https://github.com/Leaflet/Leaflet/issues/3575 https://github.com/Leaflet/Leaflet/issues/3575
- jddj 3y ago
  Thanks. For my usecase leaflet is great, but was wondering if I was missing something. I use some intermediate stuff (vue2leaflet) that is starting to rot a bit but that's less of a concern than the map lib itself.