Map over sidebar/navbar

[LukeSavefrogs]

Hi, it's me again 😄

Problem

The maps (both the Infolists\MapEntry and the Fields\Map) seem to overlap the navbar, preventing the user from clicking on anything else:

Workaround

To fix I placed the following CSS in my resources/css/app.css (vite theme):

/* Override for `Dotswan\MapPicker\*` */
div[x-ref="map"] {
    z-index: 0 !important;
}

[nirine1]

@LukeSavefrogs I had the same issue some commit before. I have made this pull request to fix it.

Here's what you can add in your CSS :

.leaflet-pane,
.leaflet-tile-pane,
.leaflet-overlay-pane,
.leaflet-shadow-pane,
.leaflet-marker-pane,
.leaflet-tooltip-pane,
.leaflet-popup-pane,
.leaflet-map-pane canvas,
.leaflet-map-pane svg,
.leaflet-control,
.leaflet-top,
.leaflet-bottom,
.map-location-button {
    z-index: auto !important;
}

Instead of a z-index: 0, make it auto so that all maps will take the z-index of its container.

The changes I have made were considered unnecessary and were removed few commits ago.

[LukeSavefrogs]

@nirine1 thank you for your submission! I don't have the means to test this fix right now, I'll try as soon as I can...

If you confirm It works on a new installation i will close the issue.

[nirine1]

@LukeSavefrogs Sorry for the late reply. I’ve just tested again on a fresh setup with v2.1.2 and Filament v4. The overlap with the sidebar/navbar is still present.

Applying the CSS rules I mentioned earlier still resolves the issue correctly by letting the map inherit the container’s z-index.

So the problem is reproducible on the latest versions, and the CSS workaround remains valid.
If you’re able to test on your side and confirm, you can close the issue accordingly.

[LukeSavefrogs]

So the problem is reproducible on the latest versions, and the CSS workaround remains valid.
If you’re able to test on your side and confirm, you can close the issue accordingly.

So you're telling me that the issue is still present?

[nirine1]

So you're telling me that the issue is still present?

Yes.

[LukeSavefrogs]

So you're telling me that the issue is still present?

Yes.

Which means I cannot close the issue, since it's still an issue 😄 (sorry for the bad word pun)

[LukeSavefrogs]

I think that the changes your PR introduced should be revisited and understood why they were removed as "unnecessary", maybe it was a mistake

[nirine1]

I think that the changes your PR introduced should be revisited and understood why they were removed as "unnecessary", maybe it was a mistake

Your fix looks better with fewer lines 😄 We could open a new PR, but yeah, we need to get why the changes were removed first.

@mohaphez Hi, any idea?