Discussion:
Upgrade for offsetWidth?
(too old to reply)
Matt Davis - NOAA Federal
2016-03-20 12:54:44 UTC
Permalink
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 core
DOM function which determines if a target is visible.

Thanks,
Matt​
--
*IRIS/iNWS Technical Lead*
*Decision Support Branch*

*Meteorological Development LabOffice of Science and Technology Integration*
*National** Weather Service, La Crosse, WI*
(608) 406-0537
Tobias Oetiker
2016-03-21 07:43:35 UTC
Permalink
Hi Matt
Post by Matt Davis - NOAA Federal
Hi Qooxdoo dev team,
'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 core
DOM function which determines if a target is visible.
Thanks,
Matt​
I have not seen this warning yet im my code. Can you try producing
a minimal example on playground triggering this warning ...

cheers
tobi
--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
www.oetiker.ch ***@oetiker.ch +41 62 775 9902
Alexander Kirsanov
2016-03-21 08:58:30 UTC
Permalink
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 <http://bugs.qooxdoo.org/show_bug.cgi?id=9255>
Post by Tobias Oetiker
Hi Matt
Post by Matt Davis - NOAA Federal
Hi Qooxdoo dev team,
'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 core
DOM function which determines if a target is visible.
Thanks,
Matt​
I have not seen this warning yet im my code. Can you try producing
a minimal example on playground triggering this warning ...
cheers
tobi
--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140_______________________________________________
qooxdoo-devel mailing list
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Dietrich Streifert
2016-03-21 10:41:41 UTC
Permalink
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?

Regards
Dietrich
Post by Alexander Kirsanov
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
Dietrich Streifert
2016-03-21 11:28:11 UTC
Permalink
And here is the corresponding issue for jQuery:

https://github.com/jquery/jquery/issues/2895
Post by 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.
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?
Regards
Dietrich
Post by Alexander Kirsanov
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
Alexander Kirsanov
2016-03-21 11:38:27 UTC
Permalink
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().width instead of elem.offsetWidth in case of SVG. But I’m not sure that it is good solution.
https://github.com/jquery/jquery/issues/2895 <https://github.com/jquery/jquery/issues/2895>
Post by 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.
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?
Regards
Dietrich
Post by Alexander Kirsanov
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>http://bugs.qooxdoo.org/show_bug.cgi?id=9255 <http://bugs.qooxdoo.org/show_bug.cgi?id=9255>
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140_______________________________________________
qooxdoo-devel mailing list
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Cajus Pollmeier
2016-03-21 11:46:27 UTC
Permalink
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 between SVG and non SVG elements.
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().width instead of
elem.offsetWidth in case of SVG. But I’m not sure that it is good
solution. 
 
On Mar 21, 2016, at 2:28 PM, Dietrich Streifert <dietrich.streifert
https://github.com/jquery/jquery/issues/2895
Post by 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.
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?
Regards
Dietrich
Hi Tobias. 
I created the issue about this behavior two weeks ago. 
You could use the example from this issue http://bugs.qooxdoo.o
rg/show_bug.cgi?id=9255
 
 
-----------------------------------------------------------------
-------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140___
____________________________________________
qooxdoo-devel mailing list
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
-------------------------------------------------------------------
-----------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
qooxdoo-devel mailing list
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Matt Davis - NOAA Federal
2016-03-21 11:56:05 UTC
Permalink
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.__manager.getHandler(qx.event.handler.Focus);
var target = focusHandler.getActive();

// Fallback to focused element when active is null or invisible
if (!target || target.offsetWidth == 0) {
target = focusHandler.getFocus();
}

// Fallback to body when focused is null or invisible
if (!target || target.offsetWidth == 0) {
target = this.__manager.getWindow().document.body;
}

return target;
},
Post by Cajus Pollmeier
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 between SVG and non SVG elements.
Post by Alexander Kirsanov
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().width instead of
elem.offsetWidth in case of SVG. But I’m not sure that it is good
solution.
On Mar 21, 2016, at 2:28 PM, Dietrich Streifert <dietrich.streifert
https://github.com/jquery/jquery/issues/2895
Post by 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.
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?
Regards
Dietrich
Post by Alexander Kirsanov
Hi Tobias.
I created the issue about this behavior two weeks ago.
You could use the example from this issue http://bugs.qooxdoo.o
rg/show_bug.cgi?id=9255
-----------------------------------------------------------------
-------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140___
____________________________________________
qooxdoo-devel mailing list
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
-------------------------------------------------------------------
-----------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
qooxdoo-devel mailing list
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
qooxdoo-devel mailing list
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
--
*IRIS/iNWS Technical Lead*
*Decision Support Branch*

*Meteorological Development LabOffice of Science and Technology Integration*
*National** Weather Service, La Crosse, WI*
(608) 406-0537
Cajus Pollmeier
2016-03-21 12:24:19 UTC
Permalink
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 Montag, den 21.03.2016, 06:56 -0500 schrieb Matt Davis - NOAA
Post by Matt Davis - NOAA Federal
Chrome was throwing this notice in event/handler/Keyboard.js in the
    /**
     * Get the target element for key events
     *
     */
    __getEventTarget : function()
    {
      var focusHandler =
this.__manager.getHandler(qx.event.handler.Focus);
      var target = focusHandler.getActive();
      // Fallback to focused element when active is null or invisible
      if (!target || target.offsetWidth == 0) {
        target = focusHandler.getFocus();
      }
      // Fallback to body when focused is null or invisible
      if (!target || target.offsetWidth == 0) {
        target = this.__manager.getWindow().document.body;
      }
      return target;
    },
On Mon, Mar 21, 2016 at 6:46 AM, Cajus Pollmeier
Post by Cajus Pollmeier
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 between SVG and non SVG elements.
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().width instead
of
elem.offsetWidth in case of SVG. But I’m not sure that it is good
solution. 
 
On Mar 21, 2016, at 2:28 PM, Dietrich Streifert
https://github.com/jquery/jquery/issues/2895
Post by Dietrich Streifert
Hi All,
I've run Alexanders playground example and can confirm the
issue
Post by Dietrich Streifert
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
Post by Dietrich Streifert
svg could please identify where the deprecated call el.offset
is
Post by Dietrich Streifert
happening?
Regards
Dietrich
Hi Tobias. 
I created the issue about this behavior two weeks ago. 
You could use the example from this issue http://bugs.qooxd
oo.o
Post by Dietrich Streifert
rg/show_bug.cgi?id=9255
 
 
-------------------------------------------------------------
----
-------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/414
0___
____________________________________________
qooxdoo-devel mailing list
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
---------------------------------------------------------------
----
-----------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
qooxdoo-devel mailing list
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
-----------------------------------------------------------------
-------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
qooxdoo-devel mailing list
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
-- 
IRIS/iNWS Technical Lead
Decision Support Branch
Meteorological Development Lab
Office of Science and Technology Integration
National Weather Service, La Crosse, WI
(608) 406-0537
-------------------------------------------------------------------
-----------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
qooxdoo-devel mailing list
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Dietrich Streifert
2016-03-21 11:58:18 UTC
Permalink
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.<Dimension|Location|Scroll> and insert everywhere
switches like

( elem instanceof SVGElement ) ? elem.getBoundingClientRect().width
: elem.offsetWidth;
or
( elem instanceof SVGElement ) ?
elem.getBoundingClientRect().height: elem.offsetHeight;

or similar.
Post by Alexander Kirsanov
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().width instead of
elem.offsetWidth in case of SVG. But I’m not sure that it is good
solution.
Dietrich Streifert
2016-03-21 13:17:30 UTC
Permalink
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

@Alexander, @Matt: give it a try by replacing qx.bom.element.Location
from my fork.

@all others: please have a look at that fix

Successful tested on Firefox 45, IE 11, Chrome 50, Chrome 49
Post by Alexander Kirsanov
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().width instead of
elem.offsetWidth in case of SVG. But I’m not sure that it is good
solution.
Dietrich Streifert
2016-03-21 13:57:56 UTC
Permalink
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 handlers
and element placement calculations and some basic things like the
isSeeable method in qx.ui.core.Widget.

That means we would have to wrap all those .offsetWidth and
.offsetHeight calls via something like qx.bom.Element.getOffsetWidth,
qx.bom.Element.getOffsetHeight calls.
Post by Dietrich Streifert
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
http://tinyurl.com/h89s2pk
@Alexander, @Matt: give it a try by replacing qx.bom.element.Location
from my fork.
@all others: please have a look at that fix
Successful tested on Firefox 45, IE 11, Chrome 50, Chrome 49
Post by Alexander Kirsanov
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().width instead of
elem.offsetWidth in case of SVG. But I’m not sure that it is good
solution.
Dietrich Streifert
2016-03-21 16:14:49 UTC
Permalink
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
Post by Matt Davis - NOAA Federal
Hi Qooxdoo dev team,
'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 core DOM function which determines if a target is visible.
Thanks,
Matt ​
Matt Davis - NOAA Federal
2016-03-21 16:27:04 UTC
Permalink
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 <
Post by Dietrich Streifert
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
Hi Qooxdoo dev team,
'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
core DOM function which determines if a target is visible.
Thanks,
Matt ​
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
qooxdoo-devel mailing list
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
--
*IRIS/iNWS Technical Lead*
*Decision Support Branch*

*Meteorological Development LabOffice of Science and Technology Integration*
*National** Weather Service, La Crosse, WI*
(608) 406-0537
Tobias Oetiker
2016-03-21 18:02:07 UTC
Permalink
Hi Matt,
Post by Matt Davis - NOAA Federal
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 using svg internally afaik. have you tried creating
a playgrouynd example for your case ?

cheers
tobi
Post by Matt Davis - NOAA Federal
Thanks,
Matt
On Mon, Mar 21, 2016 at 11:14 AM, Dietrich Streifert <
Post by Dietrich Streifert
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
Hi Qooxdoo dev team,
'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
core DOM function which determines if a target is visible.
Thanks,
Matt ​
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
qooxdoo-devel mailing list
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
www.oetiker.ch ***@oetiker.ch +41 62 775 9902
Matt Davis - NOAA Federal
2016-03-21 21:24:12 UTC
Permalink
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
Post by Dietrich Streifert
Hi Matt,
Post by Matt Davis - NOAA Federal
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 using svg internally afaik. have you tried creating
a playgrouynd example for your case ?
cheers
tobi
Post by Matt Davis - NOAA Federal
Thanks,
Matt
On Mon, Mar 21, 2016 at 11:14 AM, Dietrich Streifert <
Post by Dietrich Streifert
Hi Matt,
could you give us an insight on how you are using svg in your
application,
Post by Matt Davis - NOAA Federal
Post by Dietrich Streifert
if possible with some code snippets or playground examples.
This may help finding workarounds or fixes.
Thank you!
Regards
Dietrich
Hi Qooxdoo dev team,
'SVGElement.offsetWidth' is deprecated and will be removed in M50,
around
Post by Matt Davis - NOAA Federal
Post by Dietrich Streifert
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
core DOM function which determines if a target is visible.
Thanks,
Matt ​
------------------------------------------------------------------------------
Post by Matt Davis - NOAA Federal
Post by Dietrich Streifert
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
qooxdoo-devel mailing list
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
qooxdoo-devel mailing list
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
--
*IRIS/iNWS Technical Lead*
*Decision Support Branch*

*Meteorological Development LabOffice of Science and Technology Integration*
*National** Weather Service, La Crosse, WI*
(608) 406-0537
Dietrich Streifert
2016-03-22 11:18:42 UTC
Permalink
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
Post by Matt Davis - NOAA Federal
Hi Qooxdoo dev team,
'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 core DOM function which determines if a target is visible.
Thanks,
Matt ​
--
/*IRIS/iNWS Technical Lead*/
/Decision Support Branch/
/Meteorological Development Lab
Office of Science and Technology Integration/
/National// Weather Service, La Crosse, WI/
(608) 406-0537
Loading...