fix(mapbox-overlay) interleaved overlay using correct default parameters

[ibgreen]

Summary

• initialize interleaved map overlays with interleaved default parameters so depth and blending align with expectations

Testing

• not run (not requested)

---

Codex Task

[coveralls]

coverage: 91.144%. remained the same
when pulling 909c043 on codex/update-interleaved-initialization-for-parameters
into f713242 on master.

[Pessimistress]

@felixpalmer you added this line in #9803 it does seem that it should be true?

[chrisgervang]

Which issue is this resolving? I'm trying to reproduce

[ibgreen]

Which issue is this resolving? I'm trying to reproduce

https://openjs-foundation.slack.com/archives/C05JCDKHQUE/p1763426667707549

[Spacerat]

See this example: Interleaved mode draws jagged lines, whereas overlay mode seems to have anti-aliasing.

Overlay mode (smooth):

Interleaved mode (jagged):

The issue also appears pretty clearly in the arc example you linked to here - that's the example where I first noticed it. If you switch between overlay & interleaved mode, you can see the anti-aliasing toggle.

[Spacerat]

I attempted to test this fix myself and I found that it didn't seem to change the behavior here.

But I realized here that just setting antialias=true on the MapBox <Map> object fixes this! I suppose DeckGL anti-aliases by default when it manages the canvas, but MapBox doesn't (intentionally).

That's not to say that this change shouldn't land though. It does look like this prop probably was supposed to be set to true? But I I'm not really familiar with the code.

[chrisgervang]

But I realized here that just setting antialias=true on the MapBox object fixes this! I suppose DeckGL anti-aliases by default when it manages the canvas, but MapBox doesn't (intentionally).

Yes, this is the case (and always has been). So, just to confirm, setting antialias=true solves your issue?

If so, I think we can close this without the change. I'd rather not make a change to this area unless @felixpalmer says otherwise (he recently did an audit of these parameters) or there was a regression.

Feel free to open a doc PR adding a remark about this for interleaved users - deck shouldn't change Mapbox props, so antialiasing will need to be configured by users who want to use it.