A question about the impact may be caused by table's clientWidth/Height behavior change of Chromium

A question about the impact may be caused by table's clientWidth/Height behavior change of Chromium

Hi, I'm a contributor of Chromium Project.

which make table's clientWidth/Height match to its offsetWidth/Height.

The corresponding issue page for that change is https://bugs.chromium.org/p/chromium/issues/detail?id=978019.

In case of Firefox, its already has that behavior, and that is what we intend to introduce by the change above
(In perspective of interoperability, it would be good I think).

I got a positive feedback from David Grogan in Chromium Community to apply that change to Chromium repo,
and also heard from him that
" the client* properties are used in something like $("blah").outsideWidth or insideWidth or something."

So I wonder jQuery community could share with us about how much breakage the change might cause, whether jQuery would be ok if Chromium adopt the behavior above,
and if it's ok, how jQuery going to adapt to the change.

I'm not sure here is the right place to ask this question,
so if it's not, please let me know to correct the place of this question.


Thank you for your help:)
Joonghun Park