Identify components with broken UI - do they need tests too?

[lukestanley]

No description provided.

[lukestanley]

@gsambrotta
I was looking at the GitHub Projects demo video and they converted a check list into Issues, I wanted to see if this was possible so I made an issue for Angular 16 and then pasted the list from the Angular 16 PR comment into the top of the issue.
I saw from:
https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists
"Tip: You cannot create task list items within closed issues or issues with linked pull requests."
So I am concerned, if I like the issue to the PR, suddenly, automatically making issues for it might not work! This seems kinda weird to me, but anyway, I only wanted to test it for now but if you want the check list made into actual issues, see #440.

[gsambrotta]

• @angular/material/menu - Angular 16 has different spacing + hover on buttons + button font Issue Fix Angular Material in Angular 16 #446
• ag-grid-angular - quite different look + Launch buttons don't show up Issue Fix Grid on Angular 16 #445
• Form is red when error arise
• /connet page last link text font style and size

[gsambrotta]

I would close this in favour of #441 which is more complete of the issue to work on after Angular 16 upgrade

[dahacouk]

@gsambrotta did you mean to say "I would close this in favour of #441" above? As it seems you are referring to itself, yes?