Open Bug 1446473 Opened 7 years ago Updated 2 years ago

markupview expandAll throws if the node has more than 100 children

Categories

(DevTools :: Inspector, enhancement, P3)

enhancement

Tracking

(Not tracked)

People

(Reporter: jdescottes, Unassigned)

References

Details

Attachments

(1 file)

Attached file test_case.html
STRs: - open page in attachment - (open Browser Console to get the logs if not running a local build) - open the inspector - right click on the expand-me node in the markup view - Expand All ER: No errors in the logs (optionally, maybe the hidden nodes should be displayed automatically?) AR: Logs contain the following error: Full message: TypeError: container is undefined Full stack: _updateChildren@resource://devtools/shared/base-loader.js -> resource://devtools/client/inspector/markup/markup.js:1597:5 _expandContainer@resource://devtools/shared/base-loader.js -> resource://devtools/client/inspector/markup/markup.js:1152:12 _expandAll@resource://devtools/shared/base-loader.js -> resource://devtools/client/inspector/markup/markup.js:1177:12 _expandAll/<@resource://devtools/shared/base-loader.js -> resource://devtools/client/inspector/markup/markup.js:1181:23 Note that this doesn't really impact the behavior of the markup view, it's mostly inconvenient when trying to call expandAll programmatically.
See Also: → 1414286
Attachment #8959615 - Attachment mime type: text/plain → text/html
Product: Firefox → DevTools
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: