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
The text was updated successfully, but these errors were encountered:
lizhuomeng71
changed the title
QA: Write Automated Tests for previous Inputissues #2042
QA: Write Automated Tests for previous Inputissues
Aug 29, 2024
ArakTaiRoth
changed the title
QA: Write Automated Tests for previous Inputissues
QA: Write Automated Tests for previous Input issues
Aug 29, 2024
Acceptance Criteria:
Automated tests are written for the following stories:
Block: 100% width of inputs not working #1867
Update to Form Item spacing #1796
Bug: Inconsistent behaviour between input components #1703 (question about on Key Up)
Input: Focus with leading/trailing content #2089
Bug: Can't visually empty a FormControl value (Angular) #1598
[Bug]: Incorrect border rendering on Text Field in the Error and Focus state #1577
[Bug]: GoAInputNumber - The number shown in the input is the decimal, but only the integer value is passed back in the onChange event. #1532
Bug: Input type password in Edge shows another icon #1499 (some input does not have icon)
Bug: Disabled Input no longer appears disabled #1453
Bug: Problems with Input Time #1380 (this is not working for react, date type will load)
[Bug]: LeadingContent and TrailingContent have visible margin-bottom inside the Input #1308
[Bug]: Small padding adjustment | padding-left on text area and text input inconsistent #1276
Input search type angular component does not function like the react component #1220
Icon button position in input #1149
goa-input with pre/suffix disabled border issue #976
Reviewed and decide not to automate
The text was updated successfully, but these errors were encountered: