You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
edit-bitmask CDR does not visually indicate required state and swallows server errors #502
Please provide the branch(es) you discovered this issue in
v92
Environment Details
Edge 149.0.4022.80, Windows 11, 9.2.2
Please provide a minimal set of steps to reproduce the issue
Open the detail page containing the mandatory bitmask column.
Observe the field while it is empty:
❌ No asterisk (*) is shown next to the label.
❌ The outline is not red.
❌ The placeholder text is not red.
❌ No "This field is mandatory." message is shown below the field.
Select one or more options, then click the clear (x) button of the eui-selectwithout focusing the field first.
❌ The field does not transition to the invalid state — no red styling
and no error message appears.
Description
The EditBitmaskComponent (CDR editor for bitmask columns) has two issues
that make it inconsistent with other CDR editors (e.g. edit-default, edit-date):
1. Missing visual feedback for required fields
No asterisk (*) is shown next to the label when columnContainer.isValueRequired is true.
The field outline does not turn red when the field is required but empty/invalid.
The placeholder text remains in its default color even when the field is invalid.
The label color does not reflect the invalid state when the field is unfocused.
No inline error message is displayed when the field is left empty.
Clearing the value via the eui-select clear button (without focusing the field first)
does not update the touched/dirty state, so the required-styling never kicks in.
2. Server errors are silently swallowed
In writeValue(), the catch block sets this.lastError = undefined instead
of this.lastError = e:
Activity
github-actions commentedon Jul 23, 2026
This issue has not seen any action for a while! Closing for now, but it can be reopened at a later date.
asattler commentedon Jul 27, 2026
This should not be closed automatically!
github-actions commentedon Aug 27, 2026
This issue has not seen any action for a while! Closing for now, but it can be reopened at a later date.
asattler commentedon Aug 31, 2026
again: This should not be closed automatically!
github-actions commentedon Oct 1, 2026
This issue has not seen any action for a while! Closing for now, but it can be reopened at a later date.
asattler commentedon Oct 2, 2026
Well, it seems that nobody is taking care of the issues. But still: this issue is not solved and can not be closed..