Search Type: Posts; User: yuriy

Page 1 of 2 1 2

Search: Search took 0.26 seconds.

  1. Is there any other (elegant) way to prevent this from happening in ?
  2. I can now confirm that the issue is with touch device being present, because if I disable "HID-compliant touch screen" in device manager and restart the browser, the issue disappears.
  3. Ok... a very stupid theory: what if that's because my laptop has a multitouch screen?
  4. Yes, because Chrome 34 and IE 11 are also affected.
    I also tried to unzip that on a different machine (WS2012 R2) under IIS and use IE 11 installed there. The issue is reproduced.

    I guess you...
  5. Sure, here's how it looks

    Also, here's the project as it was generated on my machine:
  6. Ok, I tried to isolate a problem a bit further. Here's what I found out so far:
    - cannot reproduce in fiddle
    - cannot reproduce in local "sandbox": putting unmodified MainModel.js,...
  7. Ext version tested:

    Browser versions tested against:

    Chrome 34
    DOCTYPE tested against:

  8. This! It's not crisp with PNG graphics :)
  9. Or is it there and I missed it completely?
    To be honest I always hated this aspect of the framework: unsafe by default.

    Why not do it like everybody else does? Default binding syntax escapes html...
  10. Replies

    But seriously, why the hell is this not hotfixed as some kind of 4.1.4?

    Ext version tested:

    ExtJS 4.1.3
    Browser versions tested against:

    IE9 (9.0.8112.16421, update versions: 9.0.12)
    DOCTYPE tested against:
  12. Hi, unfortunately I was also hit by this memory leak issue (and some other annoying things with sandbox).

    Richard did a very good job with tracking this down to "fireDocReady", so I just took it...
  13. Replies
    I already mentioned the branch name, but let me point to the file itself:
    you see that ">>>>>>>" there?
  14. Replies
    Hi guys, seems like ext-4.0.x branch has a merge conflict or something committed for a while now.
    It's in RadioGroup.js line 98.
    If you build with that line, nothing is working.
    Am I the only one...
  15. If this is something that you started experiencing only after updating to 3.1, try specifying "forceLayout: true" for your TabPanel (I had to do it during one of pre-3.1 trunk updates to fix some...
  16. A test case I supplied works fine in both IE and FF with public ExtJS 3.1 (I downloaded it to check, since I usually use stable branch).
    Are you sure you are experiencing the same issue?
  17. Ok, thanks for the info.
  18. I am sorry, but bump.
  19. Replies
    Yeah, unfortunately I have to agree about "business maturity" here, adding:
    - no svn activity (and some strange private builds as attachments in this thread)
    - no news from author here and on...
  20. Replies
    Doing "history back" on backspace is something most browsers do.

    I disable it with this:{
    key: Ext.EventObject.BACKSPACE,
  21. Ext version tested:

    Ext 3.x trunk rev#5636

    Adapter used:

  22. I made a mistake in initial report - revision 5465 only brought Firefox exception, while the one in IE was there even earlier... didn't track down to an exact revision number though.

    Before today...
  23. Ext version tested:

    Ext trunk rev 5627

    Adapter used:
  24. Replies
    Thorsten, first thanks for the component - just started evaluating it.
    I found a bug in the component that occurs pretty often for me:
    if the grid is removed while data request is in progress, it...
  25. OK, that's what I wanted to know.

    Thanks :)
Results 1 to 25 of 29
Page 1 of 2 1 2