New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 672486 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Output of DOM.getDocument has stale attributes

Project Member Reported by joaodasilva@chromium.org, Dec 8 2016

Issue description

Verified on Linux 56.0.2924.14 unstable.

If the HTML file contains:

<input type="text" value="foo">

Then DOM.getDocument() always reports the "value" attribute set to "foo", even after the user edits the input element.

Runtime.getProperties() on that node returns the correct "value" though.

I'm surprised because DOM.getDocument() is always returning the declared value for attributes, but it picks up mutations in the DOM i.e. new node, moved nodes, etc.
 
Status: WontFix (was: Untriaged)
AFAIK, this is the classic difference between attributes and properties.

the value should be equivalent to getting elem.getAttribute('value') which is also stale after a user edit. :)

agree it doesnt make sense, but it's expected behavior.

Sign in to add a comment