4 ms·

That bug reads to me like that functionality is not yet implemented, because they're still figuring out how to securely add that back in. However, since MV2 is

by Vinnl 4y ago

That bug reads to me like that functionality is not yet implemented, because they're still figuring out how to securely add that back in. However, since MV2 is still supported, I don't see the problem here — this is just the first public release of some MV3 functionality, but full feature parity is still being worked on (Service Workers aren't supported yet either, for an example that affects my extension).

dessant 4y ago
You think it's fine to invite developers to begin porting extensions to Manifest V3, and then kneecap their work a couple of months later as they port their extensions, while also telling them to open new bug reports in which they need to spend time defending general-purpose computing? This is not a missing feature, but a limitation that has been added only to Firefox.
- Vinnl 4y ago
  As long as it's clear that it's an initial exploration and that not everything is possible yet, sure. It was clear to me, though admittedly I'm probably paying closer attention than most, so I'm not representative — it might indeed be that communication could have been better.
chrismorgan 4y ago
I regret to say I no longer trust Mozilla in this specific sort of case. As an occasional-but-regular filer of bugs and user of Nightly for my daily driver for over ten of the last twelve years, the feeling I have is that where a decade ago they generally wouldn’t ship a thing until it was done, increasingly often in the last few years they have been shipping things despite known significant problems, only finishing things months later, but leaving users in the lurch in the mean time. (Most recent example that I have in mind: they switched content dark mode from matching OS theme to matching browser theme in 95, despite quite a few immediate and detailed objections as soon as the patch landed on Nightly—and yes, I’m willing to admit that the change will match what some, perhaps more, users want—but didn’t expose it in about:preferences until 100; to my eye, they should fairly obviously have reverted the change until they had that setting, or at the very least mentioned the about:config pref to restore the old behaviour in the release notes. At least in that case there was still a pref for it.)

by Vinnl 4y ago

dessant 4y ago

You think it's fine to invite developers to begin porting extensions to Manifest V3, and then kneecap their work a couple of months later as they port their extensions, while also telling them to open new bug reports in which they need to spend time defending general-purpose computing? This is not a missing feature, but a limitation that has been added only to Firefox.

Vinnl 4y ago
As long as it's clear that it's an initial exploration and that not everything is possible yet, sure. It was clear to me, though admittedly I'm probably paying closer attention than most, so I'm not representative — it might indeed be that communication could have been better.

chrismorgan 4y ago

I regret to say I no longer trust Mozilla in this specific sort of case. As an occasional-but-regular filer of bugs and user of Nightly for my daily driver for over ten of the last twelve years, the feeling I have is that where a decade ago they generally wouldn’t ship a thing until it was done, increasingly often in the last few years they have been shipping things despite known significant problems, only finishing things months later, but leaving users in the lurch in the mean time. (Most recent example that I have in mind: they switched content dark mode from matching OS theme to matching browser theme in 95, despite quite a few immediate and detailed objections as soon as the patch landed on Nightly—and yes, I’m willing to admit that the change will match what some, perhaps more, users want—but didn’t expose it in about:preferences until 100; to my eye, they should fairly obviously have reverted the change until they had that setting, or at the very least mentioned the about:config pref to restore the old behaviour in the release notes. At least in that case there was still a pref for it.)