Focus on TextField breaks when using sencha.

[mitchellsimoens]

Can you try a third case... Make it just like the 2nd test case but just add the Sencha Touch JS and CSS code?

[ed.canas]

I have created with sencha touch js and the css added, and same problem focus does not work.
http://www.oismobile.com/touch3.html

I've tried different ways already as far as firing the focus via a sencha button on different listening options. And it goes back to simply adding the js file where it breaks even a regular html button with a focus.

[venumuvva]

Hi Guys,

We are also facing the text field focus issue. Wondering any body has any work around for the focus issue?

Appreciate your help on this.

Thanks in advance

[rdougan]

I'm unsure why you guys are not just using Ext.get('id-of-input').focus() to do this? Also, why are you adding direct listeners using "onclick", and not using our API?

Rob

[ed.canas]

Look at the thread, no matter what you use it will not work, we went back to basics to test the problem. It does not matter if you use Ext.get('id-of-input').focus() or any other derivative it will just not work. Can you look at the samples and test out. Since I have also an open ticket in support for over a Month and it has not been fixed either. The problem is that in Mobile Safari you cannot invoke a focus command. The only time you can do that is when it's initiated via a Touch Command. However Sencha captures all touch commands and re-sends them. There the original touch command is lost and focus will not work.

[rdougan]

Have you tested it with Touch 2? I tested with ST2 and it works fine. I'll have Jacky our resident event guru to have a look-

[Jacky Nguyen]

There was an old hack in Touch 1.x event manager to make click events happen instantly instead of having a default of 300ms delay, and this issue is a side-effect of that.

If you can't move to Touch 2 yet and have to stick with 1.x for a while, here's an (dirty but works) override. Put this right after the inclusion of sencha-touch.js.

Ext.gesture.Manager.onMouseEvent = Ext.emptyFn;
Ext.gesture.Manager.onTouchEnd = function(e) {
    if (Ext.is.Blackberry) {
        e.preventDefault();
    }


    if (this.isFrozen) {
        return;
    }


    var gestures = this.currentGestures.slice(0),
        ln = gestures.length,
        i, gesture, endPoint,
        needsAnotherMove = false,
        touch = e.changedTouches ? e.changedTouches[0] : e;


    if (this.startPoint) {
        endPoint = Ext.util.Point.fromEvent(e);
        if (!(this.lastMovePoint || this.startPoint)['equals'](endPoint)) {
            needsAnotherMove = true;
        }
    }


    for (i = 0; i < ln; i++) {
        gesture = gestures[i];


        if (!e.stopped && gesture.listenForEnd) {
            if (needsAnotherMove) {
                gesture.onTouchMove(e, touch);
            }


            gesture.onTouchEnd(e, touch);
        }


        this.stopGesture(gesture);
    }




    if (Ext.supports.Touch && this.isClick) {
        this.isClick = false;
    }


    this.lastMovePoint = null;
    this.followTouches = [];
    this.startedChangedTouch = false;
    this.currentTargets = [];
    this.startEvent = null;
    this.startPoint = null;
};

[WallTearer]

Jacky Nguyen, are you sure that this is a correct solution?
I've pasted your code right after including the sencha lib, and it not only doesn't make the focus() functionality working, it also breaks the radio buttons (if I have several radio buttons, I can click only on one of them, and others are becoming unresponsive).

It's a very bad bug, and there're lots of folks having the same problem on this forum and on the Internet.
Didn't see anyone who said that he had successfully fixed it.

[davide.cecconi]

IOS Focus problem it is on ver. 2.0.1 too

It 's no solve, I have open a tikect too

I hope that this BUG will solve as soon as possible because It is a big problem for application on IOS

Davide

[olegtaranenko]

Someone added very promisingly notice
Success! Looks like we've fixed this one. According to our records the fix was applied for TOUCH-409 in 2.0.
at the top of topic. Wonderful!
Does he or she not forget saying when or what exact version ST 2.0 is? 2.0.1 has no fix. May be 2.0.1.1 or 2.0.2 which is accessible for subscribers only? Is it really fixed or only looks like ...

Thank for info