[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

Todd Kloots <todd.kloots at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |todd.kloots at gmail.com

--- Comment #4 from Todd Kloots <todd.kloots at gmail.com> ---
James, 

You raise some good points. Rather than trying to tackle this problem by having the History API trigger AX notifications by default, I wonder if a better solution would be to provide an API enabling developers the ability to trigger the right AX notification via JavaScript. This might be useful in cases where it _is_ appropriate to tell the user that the URL changed and move the virtual navigation to the top of the page. For example: on twitter.com all the navigation within the site is done via pushState. If the user moves from /home to /i/notifications moving the cursor to the top of the page seems appropriate.

Todd

-- 
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/20160401/606f4918/attachment.html>