Re: [qooxdoo-devel] Upgrade for offsetWidth?

Hi all, I've created a github issue: https://github.com/qooxdoo/qooxdoo/issues/195 Please add your comments and suggestions there if appropriate. Regards Dietrich Am 20.03.2016 um 13:54 schrieb Matt Davis - NOAA Federal: Hi Qooxdoo dev team, I've been getting this warning in Chrome: 'SVGE

Re: [qooxdoo-devel] Upgrade for offsetWidth?

I have not. Since this warning is being emitted in the qx core, it may be possible that Chrome is greedily grepping for offsetWidth and simply emitting it. I'll pull beta Chrome tomorrow and test our GUI. Thanks, Matt On Mon, Mar 21, 2016 at 1:02 PM, Tobias Oetiker wrote: > Hi Matt, > > Today M

Re: [qooxdoo-devel] Upgrade for offsetWidth?

Hi Matt, Today Matt Davis - NOAA Federal wrote: > We are not using any svg in our application. I assumed because of the > warning it meant the qx framework was using it, as it comes back to the > keyboard event handler and appears to be getting the offsetWidth of a > widget... qooxdoo is not usi

Re: [qooxdoo-devel] Upgrade for offsetWidth?

We are not using any svg in our application. I assumed because of the warning it meant the qx framework was using it, as it comes back to the keyboard event handler and appears to be getting the offsetWidth of a widget... Thanks, Matt On Mon, Mar 21, 2016 at 11:14 AM, Dietrich Streifert < dietric

Re: [qooxdoo-devel] Upgrade for offsetWidth?

Hi Matt, could you give us an insight on how you are using svg in your application, if possible with some code snippets or playground examples. This may help finding workarounds or fixes. Thank you! Regards Dietrich Am 20.03.2016 um 13:54 schrieb Matt Davis - NOAA Federal: Hi Qooxdoo dev t

Re: [qooxdoo-devel] Upgrade for offsetWidth?

As I understood the deprecation of SVGElement.offset* will break existing applications out there, because they currently use SVGElements in their apps. There are a lot more locations where we would need to wrap offsetWidth and offsetHeight, e.g. target element calculations in the event handler

Re: [qooxdoo-devel] Upgrade for offsetWidth?

here is just a quick fix proposal for qx.bom.eloement.Location https://github.com/level420/qooxdoo/commit/7bdea45f23389804ddd663a7e032158f248b8466 This fixes the NaN value problem for right and bottom of Alexanders playground example in my local playground: http://tinyurl.com/h89s2pk @Alexan

Re: [qooxdoo-devel] Upgrade for offsetWidth?

You can have these errors in various places. And if you think you got them all, you'll find one in the dnd manager ;-) qx isn't makde for inline SVGs in the moment, but I'd really vote for making the code more robust for that. Focus handling with inline SVGs is another problem with SVG and IE. Am M

Re: [qooxdoo-devel] Upgrade for offsetWidth?

In https://www.chromestatus.com/features/5724912467574784 chromium is recommending to use getBoundingClientRect() as a replacement. But as Cajus said: I'll hesitate to run through qx.bom.element. and insert everywhere switches like ( elem instanceof SVGElement ) ? elem.getBoundingClientR

Re: [qooxdoo-devel] Upgrade for offsetWidth?

Chrome was throwing this notice in event/handler/Keyboard.js in the __getEventTarget method (qx Desktop): /** * Get the target element for key events * * @return {Element} the event target element */ __getEventTarget : function() { var focusHandler = this.__ma

Re: [qooxdoo-devel] Upgrade for offsetWidth?

It would be better to use the qooxdoo SVG contribution instead of injecting SVGs manually. We've an application that makes heavy use of SVG and even if you modify this one (i.e. use the proposed bounding box object), you will run into various other locations in the code where you've to distinguish

Re: [qooxdoo-devel] Upgrade for offsetWidth?

I found the issue in the qx.bom.element.Location. The issue happens in the method get, the qooxdoo gets the elem.offsetWidth and elem.offsetHeight, but elem could be an instance of the SVGElement. So, I suppose that the qx should check is it svgelement or not and using the element.getBBox().wid

Re: [qooxdoo-devel] Upgrade for offsetWidth?

And here is the corresponding issue for jQuery: https://github.com/jquery/jquery/issues/2895 Am 21.03.2016 um 11:41 schrieb Dietrich Streifert: Hi All, I've run Alexanders playground example and can confirm the issue with Chrome 50.0.2661.37 beta-m (64-bit), which is the newest beta release

Re: [qooxdoo-devel] Upgrade for offsetWidth?

Hi All, I've run Alexanders playground example and can confirm the issue with Chrome 50.0.2661.37 beta-m (64-bit), which is the newest beta release. I'm currently not using any svg images. Maybe someone wo is using svg could please identify where the deprecated call el.offset is happening?

Re: [qooxdoo-devel] Upgrade for offsetWidth?

Hi Tobias. I created the issue about this behavior two weeks ago. You could use the example from this issue http://bugs.qooxdoo.org/show_bug.cgi?id=9255 > On Mar 21, 2016, at 10:43 AM, Tobias Oetiker wrote: > > Hi Matt > > Yesterday Matt Davis

Re: [qooxdoo-devel] Upgrade for offsetWidth?

Hi Matt Yesterday Matt Davis - NOAA Federal wrote: > Hi Qooxdoo dev team, > > I've been getting this warning in Chrome: > > 'SVGElement.offsetWidth' is deprecated and will be removed in M50, around > April 2016. See https://www.chromestatus.com/features/5724912467574784 for > more details. > > ​W

[qooxdoo-devel] Upgrade for offsetWidth?

Hi Qooxdoo dev team, I've been getting this warning in Chrome: 'SVGElement.offsetWidth' is deprecated and will be removed in M50, around April 2016. See https://www.chromestatus.com/features/5724912467574784 for more details. ​Will there be an update available to handle this? It seems to be in a

Re: [qooxdoo-devel] upgrade to 3.5

On 18.02.2014 13:19, Tobias Oberrauch wrote: > Hi Micha, > > Furthermore you can check the release notes[1] and the migration guide > especially for the major update 3.0[2]. > And yes the command is then right one to upgrade your project. > thanks, I will lokk at that. Michael ---

Re: [qooxdoo-devel] upgrade to 3.5

Hi Micha, Furthermore you can check the release notes[1] and the migration guide especially for the major update 3.0[2]. And yes the command is then right one to upgrade your project. [1] http://qooxdoo.org/project/release_notes [2] http://manual.qooxdoo.org/3.0/pages/tool/migration/migration_gu

Re: [qooxdoo-devel] upgrade to 3.5

Hey Micha, yeah it's a little bit buried: http://manual.qooxdoo.org/3.5/pages/getting_started.html Just check all the requirements pages there, they list the browser and versions we support for each component (Desktop, Mobile ...) Regards Richard ---

[qooxdoo-devel] upgrade to 3.5

I want to upgrade my code from version 2.1.1 to the current version 3.5 I somehow find it difficult to find the minimum supported browsers for this version, espacially the required ie version. On this side: http://qooxdoo.org/project/features#browser_support I can read: "qooxdoo runs in any mo

Re: [qooxdoo-devel] upgrade

It isn't possible, as there are some API changes. For example from 0.6.x to 0.7.x, the way of defining classes has changed a lot. In 0.8.x expect to have differences in layout. If you have a lot of code, the migration scripts and API changes can introduce a few errors. That's the cost of progress

[qooxdoo-devel] upgrade

Hello all. Is there a way we could migrate to the latest stable release only qx.js and not update our application scripts? It is not possible for us to even think about changing all our code with migration scripts. Thanks for your advices. Ales -- View this message in context: http://www.