Re: [Edbrowse-dev] Short Timers

[Adam Thompson <arthompson1990@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1481 bytes --]

On Wed, Apr 08, 2015 at 09:19:51AM -0400, Karl Dahlke wrote:
> If you call up www.eventbrite.com you'll notice 10 javascript timers
> at the top of the page, all active in 4 milliseconds.
> It occurs to me that if javascript is suppose to run in 4 ms,
> it should probably just run.
> Now if js is scheduled to run in 10 seconds, then it should wait on your command,
> wait for you to read the page, because we read a new website slower than
> our sighted friends, so long timers are under our control,
> but perhaps any timer under one second, or whatever threshold we choose,
> should just run.
> Queue them up in order of time and run them.
> Even if they do nothing other than visual effects,
> at least those first ten annoying lines about js timers
> would be off of the web page.
> What do you think?

I think, as I've always thought, that we should have a mechanism where js
timers run when js timers are scheduled to run,
irrespective of any reading speed differences you believe exist (in actual fact
I've found in some cases I read pages *faster* than sighted friends,
and don't see this as a valid argument).
In addition, given the way web 2.0 works,
we realy need to get rid of the manual timer mechanism sooner rather than later
as otherwise timing critical ajax stuff can *never* work,
since i'm very unlikely to be able to keep activating js timers at the top of 
the page in the correct order to make a form submit etc.

Cheers,
Adam.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]