Author Topic: Issue with EXPORT HTML and new browsers version (edge, chrome, firefox 68+)  (Read 320 times)

mathieu31

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile

Hi everyone :)
i am using enterprise architect as system modeling tool and i export some diagrams/packages via export HTML throught native sparx export. (i use default web style template in Resources)
it worked well until new browsers decided to consider access to file system as a security threat.
With last versions of web browsers (chrome, edge, firefox 68+...), it seems file system protocol is not authorized anymore including for example navigation to file:// URLs from non-file:// URLs. As a consequence, when HTML export tries to load its table of content and related elements of this export, it does not work.
Is there a way to bypass this problem ?
re-code javascript ?
access throught HTTP protocol via local web server ?
 Is there smb facing same issues ?

thx in advance for your valuable advice
best regards :)

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 10438
  • Karma: +343/-30
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Issue with EXPORT HTML and new browsers version (edge, chrome, firefox 68+)
« Reply #1 on: September 10, 2020, 07:14:42 pm »
There's two ways to solve this

1. Start Chrome with the parameter to allow local access "--allow-file-access-from-file" (thus exposing you to that security risk)
2. Publish the html model with a webserver like IIS (or upload them to sharepoint)

Geert

mathieu31

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: Issue with EXPORT HTML and new browsers version (edge, chrome, firefox 68+)
« Reply #2 on: September 10, 2020, 10:42:04 pm »
thx geert for your answer.
I suspected it

best regards

mat

Uffe

  • EA Practitioner
  • ***
  • Posts: 1778
  • Karma: +122/-14
  • Flutes: 1; Clarinets: 1; Saxes: 5 and counting
    • View Profile
Re: Issue with EXPORT HTML and new browsers version (edge, chrome, firefox 68+)
« Reply #3 on: September 10, 2020, 11:30:52 pm »
Hello,

3. Publish to Joomla.
4. Buy the cloud server and use WebEA.

Not saying these are better, but they are alternatives.

/Uffe
My theories are always correct, just apply them to the right reality.

Richard Freggi

  • EA User
  • **
  • Posts: 306
  • Karma: +11/-5
    • View Profile
Re: Issue with EXPORT HTML and new browsers version (edge, chrome, firefox 68+)
« Reply #4 on: September 11, 2020, 01:00:45 pm »
There's two ways to solve this

1. Start Chrome with the parameter to allow local access "--allow-file-access-from-file" (thus exposing you to that security risk)
2. Publish the html model with a webserver like IIS (or upload them to sharepoint)

Geert

I thought the html documentation would not work in sharepoint because sharepoint disables javascript and hyperlinks between files?  Asking for a friend.

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 10438
  • Karma: +343/-30
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Issue with EXPORT HTML and new browsers version (edge, chrome, firefox 68+)
« Reply #5 on: September 11, 2020, 02:31:32 pm »
I thought the html documentation would not work in sharepoint because sharepoint disables javascript and hyperlinks between files?  Asking for a friend.
It does. I've had a number of clients who published the HTML export on sharepoint.
Don't know the technical details though.

Geert