Closed Shenniey closed 5 years ago
This issue only occurs on Microsoft Edge (Chromium) and not on EdgeHTML.
Step of reproduce: (Repro Gifs has been attached)
Run below commands in a command prompt: npm install -g @angular/cli ng new my-app cd my-app ng serve
npm install -g @angular/cli
ng new my-app
cd my-app
ng serve
Open my-app folder in another command prompt.
Configure the Edge debugger with launch.json file.
Set breakpoint at title = 'my-angular-app2; of app.component.ts.
title = 'my-angular-app2;
Launch Microsoft Edge (Chromium) against localhost(F5).
Add a Closure variable to the watch panel.
Result: Value shows up as 'not available' in watch panel (it is still correct in variables panel)
Full Repro Gif:
This is a bug on chromium. Please track this bug on chromium: https://bugs.chromium.org/p/chromium/issues/detail?id=992240
This issue only occurs on Microsoft Edge (Chromium) and not on EdgeHTML.
Step of reproduce: (Repro Gifs has been attached)
Run below commands in a command prompt:
npm install -g @angular/cli
ng new my-app
cd my-app
ng serve
Open my-app folder in another command prompt.
Configure the Edge debugger with launch.json file.
Set breakpoint at
title = 'my-angular-app2;
of app.component.ts.Launch Microsoft Edge (Chromium) against localhost(F5).
Add a Closure variable to the watch panel.
Result: Value shows up as 'not available' in watch panel (it is still correct in variables panel)
Full Repro Gif: