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
I think, it is reasonable to add some styles for .close class since it is used for styling in rainbow. For example,
.rainbow {
.close {
float: none;
font-size: inherit;
font-weight: inherit;
line-height: inherit;
text-shadow: none;
opacity: 1;
filter: none;
&:hover,
&:focus {
color: inherit;
text-decoration: inherit;
cursor: inherit;
opacity: 1;
}
}
}
This means, that in scope of .rainbow we have defined styles for .close class.
The text was updated successfully, but these errors were encountered:
Thank you for reporting!
Actually we can prevent the layout issue by overriding with .rainbow .close { ... }, but I don't think it's perfect. (see: ccampbell/rainbow#101)
I'm planning to switch the syntax highlighting library itself.
I will choose a new library that uses high compatibility class names, like .some-prefix-close.
I think, it is reasonable to add some styles for .close class since it is used for styling in rainbow. For example,
.rainbow {
.close {
float: none;
font-size: inherit;
font-weight: inherit;
line-height: inherit;
text-shadow: none;
opacity: 1;
filter: none;
&:hover,
&:focus {
color: inherit;
text-decoration: inherit;
cursor: inherit;
opacity: 1;
}
}
}
This means, that in scope of .rainbow we have defined styles for .close class.
The text was updated successfully, but these errors were encountered: