Earlier quoted context omitted.
Safari, Chrome, and Edge already partitioned the HTTP Cache by site; Firefox was the last major browser not to. It's great that Firefox is doing this, but it's not a differentiator.
The way they phrased it, in the post implies otherwise? > These impacts are similar to those reported by the Chrome team for similar cache protections they are planning to roll out.
"The feature is being rolled out through late 2020. To check whether your Chrome instance already supports it: ..."