08-22-2019 02:00 PM
08-22-2019 07:06 PM
I was using Edge Dev fine until I do Windows Update yesterday. Then today I found "Dev channel" show "This page is having a problem", even for edge://settings.
08-22-2019 07:37 PM
08-22-2019 10:20 PM
So, can you please fix the DHCP issues with Edge so I can properly cast Amazon Prime to my Chromecast Ultra? It's getting irksome that I can't use a core feature of Chromium with this new Edge Browser and DHCP is pretty much necessary for all functions revolving around paid for content providers like Hulu and Netflix.
08-22-2019 11:07 PM
08-23-2019 02:28 AM
@ericlaw Edge://conflicts will not open anything other than the same page 'this page is having trouble'.
We are running a Symantec version, on Windows 10 Pro 1809 64Bit...
Symantec version is: Version 14 (14.0 RU1 MP1) build (14.0.3876.110) - which appears to be nearly 2 years old!!! Hmmm...!
08-23-2019 02:31 AM - edited 08-23-2019 06:11 AM
I like to see Edge going forward and I use it regularly in business and at home, usually without any problems in my use cases.
But for use as standard browser in our company there is one showstopper: We have one extension provided by an cooperative for their members for Chrome via Chrome Web Store. At the moment we use Chrome as standard browser and I can force the installation of this extension for our employees via GPO - but not in Edge (copied settings from Google Chrome ADMX to Edge ADMX).
This extension can't be found in Chrome Web Store via manual search, so this is the only way to do it.
Please add the feature to force install of extensions from Chrome Web Store too.
thank you for your fast response. I have to admit, in the end it was my fault. While processing your request for details I found out that the policy definitions work fine and there was a problem with deploying the latest version of the policies to the workstations. Thank you for guiding me in the right direction.
I tried it on several workstations and our terminal server farm and it works now.
08-23-2019 04:42 AM
08-23-2019 04:46 AM
08-24-2019 08:08 AM
I found that after upgrading to Dev 220.127.116.11, the "Desktop Only" input methods are disabled and cannot be used, while previous builds and Beta 18.104.22.168 are able to use. The new Edge should be a Desktop application so that I can use them. Please fix it and thanks a lot!
08-27-2019 01:18 PM
Just an update for this discussion but I figured out the issue with the DEV Build and it was definitely Symantec Endpoint Protection that caused the issue.
SEP - Before Update - 14.0 RU1 - Build 14.0.3752.1000
SEP - After Update - 14.2 RU1 MP1 - 14.2.4811.1100
This newer version has no issues with this DEV build of Edge and everything works as expected.
08-28-2019 08:39 AM
Added support for exiting full screen mode using the ESC key on Mac.
Your app have the special combination to exit a full screen Ctrl+Cmd+F. At the same time Esc have many other useful applications. Could you, please please please, add the way to disable it from exiting a full screen?
Actually it is the only reason I cannot switch to Safari on Mac - they have the very same problem with Esc.
08-29-2019 09:12 AM
Same for it, it fails catastrophically for me after the upgrade. I did an uninstall/reinstall, and it still fails. It also complains about my Lastpass and ABP extensions, which were even present after I reinstalled. I don't know if the extensions errors are a cause or a symptom.
08-29-2019 10:35 AM - edited 08-29-2019 10:37 AM
The extension errors are a symptom. Every renderer process (including the renderer processes used by each of your extensions) is crashing because something is trying to inject code. Do you have Symantec installed? If so, you'll need to update to the latest version.
09-02-2019 06:11 AM
Scrolling with two fingers keeps triggering right click, using a hp envy x360 with default trackpad drivers.
Thanks for reading this:folded_hands::folded_hands:
09-03-2019 06:22 PM
Thumbs up. Using on all my machines. Beta also fixed some issues on work domain that Dev suffered.
BUT I wanted to post a PDF related comment though. I don't know all of the transaction process to talk intelligently about it, but the short story is certain sites result in a rendered pdf that cannot be saved as a pdf. This isn't often a surprise as sites change policies and methods, but in this case the behavior is specific to how the site is handled by the Beta and Dev (tried both) as compared to the former Edge and other browsers. To explain - I often pull down pdf's for work and home, but ran into an issue specifically with Citibank servers. If someone on the dev team has a Citibank account, ask them to download a statement. In the Beta and Dev browsers, attempts to save the rendered pdf result in an '.action' file. In the former Edge, this isn't an issue where saving as a pdf (still) works fine. Not being a mac user, I can only go on what I read, but it sounds like Citibank is interpreting the pdf as a Mac action/workflow file. No matter the reason, there is at least one person that is hoping this behavior reverts. [just to save some time - yes I am aware that I could print the rendering to a pdf instead. ]
09-09-2019 03:32 AM
09-18-2019 10:26 AM
"Fixed an issue where right clicking on some browser UI is instead treated as a left click."
I noticed that I can't right-click on context menu items anymore.
This actually breaks consistency, since right-clicking context menu items in Windows is possible.
For example, I can right-click on a folder and right-click on properties and it works.
Please consider reverting this change to stay consistent with Windows.