colin.clark at utoronto.ca
Sun Jun 24 01:51:50 UTC 2007
I'm coming into this quite late and without having had time to look at
any of the code. My comments are below.
Antranig Basman wrote:
> The firefox explosion was indeed finally tracked down to the Dojo
> I18N libraries (by the painful and traditional process of binary
> This line in the component startup was causing the Firefox event loop
> to lock:
> dojo.requireLocalization("fluid", "instructions");
From my testing, this was a bug in FireFox 1.5. It worked fine for me
in FireFox 2.0.
A question for the Dojo folks: I've been trying to find a list of
supported browsers for the 0.9 release. Does such a thing exist, and if
so can you point me to the right place?
> I have also "arbitrarily" adjusted the number of nodes in the
> whitespace Utilities test so that it passes, but as I remarked
> to Anastasia in chat yesterday (now lost locally since it crashed!)
> I don't think this DOM-sensitive approach is the right one for
> the widget either, and hope that this whitespace logic will
> eventually go away entirely. We should really be operating a
> "swappage" model wrt. our lightbox cells rather than a "slippage"
Can you clarify what you mean by "swappage" vs. "slippage" here?
> Some non-crucial refactoring work to the server package structure,
> persistence is still a little way off.
I can't wait to see persistence in action!
Technical Lead, Fluid Project
Adaptive Technology Resource Centre, University of Toronto
More information about the fluid-work