SOLVED

Salesforce behaviour with Edge Canary 86.0.611.0

%3CLINGO-SUB%20id%3D%22lingo-sub-1595451%22%20slang%3D%22en-US%22%3ESalesforce%20behaviour%20with%20Edge%20Canary%2086.0.611.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1595451%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20recently%20been%20experiencing%20issues%20with%20Edge%20Canary%20in%20the%20latest%20releases%20that%20aren't%20occurring%20in%20Edge%20itself%20with%20Salesforce.%20Some%20pages%20within%20Salesforce%20where%20we%20use%20a%20custom%20tab%20on%20an%20opportunity%20is%20opening%20as%20a%20separate%20window%20instead%20of%20appearing%20in%20the%20nested%20tab.%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20I%20click%20on%20the%20Pandadoc%20tab%2C%20it%20should%20open%20a%20nested%20view%20into%20the%20Pandadoc%20system%2C%20but%20is%20instead%20opening%20a%20new%20tab.%20The%20link%20when%20you%20highlight%20over%20the%20link%20is%20javascript%26amp%3Bcolon%3Bvoid(0)%3C%2FP%3E%3CP%3EIt%20should%20look%20like%20the%202020-08-18%2021_13_02-Window.png%20%2C%20but%20instead%20looks%20like%202020-08-18%2021_13_52-Window.png.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnfortunately%20the%20buttons%20on%20the%20new%20window%20do%20not%20work%20as%20I%20think%20they%20depend%20on%20references%20on%20the%20actual%20Salesforce%20opportunities%20page%2C%20so%20I'm%20having%20to%20work%20in%20Edge%20itself%20at%20the%20moment.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1605392%22%20slang%3D%22en-US%22%3ERe%3A%20Salesforce%20behaviour%20with%20Edge%20Canary%2086.0.611.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1605392%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F446938%22%20target%3D%22_blank%22%3E%40rob_farnell%3C%2FA%3E%3C%2FP%3E%3CP%3EHi%20there%2C%20you%20are%20welcome%20to%20the%20%3CSTRONG%3EMicrosoft%20Edge%20Insider%3C%2FSTRONG%3E%20Community%20Hub!%3C%2FP%3E%3CP%3EThanks%20for%20reporting%20the%20issue%20here.%20I%20would%20recommend%20you%20to%20send%20feedback%20about%20this%20bug%20through%20the%20in-app%20feedback%20tool%20in%20Microsoft%20Edge%20(%3CI%3EAlt%2BShift%2BI%3C%2FI%3E)%20with%20the%20diagnostics%20attached%20in%20order%20to%20help%20the%20%3CSTRONG%3EMicrosoft%20Edge%20dev%20team%3C%2FSTRONG%3E%20to%20resolve%20your%20issue%20as%20soon%20as%20possible.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1615585%22%20slang%3D%22en-US%22%3ERe%3A%20Salesforce%20behaviour%20with%20Edge%20Canary%2086.0.611.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1615585%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F537238%22%20target%3D%22_blank%22%3E%40ShaunakSawant%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20also%20started%20seeing%20issues%20in%20Salesforce%20from%26nbsp%3B86.0.611.0%20and%20all%20builds%20since.%20I%20have%20provided%20the%20feedback%20via%20the%20Edge%20Send%20Feedback%20option%20as%20well.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20use%20the%20Support%20console%20and%20when%20I%20try%20an%20open%20a%20support%20case%20I%20can%20seeing%20looping%20%22Waiting%20for..%22%20URL%20handoffs%20in%20the%20bottom%20left%20corner%20of%20the%20page%20and%20then%20I%20get%20an%26nbsp%3Berror%20and%20broken%20page%20symbol%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-applescript%22%3E%3CCODE%3E%3CREDACTEDCOMANYNAME%3E.my.salesforce.com%20redirected%20you%20too%20many%20times%3C%2FREDACTEDCOMANYNAME%3E%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20other%20pages%20I%20will%20get%20the%20following%20error%20message%20as%20it%20tries%20to%20load%20page%20elements%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-applescript%22%3E%3CCODE%3EYour%20browser%20privacy%20settings%20have%20prevented%20this%20page%20from%20showing%20some%20Visualforce%20content.%20To%20display%20this%20content%20you%20need%20to%20change%20your%20browser%20privacy%20settings%20to%20allow%20%22Third%20Party%22%20cookies%20from%20the%20domain%20%3CREDACTED%3E.%3CREDACTED%3E.visual.force.com.%20Alternatively%2C%20if%20your%20browser%20is%20Internet%20Explorer%2C%20you%20can%20add%20%3CREDACTED%3E.%3CREDACTED%3E.visual.force.com%20to%20your%20trusted%20sites%20list%20in%20the%20security%20options%20page.%3C%2FREDACTED%3E%3C%2FREDACTED%3E%3C%2FREDACTED%3E%3C%2FREDACTED%3E%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1757015%22%20slang%3D%22en-US%22%3ERe%3A%20Salesforce%20behaviour%20with%20Edge%20Canary%2086.0.611.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1757015%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20theshaunshaw%2C%3C%2FP%3E%3CP%3EI%20did%20send%20through%20the%20diagnostics%20details%20as%20per%20your%20recommendation%20back%20in%20August.%20The%20issue%20is%20continuing%20to%20occur%20on%20the%20latest%20release%2C%20so%20the%20issue%20hasn't%20been%20resolved%20as%20of%20yet.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1775709%22%20slang%3D%22en-US%22%3ERe%3A%20Salesforce%20behaviour%20with%20Edge%20Canary%2086.0.611.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1775709%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F446938%22%20target%3D%22_blank%22%3E%40rob_farnell%3C%2FA%3E%26nbsp%3BLatest%20version%20of%20Edge%20Stable%20is%20breaking%20the%20Salesforce%20site%20for%20us%20as%20well%2C%20particularly%20parts%20of%20the%20site%20coming%20from%20visual.force.com.%20All%20versions%20of%20Google%20Chrome%20(stable%2C%20beta%2C%20canary)%20are%20working%20fine.%20Sent%20a%20few%20reports%20to%20Edge%20feedback.%3CBR%20%2F%3E%3CBR%20%2F%3EAdditional%20discussion%20here%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fwww.reddit.com%2Fr%2Fsalesforce%2Fcomments%2Fj9qjps%2Fproblems_with_salesforce_and_microsoft_edge%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EProblems%20with%20Salesforce%20and%20Microsoft%20Edge%20%3A%20salesforce%20(reddit.com)%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EHopefully%20this%20gets%20addressed%20soon%2C%20this%20will%20hurt%20adoption%20of%20Edge%20within%20our%20company.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1776506%22%20slang%3D%22en-US%22%3ERe%3A%20Salesforce%20behaviour%20with%20Edge%20Canary%2086.0.611.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1776506%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F830700%22%20target%3D%22_blank%22%3E%40andrewtchilds%3C%2FA%3E%26nbsp%3BI%20had%20a%20look%20at%20the%20release%20notes%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployedge%2Fmicrosoft-edge-relnote-stable-channel%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMicrosoft%20Edge%20release%20notes%20for%20Stable%20Channel%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20don't%20think%20the%20security%20updates%20that%20you%20mention%20on%20Reddit%20are%20the%20issue%2C%20as%20the%20issue%20pre-dates%20that%20release%20number.%26nbsp%3B%3C%2FP%3E%3CP%3ECould%20it%20be%20a%20cookie%20issue%3F%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployedge%2Fmicrosoft-edge-policies%23legacysamesitecookiebehaviorenabled%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMicrosoft%20Edge%20Browser%20Policy%20Documentation%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1777249%22%20slang%3D%22en-US%22%3ERe%3A%20Salesforce%20behaviour%20with%20Edge%20Canary%2086.0.611.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1777249%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F446938%22%20target%3D%22_blank%22%3E%40rob_farnell%3C%2FA%3E%26nbsp%3BNice%20find!%20Was%20there%20some%20changelog%20that%20you%20got%20that%20from%3F%3CBR%20%2F%3E%3CBR%20%2F%3EI%20was%20able%20to%20add%20%5B*.%5Dforce.com%20and%20%5B*.%5Dsalesforce.com%20to%20the%20list%20of%20sites%20that%20use%20the%20legacy%20SameSite%20behavior%20for%20cookies%20and%20things%20seem%20to%20be%20working%20now.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EUsed%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployedge%2Fmicrosoft-edge-policies%23legacysamesitecookiebehaviorenabledfordomainlist%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ethis%3C%2FA%3E%20policy%2C%20specifically%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22EdgeSameSiteCookieGroupPolicy.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F226457i708EBE555D55EA69%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22EdgeSameSiteCookieGroupPolicy.png%22%20alt%3D%22EdgeSameSiteCookieGroupPolicy.png%22%20%2F%3E%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22EdgeSameSiteCookieRegistry.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F226456i907AB4E92EA2C812%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22EdgeSameSiteCookieRegistry.png%22%20alt%3D%22EdgeSameSiteCookieRegistry.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1777254%22%20slang%3D%22en-US%22%3ERe%3A%20Salesforce%20behaviour%20with%20Edge%20Canary%2086.0.611.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1777254%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F830700%22%20target%3D%22_blank%22%3E%40andrewtchilds%3C%2FA%3E%26nbsp%3BGreat%20news!%3C%2FP%3E%3CP%3EThe%20release%20notes%20mentioned%20the%20cookie%20change%20on%20the%20features%20list.%20It%20was%20the%20only%20thing%20that%20I%20believed%20was%20within%20the%20vicinity%20of%20affecting%20the%20iframes%20on%20the%20list.%3C%2FP%3E%3CP%3EThanks%20for%20testing%20my%20suggestion.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20attached%20an%20export%20of%20the%20registry%20key%20that%20worked%20for%20me%20too.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1778140%22%20slang%3D%22en-US%22%3ERe%3A%20Salesforce%20behaviour%20with%20Edge%20Canary%2086.0.611.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1778140%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F446938%22%20target%3D%22_blank%22%3E%40rob_farnell%3C%2FA%3E%26nbsp%3B%26amp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F830700%22%20target%3D%22_blank%22%3E%40andrewtchilds%3C%2FA%3E%26nbsp%3B-%20thanks%20guys%2C%20that%20has%20fixed%20it%20for%20me%20based%20on%201%20day%20of%20testing%20today!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1778845%22%20slang%3D%22en-US%22%3ERe%3A%20Salesforce%20behaviour%20with%20Edge%20Canary%2086.0.611.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1778845%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F446938%22%20target%3D%22_blank%22%3E%40rob_farnell%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20sorry%20I%20could%20not%20reply%20to%20the%20question%20you%20asked%20because%20I%20was%20offline%20for%20a%20month.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F830700%22%20target%3D%22_blank%22%3E%40andrewtchilds%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20giving%20the%20answer%20to%20the%20conversation%26nbsp%3B%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Fhtml%2Fimages%2Femoticons%2Fsmile_40x40.gif%22%20alt%3D%22%3Asmile%3A%22%20title%3D%22%3Asmile%3A%22%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

I have recently been experiencing issues with Edge Canary in the latest releases that aren't occurring in Edge itself with Salesforce. Some pages within Salesforce where we use a custom tab on an opportunity is opening as a separate window instead of appearing in the nested tab. 

If I click on the Pandadoc tab, it should open a nested view into the Pandadoc system, but is instead opening a new tab. The link when you highlight over the link is javascript:void(0)

It should look like the 2020-08-18 21_13_02-Window.png , but instead looks like 2020-08-18 21_13_52-Window.png.

 

Unfortunately the buttons on the new window do not work as I think they depend on references on the actual Salesforce opportunities page, so I'm having to work in Edge itself at the moment.

 

9 Replies
Highlighted

@rob_farnell

Hi there, you are welcome to the Microsoft Edge Insider Community Hub!

Thanks for reporting the issue here. I would recommend you to send feedback about this bug through the in-app feedback tool in Microsoft Edge (Alt+Shift+I) with the diagnostics attached in order to help the Microsoft Edge dev team to resolve your issue as soon as possible.

Highlighted

@TheShaunSaw 

 

I also started seeing issues in Salesforce from 86.0.611.0 and all builds since. I have provided the feedback via the Edge Send Feedback option as well.

 

We use the Support console and when I try an open a support case I can seeing looping "Waiting for.." URL handoffs in the bottom left corner of the page and then I get an error and broken page symbol:

 

<redactedcomanyname>.my.salesforce.com redirected you too many times

 

 

On other pages I will get the following error message as it tries to load page elements:

 

Your browser privacy settings have prevented this page from showing some Visualforce content. To display this content you need to change your browser privacy settings to allow "Third Party" cookies from the domain <redacted>.<redacted>.visual.force.com. Alternatively, if your browser is Internet Explorer, you can add <redacted>.<redacted>.visual.force.com to your trusted sites list in the security options page.

 

Highlighted

Hi theshaunshaw,

I did send through the diagnostics details as per your recommendation back in August. The issue is continuing to occur on the latest release, so the issue hasn't been resolved as of yet.

Highlighted

@rob_farnell Latest version of Edge Stable is breaking the Salesforce site for us as well, particularly parts of the site coming from visual.force.com. All versions of Google Chrome (stable, beta, canary) are working fine. Sent a few reports to Edge feedback.

Additional discussion here:
Problems with Salesforce and Microsoft Edge : salesforce (reddit.com)

Hopefully this gets addressed soon, this will hurt adoption of Edge within our company.

Highlighted

@andrewtchilds I had a look at the release notes here: Microsoft Edge release notes for Stable Channel | Microsoft Docs

 

I don't think the security updates that you mention on Reddit are the issue, as the issue pre-dates that release number. 

Could it be a cookie issue? Microsoft Edge Browser Policy Documentation | Microsoft Docs

Highlighted
Best Response confirmed by rob_farnell (Occasional Contributor)
Solution

@rob_farnell Nice find! Was there some changelog that you got that from?

I was able to add [*.]force.com and [*.]salesforce.com to the list of sites that use the legacy SameSite behavior for cookies and things seem to be working now.

Used this policy, specifically:

EdgeSameSiteCookieGroupPolicy.png
EdgeSameSiteCookieRegistry.png

Highlighted

@andrewtchilds Great news!

The release notes mentioned the cookie change on the features list. It was the only thing that I believed was within the vicinity of affecting the iframes on the list.

Thanks for testing my suggestion.

 

I've attached an export of the registry key that worked for me too.

Highlighted

@rob_farnell & @andrewtchilds - thanks guys, that has fixed it for me based on 1 day of testing today!

Highlighted

@rob_farnell 

I am sorry I could not reply to the question you asked because I was offline for a month.

 

@andrewtchilds 

Thanks for giving the answer to the conversation :smile: