| Summary: | AX: need to catch NSAccessibilityExceptions in DRT | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | chris fleizach <cfleizach> | ||||
| Component: | Accessibility | Assignee: | chris fleizach <cfleizach> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | abarth, bdakin, eric, webkit.review.bot | ||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | PC | ||||||
| OS: | OS X 10.5 | ||||||
| Attachments: |
|
||||||
|
Description
chris fleizach
2010-05-28 09:33:01 PDT
Created attachment 57341 [details]
patch
Comment on attachment 57341 [details]
patch
Don't we want to give the test access to the exception? Won't we want tests that expect exceptions and other tests that don't expect them? Maybe we can turn the exceptions into JavaScript exceptions?
r=me as is
filed https://bugs.webkit.org/show_bug.cgi?id=39885 to handle darin's request. as of yet, no layout tests need to know about these exceptions, but its possible in the future apparently tiger doesn't like having a NSMakeRange in a @try block. working on fix now http://trac.webkit.org/changeset/60366 might have broken Tiger Intel Release The following changes are on the blame list: http://trac.webkit.org/changeset/60368 http://trac.webkit.org/changeset/60369 http://trac.webkit.org/changeset/60370 http://trac.webkit.org/changeset/60366 http://trac.webkit.org/changeset/60367 http://trac.webkit.org/changeset/60372 might have broken GTK Linux 32-bit Debug The following changes are on the blame list: http://trac.webkit.org/changeset/60371 http://trac.webkit.org/changeset/60372 http://trac.webkit.org/changeset/60373 |