> Chrome is ahead on things like Web Components because these are features that Google has wanted and pushed.
It's a feature that Firefox wanted and pushed as well, in the past. They've stopped being leaders on this particular feature though (partly because some of the proponents left, i imagine).
> It's not due to lack of implementation effort that they're disabled in Firefox, it's because Firefox wants to wait for the standardization process to continue for a bit.
You're talking about the old v0 specs that they implemented and disabled. The v1 specs are already standardized and in Chrome stable, shadow DOM is in Safari stable.
That's my real point, not that Firefox is behind Chrome, they're usually in 3rd place on most things.
It's a feature that Firefox wanted and pushed as well, in the past. They've stopped being leaders on this particular feature though (partly because some of the proponents left, i imagine).
> It's not due to lack of implementation effort that they're disabled in Firefox, it's because Firefox wants to wait for the standardization process to continue for a bit.
You're talking about the old v0 specs that they implemented and disabled. The v1 specs are already standardized and in Chrome stable, shadow DOM is in Safari stable.
That's my real point, not that Firefox is behind Chrome, they're usually in 3rd place on most things.