[Brian]

Heh, my previous response wasn't intended to read as "I think it's better the way it currently is", but I can see how it might have. :-)

I'm not sure why it does that; may be a behavior we chose, might be one we just inherited from the frameworks or coded up and no one noticed/reported the issue until now.

Either way, I can't get the behavior he does want, but he does at least part of the time; having repro steps may help us figure this out. :-)