#3 XHTML Strict compliance, ranking of results

[Dave Mahon]

I used WICK for a project that benefited from
autocompletion but didn't have any of the inherent
issues of an e-mail client.

Thus, I stripped out (most of) the code handling
multiple entries and substitution of e-mail addresses
and names.

Interface wise, I set unlimited results since I
couldn't be sure what the user was looking for. To
help, I created a very basic ranking system. The
earlier the search string appears in the entry, the
more likely the result. This could definitely be
tweaked further though.

When I implemented the scrolling div, I had to
eliminate all references to innerHTML. Otherwise, you
couldn't select results returned from below the initial
page. As a side effect, we end up with greater W3C
compliance.

Since innerHTML is measurably faster than node
creation, we only change the actual text when the user
changes the search string.

[Dave Mahon]

[Dave Mahon]

Logged In: YES
user_id=1440234

Forgot to mention, I also stripped out the document.write
that sets up the table, so you'll have to put forth a little
effort to re-integrate this.

Also, while the div doesn't update nearly as often, it's now
possible to actually select the displayed text. This is
bad. Any ideas on how to fix it?