Closed esau-morais closed 1 year ago
Would these changes affect the existing design? If so, how? Can you add a screenshot?
Would these changes affect the existing design? If so, how? Can you add a screenshot?
This PR applies abstraction to some classes, which affects the following elements:
The idea is to divide styling between an icon and button handling with their use cases without implying the custom.css
I've applied a default background for the icon button, but it can be forced in the custom.css
using !important
As you mentioned @esau-morais, this is a destructive PR. It forces people to update their custom CSS or their page will look bad. We cannot do it. Everything we do must be backward compatible. Example:
As you mentioned @esau-morais, this is a destructive PR. It forces people to update their custom CSS or their page will look bad. We cannot do it. Everything we do must be backward compatible. Example:
I don't think the user will actually need to update the custom.css besides what I pointed out in the last comment once I've only extracted class names in refactor way. How did you reproduce this kind of styling change? Because before I made this PR, I tested with many users' links, including this one
PS.: I don't think my solution is the best and or the most beautiful to be honest, maybe suggesting a new default styling to the button is a great idea
@esau-morais sorry, I tested it without applying the changes for the backend. I will fully test it tomorrow
Description
What types of changes does your code introduce to links.dev?