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

Dartium ignores breakpoints set not in (no domain) category #21601

Closed
DartBot opened this issue Nov 13, 2014 · 1 comment
Closed

Dartium ignores breakpoints set not in (no domain) category #21601

DartBot opened this issue Nov 13, 2014 · 1 comment
Labels
closed-obsolete Closed as the reported issue is no longer relevant type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@DartBot
Copy link

DartBot commented Nov 13, 2014

This issue was originally filed by @PaulAnnekov


  1. Open "Developer tools" and "Sources" tab.
  2. Set breakpoint in some file inside the package's folder in category with your site's domain, e.g "127.0.0.1:8081".
  3. Set breakpoint in some file in category "(no domain)".

In first case this breakpoint will be ignored, in second one script will stop, so no issues.

As I understand breakpoints in category with your domain name works only for files that included directly with <script> tag. Breakpoints in files that was imported are ignored.

Plain list in "(no domain)" category is hard to use.

Dartium, chrome://version:
Google Chrome 38.0.2125.111 (Official Build 290379)
OS Linux
Blink 537.36 (@­183466)
JavaScript V8 3.28.71.17
Flash 15.0.0.189
User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.111 Safari/537.36
Command Line /opt/google/chrome/google-chrome --flag-switches-begin --flag-switches-end
Executable Path /opt/google/chrome/google-chrome
Profile Path /home/user/.config/google-chrome/Default
Variations d0bd833b-3f4a17df
f2d919bf-3f4a17df
e9f4800b-2d9ef0cc
76b48ab8-4866ef6e
c70841c8-4866ef6e
9e5c75f1-ed89c2b0
f79cb77b-3d47f4f4
24dca50e-837c4893
ca65a9fe-91ac3782
8d790604-9cb2a91c
4ea303a6-3d47f4f4
d8f57532-3f4a17df
61544484-ca7d8d80
b310ecc7-fcf6c09
9736de91-ca7d8d80
b2612322-f8cf70e2
5a3c10b5-e1cc0f14
244ca1ac-4ad60575
5e29d81-f23d1dea
3ac60855-486e2a9c
246fb659-bca011b3
f296190c-d0fe63d6
4442aae2-6bdfffe7
ed1d377-e1cc0f14
75f0f0a0-6bdfffe7
e2b18481-6e597ede
e7e71889-e1cc0f14
cbf0c14e-bf3e6cfd

Xubuntu 14.04.1 LTS


Attachment:
[Screenshot - 13.11.2014 - 22:58:07.png](https://storage.googleapis.com/google-code-attachments/dart/issue-21601/comment-0/Screenshot - 13.11.2014 - 22:58:07.png) (45.35 KB)

@DartBot
Copy link
Author

DartBot commented Nov 13, 2014

This comment was originally written by @PaulAnnekov


This bug was already announced in this comment: https://code.google.com/p/dart/issues/detail?id=13889#c9

@kevmoo kevmoo added type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) and removed triaged labels Mar 1, 2016
@matanlurey matanlurey added the closed-obsolete Closed as the reported issue is no longer relevant label Feb 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-obsolete Closed as the reported issue is no longer relevant type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Development

No branches or pull requests

3 participants