WebUI[MD-refresh]: fix various tabindex issues for cr-input
This fixes a few bugs introduced by 1103002 to cr-input, as well as making cr-input more robust against edge-cases: likely cases: - |tabindex| initially set by element are mistakenly set to 0. - if element has both |tabindex| and |disabled| set, element would not know what to set |tabindex| to once |disabled| is removed. - clicking on a |disabled| cr-input would set its |tabindex| to 0 again. edge case: - if |disabled| is changed to true in the same cycle as pointerdown is fired, then |tabindex| state gets messed up. Bug: 832177, 856118 Cq-Include-Trybots: luci.chromium.try:closure_compilation Change-Id: I91161ecde90e816340aa38db4646b3f8eedd7a8b Reviewed-on: https://chromium-review.googlesource.com/1111201 Commit-Queue: Scott Chen <scottchen@chromium.org> Reviewed-by:Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#570198}
Showing
Please register or sign in to comment