Hi Karl,
There are three primary reasons for controlling it from the server:
1) MIME processing,
2) More optimal to pass only whats necessary (a message can be large),
and
3) Security wise, its safer,
I've been able (for now) to get around this hangup by wrapping the
truncated content with and
Hey Brandon,
Thanks so much for investigating these issues, and especially for the
advice on using .filter() instead of .not(). I'll update the clueTip
script to use that as a default.
As for the truncation, I suggested to Hector off-list that he use the
truncate option built into the clu
An invalid DOM is unpredictable and difficult to work around. I would think
that the hang up would probably be in jQuery.clean but I'm not positive.
Perhaps there is a better way to handle limiting the amount of information
within the clue tip. Maybe use CSS to set overflow: hidden along with a set
Hi Brandon,
Maybe you can assist here as well.
What started this was finding jQuery, actually the jQuery.ClueTip.js
plugin hanging the browser to the point of ending the task. During
the investigation and isolating the code to the testFilter() function,
I found the other .not issue.
Karl and I
Perfect!
Maybe JR can make this into a .notAll() function in 1.2.1.1.1.1.1 :-)
Thanks Brandon!
--
HLS
On Sep 22, 8:34 pm, "Brandon Aaron" <[EMAIL PROTECTED]> wrote:
> Oh okay... So, the code is working, it matches only the DIV and appends that
> DIV. However, that DIV still contains the other
Oh okay... So, the code is working, it matches only the DIV and appends that
DIV. However, that DIV still contains the other elements. The .not method
doesn't actually remove elements from the DOM just from the jQuery
collection. I can see how this can be confusing for what you are trying to
achiev
Hi Brandon,
Let me try this
I'm not seeing it work. Here is my test code. I tried all 3 methods:
//