The GWT team has just released GWT 1.4.62. It includes fixes for the two issues known to specifically break the Firefox 3 beta, as well as a fix for a Windows hosted-mode crash bug. The specific patches are detailed below.
You will want to update to GWT 1.4.62 in order to ensure that your applications work properly on Firefox 3 when it is formally released. To update from GWT 1.4.61 to 1.4.62, follow the steps below for each GWT application you want to update:
1) Download GWT 1.4.62 for your platform at the link below and unpack it to the directory of your choice (only needs to be performed once per platform):
2) Update your GWT project build path to use the latest GWT JARs. This includes gwt-user.jar, gwt-dev-<platform>.jar and gwt-servlet.jar if your application uses GWT-RPC.
3) Update any run configurations or application compile and shell scripts to include the latest JARs in the classpath (same JARs as mentioned in step 2).
4) Run a GWT compilation over your project to generate the latest GWT application files for your project.
5) Deploy the latest GWT application files to your web server.
For those of you who have experienced the bugs that GWT 1.4.62 aims to fix, give the latest build a spin and let us know if you're still experiencing any problems. Also, please reply back to this thread if you experience any other difficulty updating to GWT 1.4.62 or deploying your GWT application with the latest release.
The following patches are included in this release:
r1533: Fixes issue 1702 insertListItem current created an option element with the wrong owner document. This causes errors in FF3 preview builds.
r1871: Fixes issue 1942 FF3 Beta 1 throws WRONG_DOCUMENT_ERROR in getBoxObjectFor if the element is not attached to the DOM. This affects our implementation of Tree when an element is selected programmatically on a tree that is unattached. This change wraps the call to getBoxObjectFor in a try/catch and returns 0 if a WRONG_DOCUMENT_ERROR occurs, which emulates what getBoxObjectFor is supposed to do. This bug is set to P1 in bugzilla, https://bugzilla.mozilla.org/show_bug.cgi?id=409111, so this change can be saftely removed in the future.
r1991, r1995: Fixes a latent bug in SwtOleGlue.extractStringFromOleCharPtr(). We were treating the incoming value as a BSTR, but it's really just a naked OLECHAR*.
> The GWT team has just released GWT 1.4.62. It includes fixes for the two
> issues
> known to specifically break the Firefox 3 beta, as well as a fix for a
> Windows
> hosted-mode crash bug. The specific patches are detailed below.
> You will want to update to GWT 1.4.62 in order to ensure that your
> applications
> work properly on Firefox 3 when it is formally released. To update from GWT
> 1.4.61 to 1.4.62, follow the steps below for each GWT application you want
> to
> update:
> 1) Download GWT 1.4.62 for your platform at the link below and unpack
> it to the directory of your choice (only needs to be performed once
> per platform):
> 2) Update your GWT project build path to use the latest GWT JARs. This
> includes gwt-user.jar, gwt-dev-<platform>.jar and gwt-servlet.jar if
> your application uses GWT-RPC.
> 3) Update any run configurations or application compile and shell
> scripts to include the latest JARs in the classpath (same JARs as
> mentioned in step 2).
> 4) Run a GWT compilation over your project to generate the latest GWT
> application files for your project.
> 5) Deploy the latest GWT application files to your web server.
> For those of you who have experienced the bugs that GWT 1.4.62 aims to
> fix, give the latest build a spin and let us know if you're still
> experiencing any problems. Also, please reply back to this thread if
> you experience any other difficulty updating to GWT 1.4.62 or
> deploying your GWT application with the latest release.
> The following patches are included in this release:
> r1533:
> Fixes issue 1702
> insertListItem current created an option element with the wrong
> owner document. This causes errors in FF3 preview builds.
> r1871:
> Fixes issue 1942
> FF3 Beta 1 throws WRONG_DOCUMENT_ERROR in getBoxObjectFor if the
> element is not attached to the DOM. This affects our implementation
> of Tree when an element is selected programmatically on a tree that
> is unattached. This change wraps the call to getBoxObjectFor in a
> try/catch and returns 0 if a WRONG_DOCUMENT_ERROR occurs, which
> emulates what getBoxObjectFor is supposed to do. This bug is set
> to P1 in bugzilla, https://bugzilla.mozilla.org/show_bug.cgi?id=409111,
> so this change can be saftely removed in the future.
> r1991, r1995:
> Fixes a latent bug in SwtOleGlue.extractStringFromOleCharPtr(). We were
> treating the incoming value as a BSTR, but it's really just a naked
> OLECHAR*.
> The GWT team has just released GWT 1.4.62. It includes fixes for the two
> issues
> known to specifically break the Firefox 3 beta, as well as a fix for a
> Windows
> hosted-mode crash bug. The specific patches are detailed below.
> You will want to update to GWT 1.4.62 in order to ensure that your
> applications
> work properly on Firefox 3 when it is formally released. To update from GWT
> 1.4.61 to 1.4.62, follow the steps below for each GWT application you want
> to
> update:
> 1) Download GWT 1.4.62 for your platform at the link below and unpack
> it to the directory of your choice (only needs to be performed once
> per platform):
> 2) Update your GWT project build path to use the latest GWT JARs. This
> includes gwt-user.jar, gwt-dev-<platform>.jar and gwt-servlet.jar if
> your application uses GWT-RPC.
> 3) Update any run configurations or application compile and shell
> scripts to include the latest JARs in the classpath (same JARs as
> mentioned in step 2).
> 4) Run a GWT compilation over your project to generate the latest GWT
> application files for your project.
> 5) Deploy the latest GWT application files to your web server.
> For those of you who have experienced the bugs that GWT 1.4.62 aims to
> fix, give the latest build a spin and let us know if you're still
> experiencing any problems. Also, please reply back to this thread if
> you experience any other difficulty updating to GWT 1.4.62 or
> deploying your GWT application with the latest release.
> The following patches are included in this release:
> r1533:
> Fixes issue 1702
> insertListItem current created an option element with the wrong
> owner document. This causes errors in FF3 preview builds.
> r1871:
> Fixes issue 1942
> FF3 Beta 1 throws WRONG_DOCUMENT_ERROR in getBoxObjectFor if the
> element is not attached to the DOM. This affects our implementation
> of Tree when an element is selected programmatically on a tree that
> is unattached. This change wraps the call to getBoxObjectFor in a
> try/catch and returns 0 if a WRONG_DOCUMENT_ERROR occurs, which
> emulates what getBoxObjectFor is supposed to do. This bug is set
> to P1 in bugzilla,https://bugzilla.mozilla.org/show_bug.cgi?id=409111,
> so this change can be saftely removed in the future.
> r1991, r1995:
> Fixes a latent bug in SwtOleGlue.extractStringFromOleCharPtr(). We were
> treating the incoming value as a BSTR, but it's really just a naked
> OLECHAR*.
Thanks for noticing, and you're right. Our plan was to stage it so that people who are active on the groups would have the earliest access (and would be most likely to give us feedback on the new version). The next step is to change the primary download hyperlink as you suggest, which we'll probably do in the next week or so.
As a data point, have you found that all your code works on FF3 using 1.4.62 ?
On Tue, Mar 25, 2008 at 6:51 AM, ToonT...@googlemail.com <
> On Mar 17, 6:30 pm, "Joel Webber" <j...@google.com> wrote: > > All,
> > The GWT team has just released GWT 1.4.62. It includes fixes for the two > > issues > > known to specifically break the Firefox 3 beta, as well as a fix for a > > Windows > > hosted-mode crash bug. The specific patches are detailed below.
> > You will want to update to GWT 1.4.62 in order to ensure that your > > applications > > work properly on Firefox 3 when it is formally released. To update from > GWT > > 1.4.61 to 1.4.62, follow the steps below for each GWT application you > want > > to > > update:
> > 1) Download GWT 1.4.62 for your platform at the link below and unpack > > it to the directory of your choice (only needs to be performed once > > per platform):
> > 2) Update your GWT project build path to use the latest GWT JARs. This > > includes gwt-user.jar, gwt-dev-<platform>.jar and gwt-servlet.jar if > > your application uses GWT-RPC.
> > 3) Update any run configurations or application compile and shell > > scripts to include the latest JARs in the classpath (same JARs as > > mentioned in step 2).
> > 4) Run a GWT compilation over your project to generate the latest GWT > > application files for your project.
> > 5) Deploy the latest GWT application files to your web server.
> > For those of you who have experienced the bugs that GWT 1.4.62 aims to > > fix, give the latest build a spin and let us know if you're still > > experiencing any problems. Also, please reply back to this thread if > > you experience any other difficulty updating to GWT 1.4.62 or > > deploying your GWT application with the latest release.
> > The following patches are included in this release:
> > r1533: > > Fixes issue 1702 > > insertListItem current created an option element with the wrong > > owner document. This causes errors in FF3 preview builds.
> > r1871: > > Fixes issue 1942 > > FF3 Beta 1 throws WRONG_DOCUMENT_ERROR in getBoxObjectFor if the > > element is not attached to the DOM. This affects our implementation > > of Tree when an element is selected programmatically on a tree that > > is unattached. This change wraps the call to getBoxObjectFor in a > > try/catch and returns 0 if a WRONG_DOCUMENT_ERROR occurs, which > > emulates what getBoxObjectFor is supposed to do. This bug is set > > to P1 in bugzilla,https://bugzilla.mozilla.org/show_bug.cgi?id=409111, > > so this change can be saftely removed in the future.
> > r1991, r1995: > > Fixes a latent bug in SwtOleGlue.extractStringFromOleCharPtr(). We were > > treating the incoming value as a BSTR, but it's really just a naked > > OLECHAR*.
> Thanks for noticing, and you're right. Our plan was to stage it so that
> people who are active on the groups would have the earliest access (and
> would be most likely to give us feedback on the new version). The next step
> is to change the primary download hyperlink as you suggest, which we'll
> probably do in the next week or so.
> As a data point, have you found that all your code works on FF3 using 1.4.62
> ?
> On Tue, Mar 25, 2008 at 6:51 AM, ToonT...@googlemail.com <
> > On Mar 17, 6:30 pm, "Joel Webber" <j...@google.com> wrote:
> > > All,
> > > The GWT team has just released GWT 1.4.62. It includes fixes for the two
> > > issues
> > > known to specifically break the Firefox 3 beta, as well as a fix for a
> > > Windows
> > > hosted-mode crash bug. The specific patches are detailed below.
> > > You will want to update to GWT 1.4.62 in order to ensure that your
> > > applications
> > > work properly on Firefox 3 when it is formally released. To update from
> > GWT
> > > 1.4.61 to 1.4.62, follow the steps below for each GWT application you
> > want
> > > to
> > > update:
> > > 1) Download GWT 1.4.62 for your platform at the link below and unpack
> > > it to the directory of your choice (only needs to be performed once
> > > per platform):
> > > 2) Update your GWT project build path to use the latest GWT JARs. This
> > > includes gwt-user.jar, gwt-dev-<platform>.jar and gwt-servlet.jar if
> > > your application uses GWT-RPC.
> > > 3) Update any run configurations or application compile and shell
> > > scripts to include the latest JARs in the classpath (same JARs as
> > > mentioned in step 2).
> > > 4) Run a GWT compilation over your project to generate the latest GWT
> > > application files for your project.
> > > 5) Deploy the latest GWT application files to your web server.
> > > For those of you who have experienced the bugs that GWT 1.4.62 aims to
> > > fix, give the latest build a spin and let us know if you're still
> > > experiencing any problems. Also, please reply back to this thread if
> > > you experience any other difficulty updating to GWT 1.4.62 or
> > > deploying your GWT application with the latest release.
> > > The following patches are included in this release:
> > > r1533:
> > > Fixes issue 1702
> > > insertListItem current created an option element with the wrong
> > > owner document. This causes errors in FF3 preview builds.
> > > r1871:
> > > Fixes issue 1942
> > > FF3 Beta 1 throws WRONG_DOCUMENT_ERROR in getBoxObjectFor if the
> > > element is not attached to the DOM. This affects our implementation
> > > of Tree when an element is selected programmatically on a tree that
> > > is unattached. This change wraps the call to getBoxObjectFor in a
> > > try/catch and returns 0 if a WRONG_DOCUMENT_ERROR occurs, which
> > > emulates what getBoxObjectFor is supposed to do. This bug is set
> > > to P1 in bugzilla,https://bugzilla.mozilla.org/show_bug.cgi?id=409111,
> > > so this change can be saftely removed in the future.
> > > r1991, r1995:
> > > Fixes a latent bug in SwtOleGlue.extractStringFromOleCharPtr(). We were
> > > treating the incoming value as a BSTR, but it's really just a naked
> > > OLECHAR*.- Hide quoted text -
> On Mar 17, 6:30 pm, "Joel Webber" <j...@google.com> wrote:
> > All,
> > The GWT team has just released GWT 1.4.62. It includes fixes for the two
> > issues
> > known to specifically break the Firefox 3 beta, as well as a fix for a
> > Windows
> > hosted-mode crash bug. The specific patches are detailed below.
> > You will want to update to GWT 1.4.62 in order to ensure that your
> > applications
> > work properly on Firefox 3 when it is formally released. To update from GWT
> > 1.4.61 to 1.4.62, follow the steps below for each GWT application you want
> > to
> > update:
> > 1) Download GWT 1.4.62 for your platform at the link below and unpack
> > it to the directory of your choice (only needs to be performed once
> > per platform):
> > 2) Update your GWT project build path to use the latest GWT JARs. This
> > includes gwt-user.jar, gwt-dev-<platform>.jar and gwt-servlet.jar if
> > your application uses GWT-RPC.
> > 3) Update any run configurations or application compile and shell
> > scripts to include the latest JARs in the classpath (same JARs as
> > mentioned in step 2).
> > 4) Run a GWT compilation over your project to generate the latest GWT
> > application files for your project.
> > 5) Deploy the latest GWT application files to your web server.
> > For those of you who have experienced the bugs that GWT 1.4.62 aims to
> > fix, give the latest build a spin and let us know if you're still
> > experiencing any problems. Also, please reply back to this thread if
> > you experience any other difficulty updating to GWT 1.4.62 or
> > deploying your GWT application with the latest release.
> > The following patches are included in this release:
> > r1533:
> > Fixes issue 1702
> > insertListItem current created an option element with the wrong
> > owner document. This causes errors in FF3 preview builds.
> > r1871:
> > Fixes issue 1942
> > FF3 Beta 1 throws WRONG_DOCUMENT_ERROR in getBoxObjectFor if the
> > element is not attached to the DOM. This affects our implementation
> > of Tree when an element is selected programmatically on a tree that
> > is unattached. This change wraps the call to getBoxObjectFor in a
> > try/catch and returns 0 if a WRONG_DOCUMENT_ERROR occurs, which
> > emulates what getBoxObjectFor is supposed to do. This bug is set
> > to P1 in bugzilla,https://bugzilla.mozilla.org/show_bug.cgi?id=409111,
> > so this change can be saftely removed in the future.
> > r1991, r1995:
> > Fixes a latent bug in SwtOleGlue.extractStringFromOleCharPtr(). We were
> > treating the incoming value as a BSTR, but it's really just a naked
> > OLECHAR*.- Hide quoted text -
