You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Extension version: Migration Toolkit for Applications v0.0.98 (preview)
Browsers:
Microsoft Edge 101.0.1210.32 (Official build) (64-bit)
Google Chrome 100.0.4896.127 (Official Build) (64-bit)
I tried the extension today and I was able to see the issues reported inside VSCode for a sample application, but when opening the report from VSCode it looks broken because the CSS/JS are not found, as in the screenshot below:
Opening the report in VSCode:
Website open in Edge (with the Developer Tools panel enabled):
The problem seems to be that there is a / encoded in the URL used to open the report. The extension tries to open the address http://localhost:61435/54fkx96i7-lqqqufhqb%5Cindex.html but it should be http://localhost:61435/54fkx96i7-lqqqufhqb/index.html instead (note the %5C is the / encoded). This encoded character causes the paths to all the CSS/JS resources to be computed as relative to the root of the web address, instead of relative to the folder (54fkx96i7-lqqqufhqb in this case).
When the correct URL is used, the report works correctly:
The correct location of the resources have the unique identifier in them, like this:
The text was updated successfully, but these errors were encountered:
dfuenzalida
changed the title
Report URL used in VSCode extension breaks CSS/JS URLs
Report URL opened from MTA extension breaks CSS/JS URLs
May 5, 2022
I tried the extension today and I was able to see the issues reported inside VSCode for a sample application, but when opening the report from VSCode it looks broken because the CSS/JS are not found, as in the screenshot below:
Opening the report in VSCode:
Website open in Edge (with the Developer Tools panel enabled):
The following URLs were broken (HTTP 404):
Likely cause
The problem seems to be that there is a
/
encoded in the URL used to open the report. The extension tries to open the address http://localhost:61435/54fkx96i7-lqqqufhqb%5Cindex.html but it should be http://localhost:61435/54fkx96i7-lqqqufhqb/index.html instead (note the%5C
is the/
encoded). This encoded character causes the paths to all the CSS/JS resources to be computed as relative to the root of the web address, instead of relative to the folder (54fkx96i7-lqqqufhqb
in this case).When the correct URL is used, the report works correctly:
The correct location of the resources have the unique identifier in them, like this:
The text was updated successfully, but these errors were encountered: