List of the REMOVED features in the latest Edge insider Canary update Version 79.0.305.0

MVP

1. Block option is Removed and only Limit and Allow is available

 

Annotation 2019-10-15 221726.png

 

You can confirm this too by going into your settings edge://settings/content/mediaAutoplay

 

2. Another removed option in this latest Canary update

 

Annotation 2019-10-15 230205.png

 

in the previous Canary version (79.0.304.0) , the InPrivate mode window would look like this:

 

Annotation 2019-10-14 205609.png

 

 

 

 

 

18 Replies
Another removed option spotted and the post update:
InPrivate mode 3rd party cookie blocking

I hope we hear from officials whether this is temporary or permanent changes because those were important features that are missing :\

Hello recently i visited this forum and saw the topic about list of added features and i was happy and today i see they are removed. why is it happening?

 

@universalnettwork 


@universalnettwork wrote:

Hello recently i visited this forum and saw the topic about list of added features and i was happy and today i see they are removed. why is it happening?

 


 

Hi,

I understand it can be frustrating, I honestly have no idea why it is happening, I'm not even sure if it's a bug cause the removed features are from entirely different sections of the browser.

Dev channel is supposedly more stable with longer update periods

 


2. Another removed option in this latest Canary update


Spoiler
Edge cookie 1.45.gif

 

Doesn't matter, I'm on Version 79.0.305.0 (Official build) canary (64-bit)
and as you can see in my screenshot that option is Removed

@HotCakeX In my case, as can be seen in the gif, it was not removed.

 

And I said it doesn't matter.

I haven't done anything on purpose to remove it. and things like this are normal thanks to the Controlled feature roll outs, not everyone's browsers are the same. this is a potential issue that needs fixing.

 

 

Also it's been removed not only on my main system and on a couple of others too, some of them on VMs and some of them physical.
it's more complicated than you think. even if we had the same OS and same browser channel and version, still things can be a lot different because Microsoft puts us in different test groups.
I had to report missing feature because it's what is happening on my system, you are not experiencing it? good for you then.

 

And I said it doesn't matter...

 


It doesn't matter? of course it matters, because in your post you say it was removed, but you don't clarify that it could be part of the Controlled feature roll-outs or that it could have been removed for some insiders and for others not, I am showing that this feature was not removed in all cases.

@leopeva64-2_ 


@leopeva64-2_ wrote:

@HotCakeXit doesn't matter? of course it matters, because in your post you say it was removed, but you don't clarify that it could be part of the Controlled feature roll-outs or that it could have been removed for some insiders and for others not, I am showing that this feature was not removed in all cases.


it "could", so not "sure".

I can't put false info there unless developers explicitly say that it's not a bug and rather a controlled feature roll out. so until then, I have no further info to add.

 

I'm seeing it on a variety of machines with different OSes (server and client) so it's more than just someone's experience.

 

@HotCakeX But you are saying that my comment doesn't matter, and it does matter because I am showing that some insiders still have that feature in this version.

@leopeva64-2_ 


@leopeva64-2_ wrote:

@HotCakeX But you are saying that my comment doesn't matter, and it does matter because I am showing that some insiders still have that feature in this version.


It doesn't matter because it doesn't help my situation, and you already said that multiple times I don't know what good it does to keep arguing about it?

 

if you wanna talk off topic, use the personal message

 

it doesn't help my situation

My comment helps others know that the feature was not removed for everyone, because anyone who reads the post (before my comment) will think that the feature was removed for everyone, and I'm sorry, but my comments are not off-topic, so I will continue to respond in this post if you also continue to respond.

Only 2 of multiple machines that I see this feature being removed from after updating from

Version 79.0.304.0 Canary to Version 79.0.305.0 Canary

 

 

Annotation 2019-10-16 011907.png

 

InkedAnnotation 2019-10-16 011445_LI.jpg

 

I could go on and on as the problem can easily be reproduced but those 2 example suffice to prove it.

@leopeva64-2_ 

Spoiler

@leopeva64-2_ wrote:

@HotCakeX My comment helps others know that the feature was not removed for everyone

And you already said the same thing multiple times, it's enough 

 


@leopeva64-2_ wrote:

 I will continue to respond in this post if you also continue to respond.


 

Ok I'm going to report this because this is going no where with you as your only intention here is Spamming.

From my understanding, @HotCakeX has an unresolved issue, while @leopeva64-2_ has indicated this is not an issue for everyone. However, it is clearly an issue for some people. 

 

These points can both be true and do not negate each other. Can we agree on that? 

 

I'm not going to close this post to new replies to allow for potential fixes to the issue, but please do not comment on the above points again.