Bug 163719

Created attachment 292162 [details] Test case When opening a URL with a fragment identifier, Safari correctly opens the new page and visually scrolls to the relevant part of the document referred to in the fragment/hash (if present). However, when VoiceOver is running, after the initial visual scroll VoiceOver resets the accessibility focus/caret all the way back to the first element at the very start of the document. This currently makes URLs with fragment identifiers useless for iOS/VO users (which is particularly problematic for very long documents, as VO users then have to still explicitly navigate all the way through the document to finally reach the actual section they were after). Video of the bug in action: https://www.youtube.com/watch?v=LvlM8Z71oWE Steps to reproduce: - with VoiceOver enabled, open a fresh tab in Safari - enter a URL with a fragment identifier (in the attached test case, there is a #target1, for instance) Expected: - Safari opens the document, visually scrolls to the location of the fragment identifier - VoiceOver sets accessibility focus/caret to the targeted element (or its first child element) Actual: - Safari opens the document, visually scrolls to the location of the fragment identifier - VoiceOver sets accessibility focus/caret to the very first element of the document - the visual viewport is scrolled back to the top of the document This is potentially a side effect of https://bugs.webkit.org/show_bug.cgi?id=116046, but filed separately as requested https://bugs.webkit.org/show_bug.cgi?id=116046#c57 The issue does not appear in Safari/VoiceOver on MacOS/OS X, so it seems iOS/Safari/VoiceOver specific.