Closed StefanRiedmann closed 6 years ago
Changing base href in index.html to this value solved the issue:
<script>document.write('<base href="' + document.location + '" />');</script>
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.
I'm submitting a...
Current behavior
Using Angular in an (offline) Extension for Adobe Illustrator. On Windows, these are installed under C:\Program Files (x86)\Common Files\Adobe\CEP\extensions
On startup, I get this error ERROR Error: Uncaught (in promise): Error: Cannot match any routes. URL Segment: 'x86'
Apparently, the (x86) part of the url (filepath) is generating issues in parsing the url segments. I already tried solving this with different values for 'base href...'.
The problem is that I can't use 'base href="/"', because that just leads to this error on load: Failed to load resource: net::ERR_FILE_NOT_FOUND
Expected behavior
The url segment loading/parsing should be able to handle this local filepath containing '... x86 ...'.
Minimal reproduction of the problem with instructions
I couldn't reproduce it yet with a minimal Angular application inside a path containing x86. I'm working on it still.
What is the motivation / use case for changing the behavior?
Make routing work in local Angular applications
Environment