Well, the select lists everyone that has access to utilize the ticketing
system for submitting feedback/kudos on them, so everyone needs to be in the
select.
I'll try the suggestions here.
Thanks for all the good advice!
On Tue, Sep 22, 2009 at 3:49 AM, DBJDBJ <dbj...@gmail.com> wrote:
>
> Web 2.0 Apps and "multi-thousand chidlren" dom collections is an issue
> (aka: problem) I already am thinking about.
> There will be a point in a "single page + ajax" web apps which will
> make this (widely used) ad-hoc app design not-feasible.
> And Matt's problem is showing this clearly. Not yet, but probably
> soon, if huge ajax result sets do result in generation of huge dom
> collections , even direct dom manipulation will show a visible (over 1
> sec) delay.
>
> --DBJ
>
> PS: Why such a large number of options in a single select ? In any
> case since we are in a "visible delay" problem teritory, maybe this
> innocent looking advice will help :
>
> "Always use (one dom node as) the jQuery context argument"
>
> In your case :
> Instead of this : $("#mySelect").find("option:selected").text()
> use this: $("option:selected", document.getElementById
> ("mySelect") ).text()
>
> And yes, context argument will "work" only if it is a single dom
> node. Documented and proved by "the Team".
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-dev@googlegroups.com
To unsubscribe from this group, send email to
jquery-dev+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
