Comment by ivanmontillam
Comment by ivanmontillam 3 hours ago
It's already problematic to have Chromium dominating/near-monopolizing, and add salt to the wound letting Gecko die this way.
Chromium is so prevalent as an engine, that most developers don't test their code on Firefox and just tell everyone to use Chrome/Chromium when they run into issues.
This has the unintentional side-effect of strong-arming the W3C into compliance with the engine and not the other way around. Why do we bother with the W3C then? if they are powerless and Chromium can do as they please?
But if firefox ran chrome, it wouldn't be a problem. Vivaldi, Opera, and others are doing just fine.