Thank you for your post.
Only direct operations can trigger scripts.
In the Notes section of FileMaker Pro 13 Help for OnLayoutEnter script trigger, it states, "This trigger does not activate if the layout is changed remotely." In addition, it say "See 'Changing object data without activating script triggers' for a list of actions that do not activate this script trigger."
The OnRecordLoad script trigger also references this same section.
Script triggers are explained not to launch for record data being changed by background processes (such as Replace Field Contents, or another user's modification), and it would make good sense for "if the layout is changed remotely" to likewise describe OnLayoutEnter not to be tripped if the layout is modified ("changed") in another window.
However, involuntary navigation due to deletion-related processes does have precedent for launching script triggers: you will most certainly trip OnRecordLoad if the record you're on is deleted by another user/window and you land elsewhere. This layout behavior is inconsistent with that behavior (which one is the error? that OnRecordLoad fires or that OnLayoutEnter doesn't?).
I suggest you enter this as a product suggestion into our Feature Requests web form at:
The entries into this web form populate a database that is monitored by Product Management and Development. Each web entry is discussed and considered for possible implementation in a future release. Although I could copy your post and paste it into the web form, there are a couple of contact questions asked on the form that only you can answer.