Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The Screenshot and text for Step 1 is now out of date #3019

Closed
BPapp-MS opened this issue Jan 16, 2024 · 3 comments · Fixed by #3040
Closed

The Screenshot and text for Step 1 is now out of date #3019

BPapp-MS opened this issue Jan 16, 2024 · 3 comments · Fixed by #3040
Labels
ADO cat: devtools DevTools-related content.

Comments

@BPapp-MS
Copy link

BPapp-MS commented Jan 16, 2024

There is now, importantly, an option for "Allow DevTools to load resources, such as source maps, from remote file paths" which must also be enabled in the DevTools Settings > Preferences screen


Document Details

Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

AB#48531703

@captainbrosset captainbrosset added cat: devtools DevTools-related content. and removed triage-needed labels Jan 17, 2024
@captainbrosset
Copy link
Contributor

Thanks for reporting this. I'll make sure this is on our backlog so we can prioritize and fix the issue.

@captainbrosset
Copy link
Contributor

After a deeper investigation, I realized that the Allow DevTools to load resources, such as source maps, from remote file paths option really only applies when the source map is loaded from a file:// URL.

@captainbrosset
Copy link
Contributor

With this in mind, I think it would make more sense to document this option under this more general source map section: https://learn.microsoft.com/en-us/microsoft-edge/devtools-guide-chromium/javascript/source-maps#enable-source-maps-in-settings

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ADO cat: devtools DevTools-related content.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants