Not sure how they could fight manifest v3, it's Google making an (objectively bad) internal code decision that has knock-on effects for Chromium and everyone else.
FWIW they are going to try and keep things working and are looking for workarounds
Not sure how they could fight manifest v3, it's Google making an (objectively bad) internal code decision that has knock-on effects for Chromium and everyone else.
FWIW they are going to try and keep things working and are looking for workarounds