Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make css more specific as to avoid interference #48

Merged

Conversation

NightJar
Copy link
Contributor

@NightJar NightJar commented Oct 7, 2019

The RealMe login detail box is strongly specified by the RealMe design team. It needs to look one of three pre-defiend ways, without modifications caused by cascading rules.
However the CSS supplied is not specific enough (nor perscriptive enough with the rules) to ensure that this is the case. So we can tighten this to be more robust.

The RealMe login detail box is strongly specified by the RealMe design team. It needs to look one of three pre-defiend ways, without modifications caused by cascading rules.
However the CSS supplied is not specific enough (nor perscriptive enough with the rules) to ensure that this is the case. So we can tighten this to be more robust.
@brynwhyman brynwhyman requested a review from madmatt October 11, 2019 00:55
Copy link
Member

@madmatt madmatt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

Thanks @NightJar!

@madmatt madmatt merged commit 80ef172 into silverstripe:master Oct 23, 2019
@NightJar NightJar deleted the pulls/3.1/cssspecificity branch January 12, 2020 21:32
emteknetnz pushed a commit to creative-commoners/silverstripe-realme that referenced this pull request May 13, 2022
The RealMe login detail box is strongly specified by the RealMe design team. It needs to look one of three pre-defiend ways, without modifications caused by cascading rules.
However the CSS supplied is not specific enough (nor perscriptive enough with the rules) to ensure that this is the case. So we can tighten this to be more robust.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants