Speed up onmouseover of rows and cols

[johkar]

This code from siteexperts.com tends to be slow onmouseover if you get
more than a 50 rows. Suggestions for increasing speed?

http://www.siteexperts.com/tips/styles/ts25/page1.asp

Thanks, John

var rowHighlight = true // turn on row highlights
var colHighlight = true // turn off row highlights

function getElement(el) {
var tagList = new Object
for (var i = 1; i < arguments.length; i++)
tagList[arguments[i]] = true
while ((el!=null) && (tagList[el.tagName]==null))
el = el.parentElement
return el
}

function checkHighlight(which) {
var el = getElement(event.srcElement,"TH","TD")
if (el==null) return
if ((el.tagName=="TH") && (colHighlight)) {
var idx = el.cellIndex
var table = getElement(el, "TABLE")
var column = table.all.tags("COL")[idx]
if (which)
column.className="cover"
else
column.className=""
}
if ((el.tagName=="TD") && (rowHighlight)) {
var row = getElement(el, "TR")
var table = getElement(row, "TABLE")
if (which)
row.className = "rover"
else
row.className = ""
cache = row
}
}

[Philip Ronan]

On 22/9/04 12:05 pm, johkar wrote:

This code from siteexperts.com tends to be slow onmouseover if you get
more than a 50 rows. Suggestions for increasing speed?

http://www.siteexperts.com/tips/styles/ts25/page1.asp

What is it supposed to do? In IE5.1 the runtime errors occur pretty much
instantaneously when you move your mouse over the table. You need faster
errors, or what?

--
Philip Ronan
ph***********@virgin.net
(Please remove the "z"s if replying by email)

[Yann-Erwan Perio]

johkar wrote:

This code from siteexperts.com tends to be slow onmouseover if you get
more than a 50 rows. Suggestions for increasing speed?

http://www.siteexperts.com/tips/styles/ts25/page1.asp if (which)
column.className="cover"
else
column.className=""

Setting the className property is much more expensive than setting a
simple style property! Try switching to style updates instead of
className updates.

Also, passing the 'this' value to the functions, and minimizing node
lookups, could be a good idea. On a different level, rewriting the
script and using caching systems may be interesting (removing mouseout
handler).
HTH,
Yep.

[Thomas 'PointedEars' Lahn]

Yann-Erwan Perio wrote:

Setting the className property is much more expensive than setting a
simple style property!

Why should it?
PointedEars
--
"A low voter turnout is an indication
of fewer people going to the polls."
-- Dan Quayle

[Jim Ley]

On Sun, 03 Oct 2004 21:34:15 +0200, Thomas 'PointedEars' Lahn
<Po*********@web.de> wrote:

Yann-Erwan Perio wrote:

Setting the className property is much more expensive than setting a
simple style property!

Why should it?

because the CSS cascade needs to be re-computed.

Jim.

[Thomas 'PointedEars' Lahn]

Jim Ley wrote:

Thomas 'PointedEars' Lahn wrote:

Yann-Erwan Perio wrote:

Setting the className property is much more expensive than
setting a simple style property!

Why should it?

because the CSS cascade needs to be re-computed.

As it would be if the "style" property/attribute changes.
That property/attribute is not off the cascade.
PointedEars

[Jim Ley]

On 5 Oct 2004 10:18:29 GMT, "Thomas 'PointedEars' Lahn"
<Po*********@web.de> wrote:

Jim Ley wrote:

Thomas 'PointedEars' Lahn wrote:

> Yann-Erwan Perio wrote:
> > Setting the className property is much more expensive than
> > setting a simple style property!
> Why should it?

because the CSS cascade needs to be re-computed.

As it would be if the "style" property/attribute changes.
That property/attribute is not off the cascade.

Except of course setting a single property on a style doesn't need to
compute as much of the cascade (inline style can only influence direct
descendants, class can of course do much more.)

Jim.