This is not a bug, the semantics of onchange are that the field's *value* changing triggers the call. Not the value of something somehow linked through the field.
This is not a bug, the semantics of onchange are that the field's *value* changing triggers the call. Not the value of something somehow linked through the field.