I was half-expecting Mozilla to support both Manifest v2 and v3. But if I were them I wouldn't want to deal with backwards compatibility issues either. From the latest updates...
I was half-expecting Mozilla to support both Manifest v2 and v3. But if I were them I wouldn't want to deal with backwards compatibility issues either.
From the latest updates declarativeNetRequest seem to solve most of the complaints that people had (size limits, dynamic rules). But Mozilla probably doesn't want to be accused of "banning adblockers" either.
Without a common extension API standard, this puts them in an awkward spot. They need to maintain parity now that they've adopted Chrome's extension API, but that also removes much of their control. Any changes they make will cause frustration for developers and reduce compatibility.
It seems to me that Manifest v3 should have been an effort towards cross-browser standardization. I wonder if there were ever talks about that?
I was half-expecting Mozilla to support both Manifest v2 and v3. But if I were them I wouldn't want to deal with backwards compatibility issues either.
From the latest updates
declarativeNetRequestseem to solve most of the complaints that people had (size limits, dynamic rules). But Mozilla probably doesn't want to be accused of "banning adblockers" either.Without a common extension API standard, this puts them in an awkward spot. They need to maintain parity now that they've adopted Chrome's extension API, but that also removes much of their control. Any changes they make will cause frustration for developers and reduce compatibility.
It seems to me that Manifest v3 should have been an effort towards cross-browser standardization. I wonder if there were ever talks about that?