WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
122104
[ATK] Expose state of aria-invalid as ATK_STATE_INVALID_ENTRY
https://bugs.webkit.org/show_bug.cgi?id=122104
Summary
[ATK] Expose state of aria-invalid as ATK_STATE_INVALID_ENTRY
Mario Sanchez Prada
Reported
2013-09-30 06:35:07 PDT
Besides exposing the value of aria-invalid as a text attribute (see
bug 122015
), we need to expose this attribute as well as a state for the given object, by means of ATK_STATE_INVALID_ENTRY
Attachments
Patch proposal
(7.17 KB, patch)
2013-10-03 08:45 PDT
,
Mario Sanchez Prada
no flags
Details
Formatted Diff
Diff
Patch proposal
(7.03 KB, patch)
2013-10-04 02:43 PDT
,
Mario Sanchez Prada
cfleizach
: review+
Details
Formatted Diff
Diff
Show Obsolete
(1)
View All
Add attachment
proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1
2013-09-30 06:36:11 PDT
<
rdar://problem/15110696
>
Mario Sanchez Prada
Comment 2
2013-09-30 06:47:26 PDT
Depending on
bug 122015
, since the changes in DRT/WKTR will be based on the patch for that bug
Mario Sanchez Prada
Comment 3
2013-10-03 08:45:48 PDT
Created
attachment 213251
[details]
Patch proposal
chris fleizach
Comment 4
2013-10-03 09:50:00 PDT
Comment on
attachment 213251
[details]
Patch proposal View in context:
https://bugs.webkit.org/attachment.cgi?id=213251&action=review
> Source/WebCore/accessibility/atk/WebKitAccessibleWrapperAtk.cpp:729 > + if (!invalidStatus.isEmpty() && invalidStatus != "false")
invalidStatus should never be empty based on previous patch you submitted
> Tools/DumpRenderTree/atk/AccessibilityUIElementAtk.cpp:1045 > + // If no text attribute was found, just return what the state says.
this comment is not necessary. you're just explaining what the code does rather than why it does it
> Tools/DumpRenderTree/atk/AccessibilityUIElementAtk.cpp:1051 > + if (isInvalidState != (attributeValue != "false"))
this is a little confusing. maybe split this into to two if/if statements for clarity?
Mario Sanchez Prada
Comment 5
2013-10-04 02:43:10 PDT
Created
attachment 213346
[details]
Patch proposal (In reply to
comment #4
)
> (From update of
attachment 213251
[details]
) > View in context:
https://bugs.webkit.org/attachment.cgi?id=213251&action=review
> > > Source/WebCore/accessibility/atk/WebKitAccessibleWrapperAtk.cpp:729 > > + if (!invalidStatus.isEmpty() && invalidStatus != "false") > > invalidStatus should never be empty based on previous patch you submitted
Argh... true. Changed it
> > Tools/DumpRenderTree/atk/AccessibilityUIElementAtk.cpp:1045 > > + // If no text attribute was found, just return what the state says. > > this comment is not necessary. you're just explaining what the code does rather than why it does it >
Removed
> > Tools/DumpRenderTree/atk/AccessibilityUIElementAtk.cpp:1051 > > + if (isInvalidState != (attributeValue != "false")) > > this is a little confusing. maybe split this into to two if/if statements for clarity?
I replaced it with this: bool isAriaInvalid = attributeValue != "false"; if (isInvalidState != isAriaInvalid) { return JSStringCreateWithCharacters(0, 0); } I guess that way is more clear now.
Mario Sanchez Prada
Comment 6
2013-10-08 03:54:04 PDT
Committed
r157096
: <
http://trac.webkit.org/changeset/157096
>
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