Results 1 to 7 of 7

Thread: Insane problem in Chrome 30 (only)

  1. #1
    Sencha User
    Join Date
    Sep 2009
    Location
    London
    Posts
    54

    Default Insane problem in Chrome 30 (only)

    We are seeing a pretty crazy behaviour of ExtJS 3.4.1.1 (yes, old, I know) in Chrome 30. This only affects this version of Chrome.


    The problem is that for CheckboxGroup and RadioGroup elements, with a listener of 'change' events, the event fires twice when the change occurs (i.e., when blurring out of the field).
    The first is the group's change event. That is fine. But then it fires a change event from the checkbox/radio itself which is then trying to handle via the group's change handler, causing all sort of unexpected behaviour.
    The problem does not exist in versions of Chrome prior to 30.
    As well when we try to recreate the problem via jsfiddle, it all works fine.
    This example: http://jsfiddle.net/sj8cn/3/ works fine, but similar code in our rather large application causes the above problem in Chrome 30. This is why its also difficult for me to provide a working code example to replicate this.
    It's as if the group is allowing events from the checkboxes themselves to then be captured by its own change handler
    Please note that we are not overriding anything to do with forms.


    Has anyone ran into this?

  2. #2
    Sencha User
    Join Date
    Jan 2011
    Posts
    549

    Default

    Why are you using listeners on the group AND individual radio/checkbox?

    If you have a listener on the group, surely you don't need one on the individual component? I'd imagine this would always fire the event twice regardless of what browser is being used.

  3. #3
    Sencha User
    Join Date
    Apr 2013
    Posts
    2

    Default

    The individual listeners are there for testing, we don't have those on our application.

    The way we replicate the issue in our app is as follows: click on a radio, radiogroup's change event fires correctly passing the checked radio as second argument. Then click out, or even again on the same radio (already checked so radiogroup's change event should not fire), radiogroup's change event fires passing true as second parameter.

    So the thing is, as soon as the field loses focus the change event fires again and breaks whatever we're trying to achieve with the listener.

  4. #4
    Sencha User slemmon's Avatar
    Join Date
    Mar 2009
    Location
    Boise, ID
    Posts
    6,165

    Default

    Are you seeing the issue on Mac or PC? Other? Both?

  5. #5
    Sencha User
    Join Date
    Apr 2013
    Posts
    2

    Default

    Both, Linux too.

    As Harel mentioned, this seems to happen only on our app but we are not overriding anything. The app has been running for quite a long time and is the first time we've encountered this issue. Only with chrome 30.

  6. #6
    Sencha User
    Join Date
    Sep 2009
    Location
    London
    Posts
    54

    Default

    If you (Sencha) are interested we could demonstrate this for you.
    At the moment we have dealt with the symptom of the problem, i.e., we check each event from the radio/check group 'change' listener to confirm the signature belongs to the group and not check boxes. As well, we will in the near future upgrade to 4.x.
    However, we are really curious by this issue and would prefer a real solution and not a symptom-fix-hack.

  7. #7
    Ext Premium Member Jan (HL)'s Avatar
    Join Date
    Aug 2010
    Location
    Germany
    Posts
    111

    Default

    I (Chrome 30, OS X) cannot confirm the issue in that fiddle, but I have some Chrome 30 only issues with Ext JS 3.x apps (Sencha's support app and an older legacy app in our company).

    I'm still looking for a bug in Chrome (Jira is looking bad, too), but could not something (like the JIT-issue in Firefox 18).

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •