Hi,
I'm sorry but are you asking for more than what is above? I can
write a simple page that puts together the HTML and JS listed above.
Yes, there are a lot of details not included in that post, which may
be relevant. There are lots of good reasons to do a complete, stand-
alone test case,
Hi T.J.,
I tried out creating a unit test case for this and doing stuff on
page load and i cant seem to reproduce this on Safari on the desktop
anymore. Its odd because i think it might have to do with timing and
how long the browser takes to render the content into the DOM but i
can reproduce
This is not during DOM load but post dom load where i am trying to
insert more dom elements into the tree that i am seeing things not
always load.
On Nov 5, 12:37 pm, Matt Foster mattfoste...@gmail.com wrote:
In taking a second look at your code...
Are you using the F function recursively to
Hey Kiran,
Function.defer is simply delegating the functions execution to
Function.delay which in the end delegates it to a wrapper of
window.setTimeout.
By using defer it enforces the timeout to be a value of 0.01 which is
just enough to hiccup the browser's procedural processing.
If your
In taking a second look at your code...
Are you using the F function recursively to wait for the DOM to be
loaded and your area element to be available?
you can use many other approaches...
Prototype
$(document).observe(dom:loaded, function()...);
Traditional
window.onload = function()...
HI T.J,
I'm sorry but are you asking for more than what is above? I can
write a simple page that puts together the HTML and JS listed above.
Is that what you want?
Kiran
On Oct 30, 2:22 am, T.J. Crowder t...@crowdersoftware.com wrote:
Hi Kiran,
It sounds like you've already put together a
Hi Kiran,
It sounds like you've already put together a minimalist test case,
would you post it (e.g., to Pastie[1] or similar)? I haven't run into
a situation where a single defer wasn't sufficient, but I also haven't
tested extensively on Mac OS.
Cheers,
--
T.J. Crowder
Independent Software
