I'm sure that every FileMaker developer has experienced this problem:
We perform a find on an unstored calculation field on a hosted database, not realizing in advance that the find is going to take ages to complete. So we click on the "Cancel" button in the "Find In Progress" dialog box, but FileMaker doesn't actually cancel the find. It simply removes the “Cancel” button and keeps on processing the find request for eons!
See screenshot below for what this looks like.
We really need FileMaker to respect our wishes to cancel the find.