WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
Bug 82644
InputType attribute changed functions should happen after the attribute change
https://bugs.webkit.org/show_bug.cgi?id=82644
Summary
InputType attribute changed functions should happen after the attribute change
Joseph Pecoraro
Reported
2012-03-29 12:48:39 PDT
InputType::disabledAttributeChanged and InputType::readonlyAttributeChanged should happen after the attribute has actually changed. This way if the InputType looks at the state, it would correctly get the new value, not the old value.
Attachments
[PATCH] Proposed Fix
(1.56 KB, patch)
2012-03-29 12:52 PDT
,
Joseph Pecoraro
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Joseph Pecoraro
Comment 1
2012-03-29 12:52:10 PDT
Created
attachment 134649
[details]
[PATCH] Proposed Fix Saw this while looking at: <
http://webkit.org/b/82558
> Toggling <input type="range"> readonly or disabled state while active breaks all click events It doesn't really make sense to call the changed function until the value has actually changed!
Eric Seidel (no email)
Comment 2
2012-03-29 13:13:06 PDT
Comment on
attachment 134649
[details]
[PATCH] Proposed Fix OK. How do we observe this?
Joseph Pecoraro
Comment 3
2012-03-29 13:39:28 PDT
(In reply to
comment #2
)
> (From update of
attachment 134649
[details]
) > OK. How do we observe this?
This doesn't change any existing behavior. The only user of these InputType functions doesn't turn around and change the readonly / disabled state of the input. But if someone wanted to do that than this ordering would matter. I had a patch that used these functions and this confused me. To fix the problem we did not go with that patch, but I still wanted to fix this issue.
Joseph Pecoraro
Comment 4
2012-03-29 13:40:30 PDT
(In reply to
comment #3
)
> (In reply to
comment #2
) > > (From update of
attachment 134649
[details]
[details]) > > OK. How do we observe this? > > The only user of these InputType functions doesn't turn around and > change the readonly / disabled state of the input.
I typo'd. This should have said, ".. doesn't turn around and check the state..."
Benjamin Poulain
Comment 5
2012-03-29 14:04:03 PDT
Comment on
attachment 134649
[details]
[PATCH] Proposed Fix This looks correct to me. I see why you cannot test this, no InputType rely on the attribute value in response to disabledAttributeChanged() or readonlyAttributeChanged().
WebKit Review Bot
Comment 6
2012-03-29 15:32:57 PDT
Comment on
attachment 134649
[details]
[PATCH] Proposed Fix Clearing flags on attachment: 134649 Committed
r112589
: <
http://trac.webkit.org/changeset/112589
>
WebKit Review Bot
Comment 7
2012-03-29 15:33:01 PDT
All reviewed patches have been landed. Closing bug.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug