All downstream Chrome clones will follow papa Google eventually, as they won't keep stuff working on their own, cherry picking upstream.
All downstream Chrome clones will follow papa Google eventually, as they won't keep stuff working on their own, cherry picking upstream.
Not that it's exactly a shock they don't care about XSLT either (how many do these does) but carrying a patch set for different functionality against upstream is something individual users on HN (including myself) do when they like, let alone entire companies shipping browser products.
Everyone likes to have their private branch, until they discover how many hours they need to keep up with upstream, especially if upstream doesn't care one iota about them.
I've been maintaining my patcheset to it for 5 years as one dude who's $dayjob is not coding. It just got a lot easier with LLMs recently as well. And of course companies have been carrying larger much larger changesets than I have been for many years.
Hell, even Firefox has multiple forks which deviated to keep old engines/UIs/features for many years and it has a tiny market share/little to no 3rd party company backed spins in comparison.
But it seems like you don't have much interest in all of this, just repeating that an upstream source is involved therefore you believe there can be no differences worth noting or discussing. Your loss, not the title's.