Bug 43004 - WebElement should provide access to attributes
Summary: WebElement should provide access to attributes
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Accessibility (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Windows Vista
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-26 14:36 PDT by Dominic Mazzoni
Modified: 2010-07-27 01:08 PDT (History)
3 users (show)

See Also:


Attachments
Implements proposed feature (15.66 KB, patch)
2010-07-26 14:54 PDT, Dominic Mazzoni
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Dominic Mazzoni 2010-07-26 14:36:06 PDT
For Windows accessibility, we need direct access to some of the attributes of a WebElement.
Comment 1 Dominic Mazzoni 2010-07-26 14:54:54 PDT
Created attachment 62616 [details]
Implements proposed feature
Comment 2 WebKit Review Bot 2010-07-26 14:58:20 PDT
Attachment 62616 [details] did not pass style-queue:

Failed to run "['WebKitTools/Scripts/check-webkit-style']" exit_code: 1
WebKit/chromium/src/WebAttribute.cpp:37:  Alphabetical sorting problem.  [build/include_order] [4]
WebKit/chromium/src/WebElement.cpp:39:  Alphabetical sorting problem.  [build/include_order] [4]
Total errors found: 2 in 8 files


If any of these errors are false positives, please file a bug against check-webkit-style.
Comment 3 chris fleizach 2010-07-26 16:43:57 PDT
Comment on attachment 62616 [details]
Implements proposed feature

is there any chance of getting a layout test with this?
Comment 4 Dominic Mazzoni 2010-07-26 18:33:18 PDT
This is all chromium wrapper code, and I have a chromium browser test ready for review that exercises these new APIs and makes sure they work. I'll send a link to the code review when I upload it.

I'm also happy to add a layout test as well, but is there any infrastructure now to access chromium wrappers like WebNode, WebElement from a layout test? As far as I can tell, building WebKit by itself doesn't even compile the code in the chromium/ directory...but if I'm missing something, please point me in the right direction!

- Dominic
Comment 5 chris fleizach 2010-07-27 00:30:06 PDT
(In reply to comment #4)
> This is all chromium wrapper code, and I have a chromium browser test ready for review that exercises these new APIs and makes sure they work. I'll send a link to the code review when I upload it.
> 
> I'm also happy to add a layout test as well, but is there any infrastructure now to access chromium wrappers like WebNode, WebElement from a layout test? As far as I can tell, building WebKit by itself doesn't even compile the code in the chromium/ directory...but if I'm missing something, please point me in the right direction!
> 
> - Dominic

I don't know anything about how chromium builds accessibility, but I imagine DumpRenderTree could be modified to accommodate testing these things. I think it would be useful to figure out how to write layout tests for changes like these
Comment 6 chris fleizach 2010-07-27 00:32:59 PDT
Comment on attachment 62616 [details]
Implements proposed feature

r=me
Comment 7 WebKit Commit Bot 2010-07-27 01:08:02 PDT
Comment on attachment 62616 [details]
Implements proposed feature

Clearing flags on attachment: 62616

Committed r64112: <http://trac.webkit.org/changeset/64112>
Comment 8 WebKit Commit Bot 2010-07-27 01:08:06 PDT
All reviewed patches have been landed.  Closing bug.