Except one does since Google is the primary maintainer. Anyway, work on other browser engines is not duplicated or wasted.
>work on other browser engines is not duplicated or wasted.
How is having N engine developers implement some new addition to the EMCAScript or CSS standard for each of their engines not duplicated work?
Maintaining a fork is not fun as taking patches from the origin repo becomes more complicated the longer the fork exists and the bigger the divergence becomes.
> How is having N engine developers implement some new addition to the EMCAScript or CSS standard for each of their engines not duplicated work?
It would be duplicated only if they all maintained, say, a Blink fork.