Results 1 to 2 of 2

Thread: Classic toolkit: setLoading and setDisable bug

    You found a bug! We've classified it as EXTJS-20091 . We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.
  1. #1

    Default Classic toolkit: setLoading and setDisable bug

    Ext version tested:
    • Ext 6.0.0.640
    Browser versions tested against:
    • Safari 7.1.8
    Description:After execute following commands:
    Code:
    container.setDisabled(true);
    container.setLoading(true);
    container.setLoading(false);
    container.setDisabled(false);
    the container was remained disabled. If swap two last methods:
    Code:
    container.setDisabled(true);
    container.setLoading(true);
    container.setDisabled(false);
    container.setLoading(false);
    it worked correct
    Steps to reproduce the problem:
    The result that was expected:
    • Component was enabled
    The result that occurs instead:
    • Component was disabled

  2. #2
    Sencha User joel.watson's Avatar
    Join Date
    Nov 2014
    Posts
    3,120

    Default

    Thanks for the report! I have opened a bug in our bug tracker.

Similar Threads

  1. [FIXED] Ext.util.Cookies belongs to classic toolkit
    By nikolay.bobrovskiy in forum Ext JS 6.x Bugs
    Replies: 1
    Last Post: 15 Jul 2015, 2:46 PM
  2. How to use classic toolkit in tablet
    By alfa19 in forum Ext JS 6.x Q&A
    Replies: 1
    Last Post: 6 Jul 2015, 6:44 AM
  3. tbtext and setDisable
    By Francois Lecroart in forum Ext 3.x: Help & Discussion
    Replies: 1
    Last Post: 10 Jun 2010, 2:35 AM

Posting Permissions

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