Currently we only have attributedStringForRange:(NSRange)range, and it's using the top document and TextIterator to figure out the right start/end point. For the case where we want to get the attributed string under some element, we shouldn't do such redundant work to walk from the beginning of the document to figure out the right range.
<rdar://problem/42872357>
Created attachment 346416 [details] patch
Comment on attachment 346416 [details] patch View in context: https://bugs.webkit.org/attachment.cgi?id=346416&action=review > Source/WebCore/accessibility/ios/WebAccessibilityObjectWrapperIOS.mm:2530 > + white space
Committed r234526: <https://trac.webkit.org/changeset/234526>