Navigation Menu

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

Jump to bottom

DOM Breakpoints don't work correctly with Dartium #13734

Closed
jacob314 opened this issue Oct 2, 2013 · 7 comments
Closed

DOM Breakpoints don't work correctly with Dartium #13734

jacob314 opened this issue Oct 2, 2013 · 7 comments
Assignees
@jacob314
Labels
type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@jacob314
Copy link
Member

jacob314 commented Oct 2, 2013

Setting a DOM breakpoint in the Dartium debug tools doesn't work when Dart code modified the DOM. You stop at a breakpoint but have no call stack.
@vsmenon
Copy link
Member

vsmenon commented Nov 14, 2013

Should we just not let DOM files be editable?

Added this to the M9 milestone.

@vsmenon
Copy link
Member

vsmenon commented Nov 14, 2013

Removed this from the M9 milestone.
Added this to the 1.1 milestone.

@jacob314
Copy link
Member Author

To be clear, these are breakpoints that trigger when the running application (Dart or JS) modifies the DOM of the webpage not when someone edits the HTML source for the page.
This should be fixed for 1.1. The main use case is you have no idea what Dart code is changing some piece of your UI so you set a breakpoint for that DOM subtree so you are notified right when code changes it.

@vsmenon
Copy link
Member

vsmenon commented Feb 27, 2014

Removed this from the 1.1 milestone.
Added this to the 1.3 milestone.

@vsmenon
Copy link
Member

vsmenon commented Jun 4, 2014

Removed this from the 1.3 milestone.
Added this to the 1.6 milestone.

@kasperl
Copy link

kasperl commented Jul 10, 2014

Removed this from the 1.6 milestone.
Added Oldschool-Milestone-1.6 label.

@kasperl
Copy link

kasperl commented Aug 4, 2014

Removed Oldschool-Milestone-1.6 label.

@jacob314 jacob314 self-assigned this Aug 4, 2014
@kevmoo kevmoo added type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) and removed priority-unassigned labels Feb 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jacob314 jacob314

Labels
type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@kevmoo @matanlurey @jacob314 @vsmenon @kasperl