Since when do server-side edits to fields (e.g. Plugin or Workflow) come back after Save and trigger the on-change of those fields on the form?

Is there any documentation of this? Anyway to stop it?

Example:

• Assume a CRM field "Name" has a JS onchange to alert the user "you changed my name!"
• Assume a synchronous Workflow triggered by another field field "Calculate Name" checkbox, will set Name to something server-side
• User checks "Calculate Name" and saves
• Result: "Name" field is updated on the screen as expected, by the synchronous Workflow's edited value
• UNEXPECTED Result: the JS onchange of "Name" is triggered and user sees "you changed my name!"

This is a simplified/odd example... but it raises an issue that now JS that was only meant to respond to User action is actually now also responding to server-side action... but only when the Update is initiated by a User on a Form. It's very unexpected, inconsistent.