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

Set safe CSS for progress indicator which does not conflict with Bootstrap #1827

Merged
merged 1 commit into from
Feb 17, 2016

Conversation

irnc
Copy link
Contributor

@irnc irnc commented Aug 11, 2015

This is not the best solution for a problem, mocha should not know anything about Bootstrap.

Proposed change would result in less conflicts. However it is made just to get the ball rolling.

In order to prevent such conflicts from happening, it is a good idea to avoid nesting in mochas CSS, e.g. by adapting BEM naming convention (see https://css-tricks.com/bem-101/).

Giving mocha elements classes named mocha-stats-progress will eliminate conflicts with other libraries entirely.

@dasilvacontin
Copy link
Contributor

LGTM. Yeah, we should really better scope those stylings, thanks for pointing it out.

@danielstjules
Copy link
Contributor

Giving mocha elements classes named mocha-stats-progress will eliminate conflicts with other libraries entirely.

Might be worth adopting BEM then? Rather than applying small fixes to individual selectors.

@Turbo87
Copy link
Contributor

Turbo87 commented Feb 9, 2016

any news on this? I just ran into the exact same problem...

@danielstjules
Copy link
Contributor

Will merge for now, but eventually all mocha CSS should just adopt BEM or a similar convention to avoid these issues.

danielstjules added a commit that referenced this pull request Feb 17, 2016
Set safe CSS for progress indicator which does not conflict with Bootstrap
@danielstjules danielstjules merged commit 0543798 into mochajs:master Feb 17, 2016
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.

4 participants