Summary: | CrashTracer: [USER] 300 crashes in Safari at com.apple.WebCore: WebCore::AccessibilityTable::isTableExposableThroughAccessibility + 573 | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | chris fleizach <cfleizach> | ||||
Component: | Accessibility | Assignee: | chris fleizach <cfleizach> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | bdakin | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | PC | ||||||
OS: | OS X 10.5 | ||||||
Attachments: |
|
Description
chris fleizach
2010-07-20 10:45:17 PDT
this can happen when you remove a row from a table, then add a row, then modify an attribute on the new row. That will cause the AccessibilityTable to see if it should be exposed as a table. That in turn will look at its grid of cells, accessing the row that was removed. the solution is that we cannot use getOrCreate in contentChanged(). we can only access AX elements already created. Actually a better solution is that the table cell should not getOrCreate its parent. it should only get it's parent. There's no real user cases where a table cell will be created in AX, before its AXTable is created Created attachment 62099 [details]
Patch
Comment on attachment 62099 [details]
Patch
r=me!
|