682432 - Add memory reporters for HTML element classes

Status: RESOLVED WORKSFORME

(Core :: DOM: Core & HTML, defect, P5)

Description

[Boris Zbarsky [:bzbarsky]]

See bug 678376 comment 10; there are various element classes in there.

Also, some elements can have nontrivial state.

Comment 1

[Mounir Lamouri (:mounir)]

By "element classes", do you mean classes inheriting from nsGenericHTMLElement?

Comment 2

[Boris Zbarsky [:bzbarsky]]

For a start, yeah.

Comment 3

[Andrew McCreight [:mccr8]]

Are we still lacking coverage for these?  Boris, what are some examples of elemenst with non-trivial state?

Comment 4

[Boris Zbarsky [:bzbarsky]]

nsHTMLInputElement (the editor state, possibly anonymous content, etc).

Image and canvas elements, though we may count that elsewhere.

Do we count slots structs?  All elements can have those.

SVG elements can have all sort of things hanging off them.

Comment 5

[Andrew McCreight [:mccr8]]

Okay, thanks!

Comment 6

[(no longer active)]

(In reply to Boris Zbarsky (:bz) from comment #4)
> nsHTMLInputElement (the editor state, possibly anonymous content, etc).

nsHTMLTextAreaElement too.

Comment 7

[Firefox Bug Husbandry Bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1472046

Move all DOM bugs that haven't been updated in more than 3 years and has no one currently assigned to P5.

If you have questions, please contact :mdaly.

Comment 8

[Nicholas Nethercote [inactive]]

I think we have coverage for all these things now.