Gelmiş geçmiş en büyük porno sitemiz olan 2pe de her zaman en kaliteli pornoları sunmayı hedefledik. Diğer video sitemiz olan vuam da ise hd porno ağırlıklı çalışmalara başladık.

    You found a bug! We've classified it as EXTJS-3046 . We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.
  1. #21
    Sencha Premium Member
    Join Date
    Jul 2012
    Posts
    95
    Vote Rating
    3
    grizzly21 is on a distinguished road

      0  

    Default


    Absolutely right, it's funny that they call it a feature not a bug..either way, it's bad design and is against conventions..

  2. #22
    Sencha User
    Join Date
    Aug 2010
    Posts
    5
    Vote Rating
    1
    Al Jey is on a distinguished road

      1  

    Default Not a bug

    Not a bug


    This is most certainly not a bug, however it would be nice if setValue would accept a "silent" argument, defaulting to false, so if you were to pass true as a second argument, for example, the event wouldn't get triggered.

  3. #23
    Sencha Premium Member
    Join Date
    Jul 2012
    Posts
    95
    Vote Rating
    3
    grizzly21 is on a distinguished road

      0  

    Default


    In the meantime you can use suspendEvents(), resumeEvents()

  4. #24
    Sencha User
    Join Date
    May 2013
    Posts
    1
    Vote Rating
    0
    juz4u2me is on a distinguished road

      0  

    Default


    How about using setRawValue() to overcome this issue instead? I see that it does not trigger the 'change' event.

  5. #25
    Sencha User
    Join Date
    Mar 2013
    Posts
    13
    Vote Rating
    -1
    rt.karthik87 is an unknown quantity at this point

      -1  

    Default


    wats the final result of this bug... i too dont want to fire change event when i call setValue function.