The users’ disappointment is even greater because Sets was already a part of preview builds of Windows 10 Redstone 5, and no one could tell that there’s something wrong with the way it worked.
Sets actually causes compatibility issues
The features worked great only at first glance, because if you took a closer look at it, you would find out that it could trigger some compatibility issues that would eventually ruin some functionalities in third-party apps. For instance, Reddit apps are just one example, and the removal of the Sets feature from Windows 10 Redstone 5 build returns everything to normal and working correctly after previously being quite unstable.
Third-party app developers agree with Microsoft’s decision
Third-party app developers agreed with this decision that Microsoft took to pull Sets, and their reason was that the apps were sometimes not working as they should due to the tab implementation. A developer, Jose Fajardo, tweeted “damnit … upgraded to 17661 and “SeparateProcess” WebView in my XAML UWP app is broken 🙁 🙁 Does anyone know if there’s a capability/declaration that needs to be set to get this working again?” and then flaunted his happened on Twitter after finding out the cause of the problem. It’s worth mentioning that Microsoft did not entirely kill the Sets feature, but it delayed its debut. It will not be packed in Redstone 5, but there’s a pretty strong chance that we’ll get to see it included in the update that’s due in the spring of 2019. We’re expecting to see Redstone 5 launched this fall. RELATED STORIES TO CHECK:
Windows 10 build 17639 brings a new wave of Sets improvements Codename for upcoming Microsoft devices got leaked Microsoft Edge blocks video autoplay in Windows 10 Redstone 5
SPONSORED
Name *
Email *
Commenting as . Not you?
Save information for future comments
Comment
Δ
