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

Issue 657430 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Inspector does not show checkedness of radio inputs

Reported by ceo.jaso...@gmail.com, Oct 19 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36

Steps to reproduce the problem:
1. Inspect a radio input
2.  Select one of them
3. Select another
4. Dev Tools does not mirror state of DOM
5. Set <input>.checked=true in console
6. Inspector does not update
7. Change "checked" attribute in inspector, input not checked (probably caused by "dirty checkedness" compliance with W3C standard, but still just terrible...more of a nice to have given the standard I suppose).

What is the expected behavior?
checked attribute should be added to element in inspector. Inspector should show valid information that doesn't deviate from <input>.checked in the console.

What went wrong?
Was trying to debug a css slideshow hack using checked inputs (original source here: http://www.cssscript.com/demo/basic-image-slideshow-with-pure-css/), and could not see which slide was being selected. This was maddening in debugging our implementation.

Did this work before? N/A 

Chrome version: 53.0.2785.143  Channel: n/a
OS Version: OS X 10.10.5
Flash Version: Shockwave Flash 23.0 r0

Even if we can't get changes in inspector to replicate back to the page, at the very least inspector should show the current state. Should not need to use the JS console to debug a JS-free slideshow implementation.
 
Cc: sureshkumari@chromium.org
Labels: Needs-Feedback
could you please provide the sample Html file to traige the issue further.


Thanks.

Comment 2 by caseq@chromium.org, Oct 21 2016

Status: WontFix (was: Unconfirmed)
Confusing as this might be, this is not a DevTools issue. Please note that checked attribute on a JavaScript element wrapper is not the same as HTML checked attribute we show on a tag in Elements panel -- these may actually be out of sync. So if on your demo page you evaluate

document.getElementById("item-3").setAttribute("checked", "checked")

this will actually have effect on what you see in the Elements panel.

The fact that blink doesn't mirror the JS and HTML values for checked attributes like it does for some others looks to be by the spec: the HTML one is for _initial_ checkedness and the IDL one is for current one (and BTW document.getElementById("item-3").checked = true will disregard dirty checkedness flag)

Cc: l...@chromium.org tkent@chromium.org
 Issue 913210  has been merged into this issue.

Sign in to add a comment