Bridging the gulf between code and behavior in programming
CHI '95 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Debugging and the experience of immediacy
Communications of the ACM
IEEE Transactions on Software Engineering
Debugging reinvented: asking and answering why and why not questions about program behavior
Proceedings of the 30th international conference on Software engineering
FireCrystal: Understanding interactive behaviors in dynamic web pages
VLHCC '09 Proceedings of the 2009 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC)
Crossfire: multiprocess, cross-browser, open-web debugging protocol
Proceedings of the ACM international conference companion on Object oriented programming systems languages and applications companion
On the analysis of cascading style sheets
Proceedings of the 21st international conference on World Wide Web
Proceedings of the 34th International Conference on Software Engineering
The DynaRIA tool for the comprehension of Ajax web applications by dynamic analysis
Innovations in Systems and Software Engineering
| Hi-index | 0.00 |
Breakpoints are perhaps the quintessential feature of a de-bugger: they allow a developer to stop time and study the program state. Breakpoints are typically specified by selecting a line of source code. For large, complex, web pages with multiple developers, the relevant source line for a given user interface problem may not be known to the developer. In this paper we describe the implementation of breakpoints in dynamically created source, and on error messages, network events, DOMmutation, DOMobject property changes, and CSS style rule updates. Adding these domain-specific breakpoints to a general-purpose debugger for Javascript allows the developer to initiate the debugging process via Web page abstractions rather than lower level source code views. The breakpoints are implemented in the open source Fire-bug project, version 1.5, for the Firefox Web browser.