Search Type: Posts; User: nohuhu

Page 1 of 5 1 2 3 4

Search: Search took 0.02 seconds.

  1. Replies
    3
    Views
    377
    This was a bug; the fix should be available in nightly builds of 5.0.2.

    Regards,
    Alex.
  2. Fixed, thanks for finding it!

    Regards,
    Alex.
  3. Honestly I've never noticed that mask before. :) Thanks for the report though, I think we need to fix the example.

    Regards,
    Alex.
  4. User 0815,

    Why is it necessary to mask the document body directly, as opposed to use Component.setLoading() method? Could you give some context to this?

    Regards,
    Alex.
  5. @ahamed,

    Thanks for the report, we're aware of the issue and the fix should be available shortly. For your reference, the ticket is EXTJS-14688.

    Regards,
    Alex.
  6. Thanks for the report! I have opened a bug in our bug tracker.
  7. iceteagroup,

    The fix should appear in the nightly builds shortly; please be aware that legacy FocusManager has been deprecated in Ext JS 5.0.1+. You do not need to use FocusManager for keyboard...
  8. EXTJS-13979 is a duplicate of EXTJS-9987 because it is asking for essentially the same thing, and is suffering the same problem: there is no sane way to pass extraParams with CUD operations, it is...
  9. @mitch,

    Not quite. There was (and is) no way to send extraParams with CUD operations. There is a new mechanism to pass metadata with Direct function calls, but it is not backwards compatible with...
  10. @moogjet,

    You're right and it's clearly a bug. Thanks for the report!
  11. JimGrimmett,

    That was EXTJS-14688.

    Regards,
    Alex.
  12. Replies
    3
    Views
    604
    @Mats,

    Use AdBlock to kill the enclosing element - that's what I did and it worked like a charm. ;)

    Regards,
    Alex.
  13. Thanks for the report! I have opened a bug in our bug tracker.
  14. You can tab to the first button and then use arrow keys to get to the other buttons in the same toolbar. This behavior is in accordance with WAI-ARIA requirements for accessible applications:...
  15. That is expected; toolbar takes care of the buttons' tabindices. Try tabbing to a button, or clicking it.

    Regards,
    Alex.
  16. Peter,

    Thanks for the explanations, I was able to reproduce this behavior. This is definitely not a feature, and the behavior is not desirable so I'm going to file a bug report for that one....
  17. FocusManager has been deprecated but not removed yet, and will be part of the framework until some time later. You can keep using it, meanwhile updating your code to work without it.

    Regards,...
  18. Well just so you can ease your mind, I've fixed the bug yesterday and it waits to be merged for 5.0.2. Your input is always highly appreciated, so don't hesitate to bug us. Enjoy your holiday! ;)
    ...
  19. Well I can't really comment on your code behavior without seeing it; maybe that was a bug that got fixed, maybe something else.

    Try this KitchenSink example in 5.0.0:...
  20. Do you have to display both views simultaneously? Hiding a view should make all elements within it untabbable.

    Regards,
    Alex.
  21. @Peter Tierney,

    There is a bug in handling modal load masks that makes elements within a modal window untabbable. If your login form is a modal window, you may have experienced it. This one is at...
  22. Thanks for the report! I have opened a bug in our bug tracker.
  23. Hey I never said I don't believe that there is a problem here. ;) There is in fact a bug that I found with your fiddle, so thanks for that.

    Regards,
    Alex.
  24. That must mean that the password field is disabled, or has tabindex < 0, or is otherwise untabbable. You can check the DOM and find what prevents focus from going to the password field.

    Usually...
  25. The new tabbing behavior is intentional; we're not trying to control where focus goes anymore, except some special cases. This is more in line with industry standard and WAI-ARIA requirements.
    ...
Results 1 to 25 of 120
Page 1 of 5 1 2 3 4