Announcement

**Isomorphic** · 24 Jan 2012, 15:26

It's hard to fully grasp the sequence of actions from the logging info you're posting here but the expected / intended behavior is:

- when a click mask is shown it remembers what component has focus
- when hidden it resets focus back to that component, unless focus has shifted to another component since the mask was shown
- when a new click mask is shown it should do the same thing - remember the current focus canvas (it has no idea about what previous click-masks remembered as the focus target), and attempt to reset to it when hidden, unless focus has validly gone somewhere else while the mask was up.

If this isn't what you're seeing, we'd need to see a standalone test case to tell if this is actually a framework bug or not. Certainly we're not aware of bugs in this area (though you should be aware that focus/blur are asynchronous in IE meaning if you've called "focus()" on some component and then show the clickMask in the same thread, the onfocus handler may not have yet fired so the clickMask may fail to pick up the new focus target).

We do have internal APIs for manipulating the "masked focus target" which we could expose to you at a pinch, but you should be aware that these will be unsupported. We can't guarantee they won't change over time (the best we could offer you would be to notify you via this thread if they do change).

**acarur01** · 25 Jan 2012, 05:21

What I'm seeing is that this button that I am clicking on which calls showClickMask a second time is not being registered as a focusCanvas. It could very well be a timing issue on our part. I will turn on scrolling and nativeFocus to see exactly what is going on when I click the button

**acarur01** · 25 Jan 2012, 07:53

Just to give an update on what I've found - we have logic to set the focus back on the last focused item before the server action - which in this case is the select field - my guess is when I click the button, it has not fully completed the selection - when I call getFocusCanvas() just before I send the click action to the server, the canvas I get is that of the select field's dynamic form and not the button. I've gotten it to work by forcing the focus back on the clicked element when the click action is invoked.

**Isomorphic** · 25 Jan 2012, 19:49

Hi Ariane,
From your description it's not clear whether there's a framework bug - sounds more like an application-specific timing issue with your focus manipulations.
In any case - good to hear you have a working solution. If you find the problem does persist for some reason and you'd like us to look further, if you can put a test case together for us we'll be happy to take a look

Regards
Isomorphic Software

Announcement

hideClickMask

Comment

Comment

Comment

Comment