Hello, Sorry for that. I did the test for Firefox, and it worked well. Before the upgrade, all the pages with a dojo component looked blank :
I use linux and have no IE, but I asked Cagatay to test it under windows, and he didn't report me any problem. Can you give me the link to the bug crashing IE6 ? Maybe we can put the bugfix in MyFaces before dojo 0.4.1 is released. Regards, Sylvain On Sun, 2006-11-19 at 16:25 +0100, Martin Marinschek wrote: > It's been Sylvain who's been doing the upgrade. > > Please, Sylvain, get yourself an IE6 to test with before you do an > important upgrade like this - and go through the sandbox components... > > regards, > > Martin > > On 11/17/06, Werner Punz <[EMAIL PROTECTED]> wrote: > > Werner Punz schrieb: > > > Gerald Müllan schrieb: > > >> Hi, > > >> > > >> well, the dojo guys changed from version 0.3.1 to 0.4 not that long > > >> time ago but we are still using 0.3.1. We agreed to only migrate to a > > >> more recent version until some time has come > > >> (For about 1-2 months). > > >> > > > The 0.4.0 upgrade wont happen, there are some issues which were > > > triggered on one of my testsite, which I had migrated to dojo 0.4 which > > > caused > > > the ie to crash it is more likely that i will target 0.4.1 directly. > > > (The bug has been reported) > > > > > > > Ok Gerald just notified me, that the upgrade was done about a week ago > > by someone else, so it seems we are on 0.4, that explains a few issues i > > had with custom components, which i was aware of of having to change > > them before the upgrade (in one case I did the work upfront and > > committed it to the dojo people). > > > > Anyway, it is done now, I am not going to revert it unless there > > are serious issues (mainly the ie problem I had in my case). > > > > But please next time before doing something major like this, > > open a discussion, I am doing some work behind the scenes, mainly > > testing, before getting ready to upgrade. This 0.4 upgrade could cause > > some troubles for some users having to rely on IE6. > > > > > > > >
