shamrickus opened a new issue, #7483:
URL: https://github.com/apache/trafficcontrol/issues/7483

   <!--
   ************ STOP!! ************
   If this issue identifies a security vulnerability, DO NOT submit it! 
Instead, contact
   the Apache Traffic Control Security Team at 
[email protected] and follow the
   guidelines at https://apache.org/security regarding vulnerability disclosure.
   
   - For *SUPPORT QUESTIONS*, use the #traffic-control channel on the ASF slack 
(https://s.apache.org/tc-slack-request)
   or the Traffic Control Users mailing list (send an email to 
[email protected] to subscribe).
   - Before submitting, please **SEARCH GITHUB** for a similar issue or PR
       * https://github.com/apache/trafficcontrol/issues
       * https://github.com/apache/trafficcontrol/pulls
   -->
   
   <!-- Do not submit security vulnerabilities or support requests here - see 
above -->
   ## This Bug Report affects these Traffic Control components:
   <!-- delete all those that don't apply -->
   - Traffic Portal v2
   
   
   ## Current behavior:
   Across the TPv2 code base we currently style Angular Material components by 
attaching to _internal_ elements/attributes. For instance `mat-card` or 
`.mat-mdc-card` (once #7454 is merged).
   <!-- Describe how the bug happens -->
   
   
   ## Expected behavior:
   These instances should be updated to use our own classes as selectors, for 
instance instead of attaching to a `mat-card` we should add our own class to it 
and select for that class. The Angular Material library is built with this in 
mind so this method of styling.
   <!-- Describe what the behavior would be without the bug -->
   
   <!-- If the current behavior is a bug, please provide the *STEPS TO 
REPRODUCE* and
   include the applicable TC version.
   -->
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to