On Feb 12, 2009, at 1:28 PM, ajpiano wrote:
>
> I don't know how much harder the point that @ is gone can be driven
> home. It was deprecated in 1.2.6. A major problem is bad/outdated
> tutorials that are still telling people the wrong way.
Actually, it was deprecated in 1.1.4, but your point
> I don't know how much harder the point that @ is gone can be driven
> home. It was deprecated in 1.2.6. A major problem is bad/outdated
> tutorials that are still telling people the wrong way.
Actually, it was deprecated in jQuery 1.2.0 - back in 2007.
--John
--~--~-~--~~---
I don't know how much harder the point that @ is gone can be driven
home. It was deprecated in 1.2.6. A major problem is bad/outdated
tutorials that are still telling people the wrong way.
On Feb 12, 10:35 am, David Zhou wrote:
> Actually, nevermind. I forgot there was a changes section:
>
>
Actually, nevermind. I forgot there was a changes section:
http://docs.jquery.com/Release:jQuery_1.3#Upgrading
Maybe change the "Changes" name to something more explicit like
Backwards Incompatible Changes? Right now, a person scanning the
release note headers could easily misconstrue that as
I wonder if it would be helpful to have a backwards incompatible
changes section for every jQuery release, and a master page somewhere
collating all those changes. The changes are usually highlighted in
the release notes, but it'd be more clear if there was a section
specifically calling out the
This sounds more like a problem of circumstances. IE was being
unhelpful and not providing the nice error message that we specified -
and the error was only happening in IE (since the fix was browser
specific). All of it was very unfortunate - but I'm not sure if
there's a lot that we can do on ou
