Hi all,
Thanks Jeremy for posting my workaround about activating the view before doing IsolateElementTemporary. In fact this appears to be needed for all uses of IsolateElementTemporary, regardless of if the view is newly created or not!
Also, I thought this behavior was fixed in our internal development release...but it is not. Sorry for any false hope there. We'll keep digging for the root cause.