[Webkit-unassigned] [Bug 155399] AX: Investigation: Determine if document history pushState() and replaceState() should trigger additional AX notifications

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=155399

--- Comment #3 from James Craig <jcraig at apple.com> ---
A few negative case examples from some internal discussion:

"""
AK: Browse to http://www.apple.com/shop/buy-iphone/iphone5s
Select the appropriate options e.g. Space Gray, 16GB, Unlocked.
The URL updates to http://www.apple.com/shop/buy-iphone/iphone5s/16gb-space-gray

It’s appropriate to tell the user that the URL changed (even though this is replaceState) but definitely not appropriate to move their focus.

...
With pushState, we would rarely use a hash in the URL. That’s the fallback old style behaviour, where you need no .history() object. We would instead use a “real” URL that can be shared, bookmarked, and so on - and reacted to server-side (which is great SEO) rather than detecting the hash via JS.
"""

and

"""
CS: While yes, devs should be moving focus correctly, I fear that it would degrade the UX for AT users to have focus jumped for sites that already have poor AX.

Also, I can see having fixed timings causing a lot of issues on slow networks, and just being hard to debug (race conditions). E.g. I might update the URL on user click, but it takes longer to get the new content than ~500ms.
"""

I will close as WORKFORME if there are no objections or strong counterpoints.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160315/c9f8ae8f/attachment-0001.html>