So you should be able to prevent navigation on iOS using:
on browserLoadRequest pURL, pType
-- iOS only
end browserLoadRequest
But that does not work with the browser widget. Also I don;t seem to be
able to respond to browser html / javascript events that seek to open a url
in a new browser tab
Is there a way to prevent the desktop browser widget from navigating to a
new url by blocking a message? I seem to remember it was possible but
intercepting: browserNavigateBegin, browserDocumentLoadBegin messages do
not prevent the navigation. I wish to process a url dropped on the page
rather tha
Many thanks to Richard, for his interesting results and for the reminder that
speed testing is pretty easy. I ran a similar test on a slightly different
task--flipping among 50 different groups, or 50 different cards--and got
similar results. Adding a “lock messages” sped up the card option by
