Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

dart.openDevTools setting ignores embedded flag and always opens in a browser

See original GitHub issue

Not sure if it’s a bug or desired behavior.

As I know, embedded Dev Tools are enabled by default. From my observations, for Windows device embedded Dev Tools are opened inside VSCode windows, but for Web/Chrome device Dev Tools always opened in browser even if I explicitly set dart.embedDevTools to true explicitly.

What is desired behavior? Should embedded Dev Tools not open for Web device or this my be caused by some environment configuration on my machines (iItested on home and work PC)?

Issue Analytics

State:
Created 2 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

roman-petrovcommented, Apr 6, 2021

@DanTup thank you for great product & support!

0reactions

roman-petrovcommented, Apr 6, 2021

seems to be a good workaround, thank you!

Top Results From Across the Web

How to remove Dart DevTools? - flutter

To disable DevTools: Open VS Code settings and search for Dart: Open Dev Tools and set it to never . (Removing "dart.

Have Chrome flag to automatically open developer tools in ...

I think automatically opening DevTools on all pages opened from the page ... a "Auto open Dev Tools for the following urls" field...

Dart DevTools

Open DevTools and connect to the target app. Copy the Dart DevTools debugger and profiler URL, and paste it into the address bar...

ipcmain handle vs on - You.com | The Search Engine ...

Open side panel ... returnValue would be set too late and the response wouldn't work. ... ipcMain; // In renderer process (web page)....

Security Bulletin 15 Dec 2021

CVE Number Base Score Reference CVE‑2019‑3398 8.8 https://nvd.nist.gov/vuln/detail/CVE‑2019‑3398 CVE‑2019‑3394 8.8 https://nvd.nist.gov/vuln/detail/CVE‑2019‑3394 CVE‑2021‑22112 8.8 https://nvd.nist.gov/vuln/detail/CVE‑2021‑22112