What's the impact overall? Is this a result of upgrade to JQuery
1.3.1?
Thanks, Tim
On Feb 16, 4:51 pm, David Pollak feeder.of.the.be...@gmail.com
wrote:
Folks,
It turns out that there are issues with jQuery's methods that insert/replace
HTML and using XHTML on Firefox. Sigh.
We should be
On Mon, Feb 16, 2009 at 9:04 AM, Tim Perrett he...@timperrett.com wrote:
What's the impact overall?
The impact is: use innerHTML directly rather than going through jQuery's
HTML re-writing.
Is this a result of upgrade to JQuery
1.3.1?
No. This is a latent Firefox bug and has to do with
How about adding a class-attribute called gc to everything that's
supposedly collectible?
Then doing a scrape using jQuery(.gc) would be just as feasible.
Would it solve the problem or can it be extended to solve it fully?
On Mon, Feb 16, 2009 at 10:37 PM, David Pollak
what would the raw XHTML look like?
Also, we can't rely on jQuery to scrape because we have to support other
libraries (e.g., YUI) without jQuery.
On Mon, Feb 16, 2009 at 1:45 PM, Viktor Klang viktor.kl...@gmail.comwrote:
How about adding a class-attribute called gc to everything that's
This might be a bit of a pain to deal with, but something like:
tag class=lift-gc lift-gc-[uuid] /
Of course, you'd want to append to the 'class' attribute, not replace it
entirely.
--j
On Mon, Feb 16, 2009 at 1:49 PM, David Pollak feeder.of.the.be...@gmail.com
wrote:
what would the raw
I wonder if 1,000 missing classes will cause the CSS engines to barf.
Anyone want to mock up a page or two and feed them into IE6, etc.?
On Mon, Feb 16, 2009 at 2:15 PM, Jorge Ortiz jorge.or...@gmail.com wrote:
This might be a bit of a pain to deal with, but something like:
tag