Looks like we can't reproduce the issue or there's a problem in the test case provided.
  1. #1
    Sencha User
    Join Date
    Feb 2012
    Posts
    115
    Vote Rating
    9
    Sottilde will become famous soon enough

      0  

    Default Renaming a custom component sometimes gives an error and deletes the component

    Renaming a custom component sometimes gives an error and deletes the component


    Every once in a while, if you rename a custom component, you see an error box:

    RangeError: Maximum call stack size exceeded.

    This wouldn't be such a huge deal (as you can safely 'Ignore') but it also deletes the custom component!

  2. #2
    Sencha - Architect Dev Team aconran's Avatar
    Join Date
    Mar 2007
    Posts
    8,185
    Vote Rating
    63
    aconran is just really nice aconran is just really nice aconran is just really nice aconran is just really nice aconran is just really nice

      0  

    Default


    Any additional steps to reproduce? Build 298 or 309?
    Aaron Conran
    @aconran
    Sencha Architect Development Team

  3. #3
    Sencha User
    Join Date
    Feb 2012
    Posts
    115
    Vote Rating
    9
    Sottilde will become famous soon enough

      0  

    Default


    It was happening with nearly every custom component I tried in Build 298. It appears to be fixed in 309, I can't reproduce.

  4. #4
    Sencha - Architect Dev Team aconran's Avatar
    Join Date
    Mar 2007
    Posts
    8,185
    Vote Rating
    63
    aconran is just really nice aconran is just really nice aconran is just really nice aconran is just really nice aconran is just really nice

      0  

    Default


    Okay, please let us know if you encounter it again.
    Aaron Conran
    @aconran
    Sencha Architect Development Team