OK, I tried your suggestion, and the performance is about the same as
it was using the second revision in 1.3.1. The hovers execute about
quarter to a half second after you move your mouse over it. On the
plus side, when I am using 1.2.6, it is extremely fast and performance
has improved significa
Will try it out, thanks!
On Feb 18, 1:15 pm, James wrote:
> How about doing it this way:
>
> $("table tbody tr")
> .bind("mouseover", function(e) {
> $(e.target).parent().children("td").addClass("row_on");
> })
> .bind("mouseout", function(e) {
> $(e.target).pa
How about doing it this way:
$("table tbody tr")
.bind("mouseover", function(e) {
$(e.target).parent().children("td").addClass("row_on");
})
.bind("mouseout", function(e) {
$(e.target).parent().children("td").removeClass("row_on");
})
.bind("click", fu
The issue that I am having with doing it that way is that the hover
action is only triggered when a person mouses over the table. You can
move all around the table, but it won't trigger again until the mouse
is moved off and then back on the table. I need the over to be
triggered for every row. Is
It seems you're still binding several events to every and not
using event delegation.
Your goal is to make events like click and hover attached to the table
instead of on each row, such that your very top-level statements look
like:
$(table).click(function() {});
$(table).hover(
function()
OK, I rewrote the code, and the page loads a lot faster, but I ran
into another problem. Now the performance of the script slows down as
the length of the table increases. As I hover over a cell in the above
table that triggers the event, it may take a half second or so to
trigger. I tested the s
Thanks for the reply. I will try it and let you know how it goes.
On Feb 12, 2:02 pm, James wrote:
> Try looking into using Event Delegation for managing your events. This
> means, instead of attaching events to a specific elements (thus, many
> attachments and more processing time), you're atta
Try looking into using Event Delegation for managing your events. This
means, instead of attaching events to a specific elements (thus, many
attachments and more processing time), you're attaching just a single
event to the parent element and take actions for the children's
events. Here are some l
8 matches
Mail list logo
