Search Type: Posts; User: Phil Guerrant

Page 1 of 5 1 2 3 4

Search: Search took 0.04 seconds.

  1. Replies
    Looks like a bug with listener scope resolution on plugins. I have opened a bug in our bug tracker.
  2. "self" is a framework-internal scope that indicates that the listener was declared on a class body (as opposed to an instance config). It is an internal implementation detail and shouldn't be relied...
  3. The bug is fixed. The default behavior for cell editors is to be vertically centered over the grid cell. Unfortunately this alignment resulted in the editor being clipped when close to the edge of...
  4. This bug occurs when you use "fit" layout with "html" and scrollable:true. We're working on a fix, in the mean time, if you remove layout:'fit' and use the default ('autocontainer') layout, it...
  5. Thanks for the report! I have opened a bug in our bug tracker.
  6. With the removal of IE6/7 support in Ext 5, we are able to use the browser's native querySelector/querySelectorAll to execute dom queries. Since these native functions cover 99% of the use cases, we...
  7. Replies
    to elaborate on what Seth said - you can make your toolbar match the color of the active tab by setting it's background-color to $tab-base-color-active in your app or theme's sass.
  8. enableTextSelection is currently only available on Ext.view.Table (grid and tree views), but not on Ext.view.View currently.

    In v5, for accessibility reasons view items receive focus when...
  9. Width and height of Panels and Windows are typically set by the Layout of the component's owning container, or configured directly on the component. They are an application concern, not a theme...
  10. Ext.view.Table already has a way to configure text-selectability (enableTextSelection: true - it is disabled by default for grids). We could maybe consider moving that config upward to...
  11. You could try:

  12. @SebTardif I'm trying to create a simple test case so I can make sure we have the correct behavior in future releases. I've created the following fiddle, but it doesn't seem to fail as you are...
  13. You can know for sure if the override is working by putting a breakpoint inside the isGarbage function in the override.

    If the override is being called, I'd need more detail to know for sure...
  14. give "sencha app watch" a try.
  15. This is by design so that you can use UIs like "default" on a toolbar.

    If you need the -toolbar suffix just add it as part of your UI name
  16. Something like this perhaps?

  17. You'd get that error if the Ext.dom.Element's "dom" property was null, that is if the element had already been destroyed. That's about all I can tell based on your description.

    Have a look at the...
  18. fieldLabel is camel case - you need to capitalize the "L"
  19. Are you overriding any methods of Ext.window.Window in your derived class? If so, make sure you are including a call to
    this.callParent(arguments); in those overridden methods
  20. hard to say without seeing your code. can you make a fiddle out of your test case?
  21. I see your point. It would be more intuitive to use the component instance as the scope if you've given us an inline function instead of a method name. I'll see what it takes to get this fixed in a...
  22. works for me

    xtype: 'container',
    renderTo: document.body,
    height: 200,
    width: 200,
  23. Replies
    Have a look at Ext.scopeCss
  24. you could try using a column layout instead of hbox on the paging toolbar. This will allow the items to wrap when they run out of horizontal space, but it requires a bit of CSS tweaking...
  25. The problem is your use of Ext.Msg.alert(). Since Ext.Msg is a singleton instance, a second call to Ext.Msg.alert() will simply replace the first one:

    Ext.Msg.alert('Message 1', 'Hi');...
Results 1 to 25 of 118
Page 1 of 5 1 2 3 4