No srsly why. This is triggering one of those bugs from hell where the horizontal offset of a L.Popup depends on the offsetWidth of a detached DOM element before the @firstname.lastname@example.org CSS is loaded async'ly.
- Linking the CSS in the <svelte:head> is async and leads to race conditions
- Doing an import of the CSS requires that the consumer uses some rollup-plugin-css stuff
- Embedding the Leaflet CSS in the component might not be doable and requires an extra build step
...this is the kind of stuff that I'm very wary of when it comes to any kind of reactive framework (even @email@example.com): debugging this stuff requires *a lot* of knowledge about lifecycles and events and whatnot. Learning curve looks gentle enough, then it steeps up to brain damage.
Nothing like a good ol' polling hack to work around the issue.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!