Forum Discussion
Solved
Features
I am missing the new features in microsoft edge 90 for example history , download flyout menus
- Apparently even in the Stable channel, features are still A/B tested, and so random users will see some of the advertised new features, and others won't. Which to me, frankly, is stupid. If Microsoft want to test features, that's what the Dev (Beta) and Canary (Daily/Alpha) channels exist for; Stable should provide a consistent experience for everyone. It's beyond silly to advertise features that are in a new major-version, let news publications do write-ups, but then have users find those features aren't actually there yet!
If Microsoft know in-advance a feature is still "not-quite-ready" then hold it back until the next major milestone release instead!
Apparently even in the Stable channel, features are still A/B tested, and so random users will see some of the advertised new features, and others won't. Which to me, frankly, is stupid. If Microsoft want to test features, that's what the Dev (Beta) and Canary (Daily/Alpha) channels exist for; Stable should provide a consistent experience for everyone. It's beyond silly to advertise features that are in a new major-version, let news publications do write-ups, but then have users find those features aren't actually there yet!
If Microsoft know in-advance a feature is still "not-quite-ready" then hold it back until the next major milestone release instead!
If Microsoft know in-advance a feature is still "not-quite-ready" then hold it back until the next major milestone release instead!
Spoiler
dftf-wip wrote:
Apparently even in the Stable channel, features are still A/B tested, and so random users will see some of the advertised new features, and others won't. Which to me, frankly, is stupid. If Microsoft want to test features, that's what the Dev (Beta) and Canary (Daily/Alpha) channels exist for; Stable should provide a consistent experience for everyone. It's beyond silly to advertise features that are in a new major-version, let news publications do write-ups, but then have users find those features aren't actually there yet!
If Microsoft know in-advance a feature is still "not-quite-ready" then hold it back until the next major milestone release instead!
it's not stupid when you know the reason behind it, neither is it about feature not ready.
stable build is used by the most users in the world, so no matter how many insiders test it, when introducing certain novel features to millions of people, it's always best to do it cautiously and in waves. that's what the staged rollout is all about.
when a bug or problem happens, it won't affect everyone in the world simultaneously. there is absolutely nothing stupid or silly about it.