RESOLVED FIXED 158198
AX: iOS: VoiceOver can't access attachments in mail messages
https://bugs.webkit.org/show_bug.cgi?id=158198
Summary AX: iOS: VoiceOver can't access attachments in mail messages
chris fleizach
Reported 2016-05-30 00:20:49 PDT
VoiceOver is not able to access attributed strings with attachments in them on iOS <rdar://problem/26523054>
Attachments
Patch (8.19 KB, patch)
2016-05-30 00:31 PDT, chris fleizach
no flags
Patch (9.54 KB, patch)
2016-05-31 12:51 PDT, chris fleizach
buildbot: commit-queue-
Archive of layout-test-results from ews126 for ios-simulator-wk2 (699.38 KB, application/zip)
2016-05-31 13:46 PDT, Build Bot
no flags
Patch (11.25 KB, patch)
2016-06-01 11:39 PDT, chris fleizach
no flags
Patch (9.98 KB, patch)
2016-06-01 11:40 PDT, chris fleizach
no flags
chris fleizach
Comment 1 2016-05-30 00:31:40 PDT
Created attachment 280075 [details] Patch There's no expected file right now. Couldn't make simulator run for me. Hoping build bots produce expected result
chris fleizach
Comment 2 2016-05-31 12:51:10 PDT
chris fleizach
Comment 3 2016-05-31 12:51:43 PDT
Joanmarie: ready for review if you have a chance
Build Bot
Comment 4 2016-05-31 13:46:02 PDT
Comment on attachment 280169 [details] Patch Attachment 280169 [details] did not pass ios-sim-ews (ios-simulator-wk2): Output: http://webkit-queues.webkit.org/results/1413955 New failing tests: accessibility/ios-simulator/attributed-string-for-range.html
Build Bot
Comment 5 2016-05-31 13:46:05 PDT
Created attachment 280174 [details] Archive of layout-test-results from ews126 for ios-simulator-wk2 The attached test failures were seen while running run-webkit-tests on the ios-sim-ews. Bot: ews126 Port: ios-simulator-wk2 Platform: Mac OS X 10.11.4
chris fleizach
Comment 6 2016-05-31 16:44:09 PDT
(In reply to comment #5) > Created attachment 280174 [details] > Archive of layout-test-results from ews126 for ios-simulator-wk2 > > The attached test failures were seen while running run-webkit-tests on the > ios-sim-ews. > Bot: ews126 Port: ios-simulator-wk2 Platform: Mac OS X 10.11.4 Ah, debug vs. Release -(NSString *)description not implemented in release
chris fleizach
Comment 7 2016-06-01 11:39:20 PDT
chris fleizach
Comment 8 2016-06-01 11:40:17 PDT
Joanmarie Diggs
Comment 9 2016-06-01 13:46:00 PDT
Comment on attachment 280252 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=280252&action=review > Source/WebCore/ChangeLog:8 > + Replaced elements, like attachemnts, were not being exposed in the attributed string returned to VoiceOver. nit: attachments > Source/WebCore/accessibility/ios/WebAccessibilityObjectWrapperIOS.mm:65 > + NSAttachmentCharacter = 0xfffc /* To denote attachments. */ It looks like this will be the third place this character is being defined (the other two being editing/cocoa/HTMLConverter.mm and platform/mac/WebNSAttributedStringExtras.mm). Would it make sense to define it once in a platform header?
WebKit Commit Bot
Comment 10 2016-06-01 14:25:45 PDT
Comment on attachment 280252 [details] Patch Clearing flags on attachment: 280252 Committed r201568: <http://trac.webkit.org/changeset/201568>
WebKit Commit Bot
Comment 11 2016-06-01 14:25:50 PDT
All reviewed patches have been landed. Closing bug.
chris fleizach
Comment 12 2016-06-01 17:24:21 PDT
(In reply to comment #9) > Comment on attachment 280252 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=280252&action=review > > > Source/WebCore/ChangeLog:8 > > + Replaced elements, like attachemnts, were not being exposed in the attributed string returned to VoiceOver. > > nit: attachments > > > Source/WebCore/accessibility/ios/WebAccessibilityObjectWrapperIOS.mm:65 > > + NSAttachmentCharacter = 0xfffc /* To denote attachments. */ > > It looks like this will be the third place this character is being defined > (the other two being editing/cocoa/HTMLConverter.mm and > platform/mac/WebNSAttributedStringExtras.mm). Would it make sense to define > it once in a platform header? https://bugs.webkit.org/show_bug.cgi?id=158287
Note You need to log in before you can comment on or make changes to this bug.