View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000878 | Xdebug | Uncategorized | public | 2012-08-30 16:08 | 2020-03-12 18:01 |
| Reporter | Tgr | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | resolved | Resolution | won't fix | ||
| Product Version | 2.1.0 | ||||
| Summary | 0000878: HTML output breaks when started inside a tag | ||||
| Description | The fancy HTML display (for var_dump, stack traces etc.) becomes unreadable when it is preceded by an unclosed tag. | ||||
| Steps To Reproduce | Enable pretty stack traces on fatal errors and run this: <div class="<?php get_class() ?>">Foo</div> This would create a non-existent method fatal error message with a stack trace table, but since the output starts within the attribute of a HTML tag, the <table> tag does not get interpreted by the browser, and the output becomes unreadable. Debug output inside a comment or a script tag has similar results. | ||||
| Additional Information | This could be avoided by prefxining the debug output with code to close open tags, such as <div style="display: none">--><script></script></div> this is normally invisible, not wildly invalid HTML, and breaks out of the most frequent enclosing markup. | ||||
| Tags | No tags attached. | ||||
| Operating System | |||||
| PHP Version | 5.3.9 | ||||
|
|
I am not going to change this. If you want to prevent Xdebug stopping your layout from breaking, use the http://xdebug.org/docs/all_functions#xdebug_start_error_collection and http://xdebug.org/docs/all_functions#xdebug_get_collected_errors |
