HDR10/Dolby Vision MP4 - Container (mis)identified as MOV?

[forbis]

Just as an update, I think the "mov" container might be a red herring, as the github issue linked by theguymadmax alluded to. Apparently ALL of my movies show as "mov" in the Media info view. I am beginning to think that container "misidentification" actually doesn't matter, and what does matter is Chrome is either incapable of displaying DV 8 or Jellyfin thinks it is - which of these is true, I'm not sure.

I'm going to see about enabling more verbose logging to see if I can tell exactly what is triggering the remux. Since I'm a code monkey by day I might also familiarize myself with the source and see if I can glean anything from it.

Further update: Gleaned this from the Jellyfin logs - TranscodeReason=VideoRangeTypeNotSupported

So, Jellyfin is obviously choosing to remux because it believes Chrome cannot play the Dolby Vision content. The "mov" was indeed a red herring and is likely related to the bug outlined in the github issue above. However I am under the impression that DV Profiles 7 and 8 fallback to HDR10 when the player/display is not DV-capable, correct me if I'm wrong here. Why does this not happen automatically and allow me to play direct to the browser?