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
We have this rule, which we discussed, implemented and knew could be problematic as a general rule: a { color: #266c9a; border-bottom: 2px solid #266c9a; }
It is problematic for everything except as links in a block of text. My use case is links in tables or as headings.
It is easy enough to write a custom rule to remove this underline, but is it a good idea to include a .remove-underline class to anchors? (It should get a better name of course)
The text was updated successfully, but these errors were encountered:
We need more than just color to differentiate a link from block-text so we are skeptical to add a helper-class to remove underline. Is this an aesthetic issue? If yes then we should make new ways to present links in tables and other components.
Yes, it's aesthetic. Any solution to remove the undelines is fine by me. I don't believe that my example Charlie Checkoutcustomer under Customer will be a component though.
Another approach that might be okay is to specify underline for block text links: p a { border-bottom: 2px solid #266c9a; }.
We have this rule, which we discussed, implemented and knew could be problematic as a general rule:
a { color: #266c9a; border-bottom: 2px solid #266c9a; }
It is problematic for everything except as links in a block of text. My use case is links in tables or as headings.
It is easy enough to write a custom rule to remove this underline, but is it a good idea to include a .remove-underline class to anchors? (It should get a better name of course)
The text was updated successfully, but these errors were encountered: