westor schrieb: > Yesterday I fixed all my qooxdoo applications to run with crome - I > thought!!! (See 2 of my threads below.) > > Today I see at another PC again that my applications wouldn't come up. I'm > not sure, if google has updated something in the background or if there are > several chrome versions since last week or if this is also dependent of > operating system. > > I'm using 0.7.4. of qooxdoo. > > - I see the following uncought error: > Unsupported client: ... > I fixed this in qx.bom.client.Engine in line 90, which goes from > else if (navigator.vendor && navigator.vendor === "Apple Computer, > Inc.") > to > else if (navigator.vendor && navigator.vendor === "Apple Computer, > Inc." || navigator.vendor === "Google Inc.")
It seems that they have changed the vendor authentification in one of the latest builds (it has some type of auto-update mechanism). Fixed in trunk & legacy_0_7 Sebastian > > - In the log window appears: > "Refused to set unsafe header Referer" > This seems to have no effect for the application, but I don't know, what > that message means. > > - Integration of FCK Editor does not work. > > I'm a little bit tired of fixing all this now. Don't know, how qooxdoo will > run, if chrome goes from beta to release. And I'm not sure if some of these > issues will be fixed only for 0.8 or for 0.7.x too. > I have several apps already in qooxdoo and it would take a lot of additional > work If I have to decide to upgrade all of them :-( > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
