I've noticed an oddness with the Numeric Entry Field and focus events. Is this how it's supposed to work?
First, when a NEF has focus and Enter is pressed on the keyboard, the cursor goes away, any selection is unselected, but the onBlur event does not fire. I can then click on a different widget, which gets focus, but again, onBlur does not fire. If I click off the component or type a tab, the NEF loses focus and onBlur does fire.
Second, when the NEF gets focus, the onFocus event fires twice. I was thinking maybe it's firing once for the container and once for the input, but I wasn't sure how to tell the difference. Adding Stop Propagation did not prevent this.
(In retrospect, I was trying to do something when the NEF changed and onActionPerformed appears to be the place to do this. It does fire if Enter is pressed or if the component loses focus and the value has changed.)
Short answer: it's a funky composite control. This is better shown diagramatically
Yes, that seems like what I observed. Where is that slide from?
It looks like the "Press Enter, click different component, no onBlur event" is not intended behavior and I will report that.
I put it together with my new software. Not ready just yet to announce it, coming soon!
Edit: I see your in retrospect comment, so my comment below is irrelevant, but perhaps interesting nonetheless... 
What are you actually trying to do in the onBlur script? If it's something simple that should happen client-side like that can be handled by CSS, then you should use CSS (perspective styles) with a pseudo-class (i.e. :hover), as these are guaranteed to fire. Anything that relies on a handshake back to the gateway is not guaranteed (this is also why momentary/jog buttons are a no go in Perspective)
For example, if you want to show a component only when another component is hovered, this should be handled in CSS, not by using the event handler scripts and custom props.
