E-mail List Archives
Re: JAWS 14 issues with partial view reloads for Single Page Java web applications
From: _mallory
Date: Jul 22, 2015 1:11AM
- Next message: Mary Elizabeth Sullivan: "Re: JAWS 14 issues with partial view reloads for Single Page Java web applications"
- Previous message: Subhash Chhetri: "Re: Tiny clickable element: does this fail WCAG2?"
- Next message in Thread: Mary Elizabeth Sullivan: "Re: JAWS 14 issues with partial view reloads for Single Page Java web applications"
- Previous message in Thread: Mary Elizabeth Sullivan: "Re: JAWS 14 issues with partial view reloads for Single Page Java web applications"
- View all messages in this Thread
On Tue, Jul 21, 2015 at 05:42:50PM +0100, <EMAIL REMOVED> wrote:
> You are right that document ready is too early to affect content loaded in
> via AJAX, but instead of using a timeout (when you cannot guarantee it will
> run at the right time) you listen for the completion of the AJAX call.
It's too bad we don't have cross-UA mutation/object observers. But so
a Promise might indeed be the best thing for dealing with focus, instead
of setTimeouts.
Having JS determine focus instead of whatever browser default there is
can be desireable in cases where users (all of them) expect to stay in
the same page position even when new content loads (so long as it isn't
loading far away from current-position).
_mallory
- Next message: Mary Elizabeth Sullivan: "Re: JAWS 14 issues with partial view reloads for Single Page Java web applications"
- Previous message: Subhash Chhetri: "Re: Tiny clickable element: does this fail WCAG2?"
- Next message in Thread: Mary Elizabeth Sullivan: "Re: JAWS 14 issues with partial view reloads for Single Page Java web applications"
- Previous message in Thread: Mary Elizabeth Sullivan: "Re: JAWS 14 issues with partial view reloads for Single Page Java web applications"
- View all messages in this Thread