AEM 6.2 EDGE Browser Issues in Authoring | Community
Skip to main content
MarkJ_TX
Level 2
January 12, 2017
Question

AEM 6.2 EDGE Browser Issues in Authoring

  • January 12, 2017
  • 5 replies
  • 1353 views

Has anyone run into problems using EDGE Browser to edit in the authoring system?  We are running into issues where content gets deleted when trying to edit with EDGE.  If we drop EDGE to IE11 mode then it does not have any problems.  It seems that this only happens with components that utilize ACS Commons.  I am not sure if that is related or not.  We do no have any issues with IE11, Chrome or FF.

 

thanks

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

5 replies

edubey
Level 10
January 13, 2017

As per AEM docs, I don't think they support EDGE with 6.2, check here

https://docs.adobe.com/content/docs/en/aem/6-0/deploy/technical-requirements.html#Supported Browsers for Authoring User Interface

kautuk_sahni
Community Manager
Community Manager
January 13, 2017

edubey wrote...

As per AEM docs, I don't think they support EDGE with 6.2, check here

https://docs.adobe.com/content/docs/en/aem/6-0/deploy/technical-requirements.html#Supported Browsers for Authoring User Interface

 

Hi Praveen,

The link you just referred here is for AEM 6.0, but for 6.2, Edge is supported.

See:- https://docs.adobe.com/docs/en/aem/6-2/deploy/technical-requirements.html#Supported Browsers for Authoring User Interface

Kautuk Sahni
kautuk_sahni
Community Manager
Community Manager
January 13, 2017

Mark Jaggers wrote...

Has anyone run into problems using EDGE Browser to edit in the authoring system?  We are running into issues where content gets deleted when trying to edit with EDGE.  If we drop EDGE to IE11 mode then it does not have any problems.  It seems that this only happens with components that utilize ACS Commons.  I am not sure if that is related or not.  We do no have any issues with IE11, Chrome or FF.

 

thanks

 

Can you please specify the particulars to reproduce this? Which ACS commons component are behaving like this? Any error in browsers or AEM error.log ?

~kautuk

Kautuk Sahni
MarkJ_TX
MarkJ_TXAuthor
Level 2
January 16, 2017

We do not get any errors or see anything in the logs.  It only happens with components using acs-commons-nested="NODE_STORE"

kautuk_sahni
Community Manager
Community Manager
January 18, 2017

I have asked internal experts to have a look at this one.

~kautuk

Kautuk Sahni