Orange skin display issues with Edge Legacy - home page gap; topic content missing

[marcquesd85662268]

Hello,

Our clients have recently informed us of several display issues when using the legacy version of Microsoft Edge (non-Chromium). We have created output using the Orange skin. I have tested and confirmed all these issues by creating a new, blank project, using an unmodified Orange skin, and observing the results.

The issues are as follows:

1. The Home page displays a large gap between the drilldown tils at the top and any content you select for the home page
   • This appears to be due to an incorrect "calc" in layout.css that Legacy Edge interprets incorrectly. In Chrome and FF, it correctly shows as 100% - 29em. Legacy Edge shows it as -29em + 100%
2. The home page footer displays in the middle of the linked topic content, likely due to #1
3. Content on topic pages does not display. Only the breadcrumb headres for the topic show. This only occurs on a web server environtment; this works as expected locally.

I have noticed that the console in Edge Legacy reports errors with the opening XML tags from RoboHelp, where it considers the question mark in the <?XML tag to be incorrect formatting.

Any guidance on how to resolve these issues would be appreciated. These issues seem new since we upgraded to RoboHelp 2020; we did not have reproted issues in Edge Legacy with RoboHelp 2019.

Please see screenshots attached. 

Topic page local

Topic page on server

Large gap between tiles and front page content

[Peter Grainge]

I'm not sure that legacy Edge was supported in 2019. It may have been that prior to 2020 the code behind the skins just happened to work but changes were made that required the Chrome based version.

I am trying to find out but you could try Support to check.

See https://helpx.adobe.com/contact/enterprise-support.other.html#robohelp for your support contact options.

[Peter Grainge]

Adobe have confirmed that the new versions were not certified for legacy Edge. It does look therefore as if you were lucky with 2019.

Changes were made to support accessibility so maybe that is what broke it for you.

[marcquesd85662268]

Thank you for the update. I will inform our support teams of this.