Issue metadata
Sign in to add a comment
|
GXT Form with Tree component doesn't working in Chrome 53 on Windows
Reported by
anton.fo...@gmail.com,
Sep 18 2016
|
||||||||||||||||||||||
Issue descriptionChrome Version : 53.0.2785.116 (Официальная сборка) m (64 бит) URLs (if applicable) : https://demo.dentplan.ru/?login=ddf1bba6302d01188073§ion=expenditures Other browsers tested: Add OK or FAIL, along with the version, after other browsers where you have tested this issue: Safari: OK Firefox: OK IE: OK What steps will reproduce the problem? The demo version (wich not requires any registration) of our GXT-based application contains the form which causes the problem. (1) Visit our website www.dentplan.ru. (2) Click the orange button to start demo application (as shown in attached file). Every orange button opens one corresponding form after demo loaded, the 4-th button (located in "Контроль расходов" section) opens the form what causes a problem. (3) You can open any form in demo application, but only "Расходы" form, which contains Tree component, causes a problem (as shown in attached file). What is the expected result? The form should open. What happens instead? Web application immediately and totally stops to responding. Additional information: The bug appeared when Chrome was updated to version 53.0.2785.101. The problem occurs only on Windows (all versions, I tried in 10, 7, Server 2008). In MacOS and iOS all works correctly. Our web application uses Sencha GXT 2.3.1a and GWT 2.7.0. Bug appears in every form with Tree component. All other forms are working properly. When you tried to open a form with tree, page immediately stops to responding. After a little time a Chrome's standard dialog "Page not responding" is appearing. If a developer tools panel was open before, no activity displayed in it. After the effect happened, it become not easy to close tab in the top bar of Chrome.
,
Sep 19 2016
My change was for internal performance utilities that are not part of the chrome build. +szager@, it looks like your change in the referenced log is in the only thing that might be plausible, could you take a look?
,
Sep 20 2016
,
Sep 20 2016
,
Sep 27 2016
Fixing the spelling error in label.
,
Sep 29 2016
,
Oct 3 2016
The original content is not accessible any more, it seems to give an error about not being logged in. Can you please provide a new URL for reproducing the problem?
,
Oct 3 2016
,
Oct 3 2016
Hello! Today I updated my Chrome browser to version 53.0.2785.143 m (64-bit), and problem is gone! I tried to reproduce error on Windows and MacOS, and all working fine. It's very good, but it's also strange, because there are no comments here about fix for this error. To reproduce error in older version mentioned earlier, please perform steps described in section "What steps will reproduce the problem?" (and see attached screenshots). Error may not be reproduced by direct link.
,
Jan 27 2017
Thanks for the confirmation. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Sep 19 2016Labels: -Type-Bug -Pri-3 hasbisect-per-revison M-53 OS-Linux OS-Windows Pri-1 Type-Bug-Regression
Owner: mattcary@chromium.org
Status: Assigned (was: Unconfirmed)