ACTION-5: PinFocus already covered by ATFocusIn/ATFocusOut

Clearing through some of these items:
http://lists.w3.org/Archives/Public/public-indie-ui/2012Sep/att-0000/NewEvents22Aug2012.html

I'm pretty sure the following event suggestion is better covered by the existing events ATFocusIn and ATFocusOut (the original proposal called these AXFocus and AXBlur). There's also no need for the element to be included in context info, because the element is already the target of the event.

Any objections to foregoing this change and leaving the existing events listed here?
https://dvcs.w3.org/hg/IndieUI/raw-file/aba80041ed8d/src/events.html#AccessibilityEvent


> Pin Focus
> The user has explored the user interface and moved their point of regard to a specific widget or ___location. They want to pin focus to that ___location such that further user gestures are directed solely at the pinned item.
> 
> Bubbles: Yes (Not sure, since focus events themselves do not bubble)
> Cancelable: No.
> Context Info:
> the widget or ___location that currently has focus (DOM element?)
Context Info suggestion is redundant, beside the event is already fired on this element.
> Note: There was debate on whether to call this "focus". The group decided on "focus" for the time being even though a keyboard may not be involved. If this name is problematic, it can be changed.
> 
> Note: A "Pin focus" event implies an "Unpin" event. Alternatively, some gesture(s) automatically un-pins the focus. Consider, for example, how a pinned focus would interact with the "Popup" event described below -- if the popup is displayed, does it have focus? Or does the focus remained pinned at its former pre-popup ___location?
>