Like others have pointed out, it seems to work fine in other browsers once you trick it into letting you in. General compatibility doesn't seem to be an issue. So, what is it that Firefox and Chrome on Linux (and only on Linux) don't support?
H.265 is what they don't support. I'm not an avid enough user to know where Apple Maps makes use of media, but the source code contains media player controls, so it must somewhere. Retrofitting compatibility by launch may be as simple as re-encoding the H.265 content. Not at all worth the effort for beta 1, but with an obvious path forward.
> So, what is it that Firefox and Chrome on Linux (and only on Linux) don't support?
H.265 is what they don't support.
Do codecs need to be supported by the browser itself? I thought this was unloaded to some media decoding framework. Linux does have h.265 support at least in mpv.
> Do codecs need to be supported by the browser itself?
Not necessarily. The browser could defer to licensing established by the operating system vendor, but Firefox places the expectation upon itself to have parity across platforms and to not support encumbered technologies.
> Linux does have h.265 support at least in mpv.
And if you've negotiated the licensing fees you can even use it, but chances are... Microsoft and Apple have dealt with the licensing for you on their platforms, so the ballgame is different there.
> To start, Maps on the web is available only in English. Maps on the web will be available for additional browsers, platforms, and languages soon.
Published Date: July 24, 2024
It's extremely hard to retrofit compatibility onto products. Case in point: all the "we only work in Chrome" sites that use Chrome-only APIs.