Based on commentary I think google has done a good job of misleading people.
ITP and isolated cookies are a response to companies like Google and Facebook developing mechanisms to defeat/undermine 3rd party cookie blocking.
Google's "tracking protection" is something Safari did from the very first beta two decades ago, Firefox adopted 3rd party cookie blocking more recently, but that's all google is doing right now, and (presumably because) it's a tracking mechanism that they have already defeated.
They're calling it "tracking protection" to try and launder the "tracking protection" terminology of actual privacy mechanisms and terminology of other browsers, rather than actually acknowledging that what they're doing now was insufficient years ago (when safari and firefox had to introduce a bunch of very complex logic to continue to actually protect user privacy).
https://www.theverge.com/2020/3/24/21192830/apple-safari-int...
ITP is not 3rd party cookie blocking.
3rd party cookie blocking has been the default in safari and webkit since literally the first beta.
ITP is a response to companies like google and Facebook developing techniques to circumvent 3rd party cookie blocking as it became more popular (due to Firefox, Safari, and mostly iOS safari). Google is not developing an equivalent to ITP, it's literally flipping a single flag that they decided to turn off when they launched chrome because they're an advertising company that was dependent on them.
You need to understand here: Google is not working on releasing anything equivalent to ITP or whatever Firefox calls their version, they're working on something much more basic, and it's something they have already circumvented (which is why Safari and Firefox have their complex ITP or whatever mechanisms).
ITP is not about 3rd party cookies, ITP is first and second party cookies where people use indirect load mechanisms to circumvent 3rd party cookie blocking. e.g when people load Facebook buttons and such like directly into a page the 3rd party cookie isn't available in JS but the resource load for the Facebook button allows Facebook (or whoever) to return the tracking identifier directly to the host page so that it can update its own tracking information. ITP (and similar in Firefox) prevents that by saying some variation of "if I see requests to domain X from lots of different domains, we should assume that's being used for tracking purposes, and so not every request to domain X from a domain Y should be completely isolated from queries to domain X from any other domain" so now once you decide the domain X is used for tracking purposes you don't have a "cookies for X" database you have "cookies for X when loaded from Y", "cookies for X when loaded from Z", etc.
What google is talking about is not anything approaching ITP, they're literally talking about something even more basic: JS on domain A can't directly interact with cookie information on domain B, which is the 3rd party blocking that is what Safari and WebKit have always done by default.