Search Type: Posts; User:

Page 1 of 2 1 2

Search: Search took 0.05 seconds.

  1. Thanks for sharing this guys. I tend to use @siq (post #27) 's patch, since it targets the root-cause of the issue.
  2. There are more issues with the current default (eval-based) approach. E.g. \u2028 and \u2029 characters can not be decoded using eval since they are not valid in a string, but work fine with...
  3. I worked around the issue by resorting the fields _after_ constructing the Model:

    Ext.define('App.model.MyModel', myModelConfig, function (function (myModel) {
    var correctOrder =...
  4. The same issue (still?) applies to ExtJs 4.2.2
  5. Running into the same issue here using 4.2.2 . Noticed some layout-rendering issues too.

    Ext 5 beta has the same issue. I've set up a fiddle here:

  6. The issue here is a local store, with a configured pageSize. This will add a pagingtoolbar to the combo-picker that will do a "loadPage" and empty the store, because it has not idea of...
  7. Possible Fix:

    Ext.override(, {
    createMenuStore: function () {
    var me = this,
    options = [],
    i, len, value;
  8. Fiddle is not possible, 4.2.2 nor Ext.ux is available there...

    Due to an Issue in Ext 4.2.2 any configured options to Ext.ux.grid.filter.ListFilter may be removed by...
  9. +1 - These warnings are annoying and i don't want to mangle "vendor" code.

    The same stuff (scrollLeft / scrollTop) throws warnings from other places too, e.g. Ext.Component.focus()
  10. This issue was _NOT_ fixed in 4.2.2
  11. Replies
    Is there any way to load regular AMD modules / code properly and bundle them in the production build?

    I'm surpised i can't find this question in the first place...

    Thanks in advance for any...
  12. Whoops, made a typo:


    should be

  13. Thanks for the fast reply!

    While reading through this thread i could have known that the issue would relate to this... Sorry for the inconvenience...

    However, i do think it would be more...
  14. Thanks for your work, i'ts much appreciated.

    I've just updated to the latest stable version 2.7 noticed a bug: when editing in HTML-mode and apply-ing the changes,

  15. Ext version tested:

    Ext 4.2.0
    Ext 4.2.1

    Browser versions tested against:
  16. Hi,

    I was wondering where and how the ExtJs-version dependency should be entered in package.json when creating a package.

    When adding some code to the "patches" folder for example, the code...
  17. the deletion of the repo worked like a charm with a clean install of `Sencha Cmd v3.1.2.342`

  18. This is indeed incorrect behaviour. "Home" should navigate the list, "SHIFT+Home" should select the text in front of the cursor. Mapping the "Page up" and "Page down"-key to browsing pages makes even...
  19. I don't get it why no one else seems to run into this issue. This is on my shortlist too!

    For anyone puzzling how to get stack traces of errors in a production environment, after hours of digging...
  20. Good question and clear answers by the way... thnx!
  21. Bug confirmed here: Focusmanager breaks default use of tabindex.
  22. That should do it. Thanks!
  23. Hi there,

    I'm looking for a way to differentiate the development and production HTML of my Extjs project. The development version could load extra JavaScript to help debugging errors, while the...
  24. ... is needed to make sure can read te records properly in ExtJs 4.2.0

    Ext.override(, {
    extractData: function (root) {
  25. @allansun Thanks. This fix is still needed (:() and working for ExtJS 4.2.0 (release) too!
Results 1 to 25 of 50
Page 1 of 2 1 2