Forum Discussion
josh_bodner
Nov 03, 2020Silver Contributor
Dev channel update to 88.0.685.3 is live
Hello Insiders! Today we’re releasing build 88.0.685.3 to the Dev channel. It’s a relatively quiet week this week, although for heavy tab users, we’ve got some interesting stuff: a discussion abou...
ajasnz
Nov 08, 2020Brass Contributor
Can you confirm how history and open tab sync has been rolled out? It appears to be a/b tested as only one of my devices has got it available (they are all on the same edge version). It defeats the purpose of the functionality if not all of your devices have it available.
Thanks
HotCakeX
Nov 08, 2020MVP
Yes as you said it is A/B test, and this only happens at the beginning, to help them find issues quickly in a small test population before it hits everyone.
It will eventually be rolled out to everyone.
It will eventually be rolled out to everyone.
- ajasnzNov 08, 2020Brass ContributorWhile I understand the point of a/b testing and dont have a problem with it for most features I dont think it should be used in cases such as this which require you to have at least two devices with a feature.
- Dennis5mileNov 10, 2020Silver Contributorhhmm, interesting as I have it on all 4 of the devices I control.. If you do not have Dev/Canary on the other devices you will not see it. Also, if you are not logged into the same account on the other devices that do have it, they will not sync.
Dennis5mile - HotCakeXNov 09, 2020MVP
ajasnz wrote:
While I understand the point of a/b testing and dont have a problem with it for most features I dont think it should be used in cases such as this which require you to have at least two devices with a feature.But you/they don't know whether the first experimental implementation of History and open tabs sync can cause problem to other areas or not, so they have to use A/B testing in order to keep it safe.
- WittycatNov 08, 2020Iron ContributorPersonally i think more your configuration is exotic more chance you have to be on the test list ^^