However, in this scenario, the error is not clear:..
The display is masking the underlying error. The field is highlighted amber giving the sharp-eyed user the hint that the problem is at field level (though many could miss that). If you click on that field you see the field-level compiler warning - and note that this warning has caused the frame level error (still displayed) to be shown as a warning.
I think we need to explore (possibly in a branch) changing the policy here, such that ...
If there is a field-level warning/error then there should be no warning/error message displayed for the frame that directly owns that field.
This error is clear:
However, in this scenario, the error is not clear:..
The display is masking the underlying error. The field is highlighted amber giving the sharp-eyed user the hint that the problem is at field level (though many could miss that). If you click on that field you see the field-level compiler warning - and note that this warning has caused the frame level error (still displayed) to be shown as a warning.
I think we need to explore (possibly in a branch) changing the policy here, such that ...