Upgrade jQuery version, used in administrative console

[Alexander Obuhovich]

I think, that we should upgrade jQuery version, used in administrative console. Also make sure, that all extensions of jQuery works properly after update. For example ThickBox may use $.browser, that most likely is not available in 1.4.x versions of jQuery.

--
Best Regards,

http://www.in-portal.com
http://www.alex-time.com

[Phil ..:: domicilis.biz ::..]

On front, 503-B1 is still using jQ 132 (released 1y. ago), while 142 is available now.

2010/3/29 Alexander Obuhovich <aik....@gmail.com>

To unsubscribe from this group, send email to in-portal-dev+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.

[Alexander Obuhovich]

We usually don't upgrade 3rd party libraries, just because there are new versions available. That's because nothing isn't upgraded until it's not compatible with current browser versions. Why bother if it already works.

[Dmitry Andrejev]

Alex, what was the main reason you wanted to upgrade Admin to JQ 1.4.x?

Front end, well - yes we kind of can do that too, but only once tested well. I say we create a task and add to 5.1.0?

DA.

[Phil -- wbtc.fr --]

Alex, I totally agree with your point, but I think front end could benefit of an updated jQuery.

I'm doing some cool little things with this, I'll show you once finished.

2010/3/29 Dmitry Andrejev <dand...@gmail.com>

[Alexander Obuhovich]

Front-end jquery isn't related to admin's jquery. Only place when they overlap is when content mode is used, where front-end jquery is not used and only admin's version is used.

I came across theme, where admin's version of jQuery were not working on front-end, because front-end js expected 1.4 version of jquery and used something specific from it.

[Phil -- wbtc.fr --]

sorry, I was out of the subject :$

2010/3/30 Alexander Obuhovich <aik....@gmail.com>

[Dmitry A.]

Since we have Themes released independently from Core we can actually
test and include JQ 1.4.x as we feel like - I see no problem with
that. As long as it tested and works of course.

I guess time for Admin JQ update to 1.4.x?

DA.

On Mar 30, 8:57 am, "Phil -- wbtc.fr --" <p...@wbtc.fr> wrote:
> sorry, I was out of the subject :$
>

> 2010/3/30 Alexander Obuhovich <aik.b...@gmail.com>

>
>
>
> > Front-end jquery isn't related to admin's jquery. Only place when they
> > overlap is when content mode is used, where front-end jquery is not used and
> > only admin's version is used.
>
> > I came across theme, where admin's version of jQuery were not working on
> > front-end, because front-end js expected 1.4 version of jquery and used
> > something specific from it.
>

> > On Mon, Mar 29, 2010 at 11:22 PM, Phil -- wbtc.fr -- <p...@wbtc.fr> wrote:
>
> >> Alex, I totally agree with your point, but I think front end could benefit
> >> of an updated jQuery.
>
> >> I'm doing some cool little things with this, I'll show you once finished.
>

> >> 2010/3/29 Dmitry Andrejev <dandre...@gmail.com>

>
> >> Alex, what was the main reason you wanted to upgrade Admin to JQ 1.4.x?
>
> >>> Front end, well - yes we kind of can do that too, but only once tested
> >>> well. I say we create a task and add to 5.1.0?
>
> >>> DA.
>

> >>> On Mon, Mar 29, 2010 at 2:29 PM, Alexander Obuhovich <aik.b...@gmail.com

> >>> > wrote:
>
> >>>> We usually don't upgrade 3rd party libraries, just because there are new
> >>>> versions available. That's because nothing isn't upgraded until it's not
> >>>> compatible with current browser versions. Why bother if it already works.
>
> >>>> On Mon, Mar 29, 2010 at 6:54 PM, Phil ..:: domicilis.biz ::.. <
> >>>> p...@domicilis.biz> wrote:
>
> >>>>> On front, 503-B1 is still using jQ 132 (released 1y. ago), while 142 is
> >>>>> available now.
>

> >>>>> 2010/3/29 Alexander Obuhovich <aik.b...@gmail.com>

[Alexander Obuhovich]

Ok.

[Dmitry A.]

Tasked filed:

686: Upgrade to JQuery 1.4.x for Admin Interfaces

http://tracker.in-portal.org/view.php?id=686

DA.