On Tue, May 29, 2007 at 05:55:22PM +0000, Javier Kohen <[EMAIL PROTECTED]> 
wrote:
> El mar, 29-05-2007 a las 19:52 +0200, Mike Hommey escribió:
> > On Tue, May 29, 2007 at 06:58:24PM +0200, Javier Kohen <[EMAIL PROTECTED]> 
> > wrote:
> > > Package: libxul0d
> > > Version: 1.8.1.4-1
> > > Severity: important
> > > 
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > > 
> > > I just upgraded from version 1.8.0.11 and I'm seeing interesting 
> > > regressions in Epiphany. For instance, entering some text in the address 
> > > bar reports that the URL is wrong and cannot be loaded, and if "keyword:" 
> > > is prepended, it gives an error message saying that that is not a 
> > > registered protocol, whereas it's been always the case that it opens a 
> > > user-setup URL passing the entered text as an argument.
> > 
> > There is a bug opened on epiphany for this.
> 
> Given that the upgrade happened only on the library side, I didn't think
> to blame Epiphany for the regressions, that's why I opened the report
> here without checking over there, sorry.
> 
> > 
> > > Another less obvious regression happened with www.koolim.com. The client 
> > > at http://web05.koolim.com/client6/html/gui/embed/main.html can't be 
> > > loaded with this version of the library, but it was working with the 
> > > previous version and I can still access it from my parallel Iceweasel 
> > > 2.0.0.3-2 installation.
> > 
> > It works fine, here. What does the error console tell you ?
> 
> Does it pass the "wait while loading and connecting" screen?

Yes it does.

> Here it
> doesn't and I get the following message on the JS console:
> 
> Error de JavaScript en , en la línea 0:
> uncaught exception: [Exception... "Failure"  nsresult: "0x80004005
> (NS_ERROR_FAILURE)"  location: "JS frame ::
> http://web05.koolim.com/client6/html/js/BSComm.js ::
> CreateXmlHttpObject :: line 133"  data: no]
> 
> The relevant line reads:
>          if (!xmlhttp && window.XMLHttpRequest) { try { xmlhttp = new
> XMLHttpRequest(); } catch (e) { xmlhttp=false; } }

It's strange you get an uncaught exception with such code...

Mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to