@yngve: THANK YOU so much, at last some informative response. I have reported that issue quite a few snapshots ago, only recently managed to test it out in a new/empty profile (and ran into it again). Now that I know this is an upstream issue, I'll just stfu and patiently wait for this to be patched into V (from what you say, probably 2, max 3 snapshots ahead), cause at least I know the issue is known - and even worked on.
Oh, also, why would anyone keep Chrome/Edge around anyway?