Gelmiş geçmiş en büyük porno sitemiz olan 2pe de her zaman en kaliteli pornoları sunmayı hedefledik. Diğer video sitemiz olan vuam da ise hd porno ağırlıklı çalışmalara başladık.

  1. #11
    Ext JS Premium Member neongrau's Avatar
    Join Date
    Mar 2007
    Posts
    249
    Vote Rating
    0
    neongrau is on a distinguished road

      0  

    Default


    just did a quick test. and it seems (but beware i haven't yet looked at Ext.KeyNav)
    that there is a mixup with keyCode and charCode on the keypress event.

    with "keypress" FF reports for SHIFT+8:
    keyCode: 0 and charCode: 40

    with "keydown" FF reports for SHIFT+8:
    keyCode: 57 and charCode: 0

    so when using the charCode instead of keyCode the keypress gets wrongfully mapped to keyCode 40 which is in fact cursor down?!?

  2. #12
    Sencha User jack.slocum's Avatar
    Join Date
    Mar 2007
    Location
    Tampa, FL
    Posts
    6,955
    Vote Rating
    16
    jack.slocum will become famous soon enough

      0  

    Default


    So the down arrow and shift+8 return the same thing?
    Jack Slocum
    Ext JS Founder
    Original author of Ext JS 1, 2 & 3.
    Twitter: @jackslocum
    jack@extjs.com

  3. #13
    Ext JS Premium Member neongrau's Avatar
    Join Date
    Mar 2007
    Posts
    249
    Vote Rating
    0
    neongrau is on a distinguished road

      0  

    Default


    yes, it looks like Ext.KeyNav returns the charCode as keyCode which should be different.

  4. #14
    Ext JS Premium Member neongrau's Avatar
    Join Date
    Mar 2007
    Posts
    249
    Vote Rating
    0
    neongrau is on a distinguished road

      0  

    Default


    hi jack!

    when looking at Ext.EventObjectImpl.prototype i see that getKey and getCharCode always try to fall back to the other value.

    you can't do that since they have different meanings, keyCode is the id of the key while charCode is the reference to the typed character. for example:

    String.fromCharCode(40) is "("
    or
    String.fromCharCode(38) is "&"

    that must not be taken as a keyCode!!!

    i tried it with the "|| .." parts commented out:

    Code:
    Ext.EventObjectImpl.prototype {
    ...
            getCharCode : function(){
                return this.charCode;// || this.keyCode;
            },
    
            
            getKey : function(){
                var k = this.keyCode;// || this.charCode;
                return Ext.isSafari ? (safariKeys[k] || k) : k;
            },
    ...
    this results in Firefox working as expected, nothing seems to break in IE, shouldn't have any effect to Safari. Opera will still do it wrong but not better or worse then before.

  5. #15
    Sencha User jack.slocum's Avatar
    Join Date
    Mar 2007
    Location
    Tampa, FL
    Posts
    6,955
    Vote Rating
    16
    jack.slocum will become famous soon enough

      0  

    Default


    The reason for that is FF w/ keypress in many cases does not return a keyCode, only charCode.

    If you scroll to the bottom of this page:

    http://www.quirksmode.org/js/keys.html

    There is a nice key tester. If you check keypress and keydown and use FF, you will see what I mean.

    However there is probably a range of keys that we can filter (like 37-40, 8, 13, etc). If you can help determine what keys are going wrong on your keyboard, I would happy to add that filter in.

    Thanks,
    Jack
    Jack Slocum
    Ext JS Founder
    Original author of Ext JS 1, 2 & 3.
    Twitter: @jackslocum
    jack@extjs.com

  6. #16
    Ext JS Premium Member neongrau's Avatar
    Join Date
    Mar 2007
    Posts
    249
    Vote Rating
    0
    neongrau is on a distinguished road

      0  

    Default


    it's probably not that easy. since it differs not only from brwoser to browser (from what i read only gecko browsers and opera (partly) seem to support charCode). it also differs by the event listened for.

    for example: the SHIFT+8, with onkeydown it will only be report keycodes (shift, 8, and the combo), while onkeypress will resemble the generated character that was supposed to be printed into a textbox or s.th. as charCode. so it'd be necessary to decide what element has the focus and will this element accept the insertion of the char. and only if it does accept
    the char the custom mapped action should be allowed to get cancelled.

    but i see the differences in all browsers with that are a huge mess to deal with

Similar Threads

  1. Has anyone tried Opera 9.10? turtle speeds?
    By vtswingkid in forum Ext 2.x: Help & Discussion
    Replies: 2
    Last Post: 20 Feb 2007, 1:53 PM
  2. using keyboard (arrow up/ down) in grid with FF?
    By franklt69 in forum Ext 1.x: Help & Discussion
    Replies: 15
    Last Post: 6 Feb 2007, 6:00 AM
  3. Toolbar Problems in Firefox and Opera
    By adzaip in forum Ext 1.x: Help & Discussion
    Replies: 1
    Last Post: 23 Dec 2006, 5:15 AM

Thread Participants: 2