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

Issue #2320 - Adds wc-Comment-content-nsfw to new CSS #2648

Merged
merged 3 commits into from
Oct 16, 2018

Conversation

marimeireles
Copy link
Member

@marimeireles marimeireles commented Oct 10, 2018

This PR fixes issue #2320

It's necessary to add a nsfw label to the github repository in order for these changes to work.

r? @magsout


@magsout
Copy link
Member

magsout commented Oct 11, 2018

@marimeireles thanks. The logic of nsfw is back.

In the issue #2320 there are two purposes.

  1. Logic back
  2. Consistency in naming

You did the first step, but no the second step.

So you have to update the className in the css file and the js file to be consistency with the classNames

@miketaylr
Copy link
Member

consistency with the classNames

Is the style we should be using documented somewhere @magsout? I'm not sure I even know. :))

@magsout
Copy link
Member

magsout commented Oct 11, 2018

Is the style we should be using documented somewhere @magsout? I'm not sure I even know. :))

Good question @miketaylr and I would say, no.

It's just about feeling of what kind of component you're coding and/or where you're adding properties.

It's very subjective so I think it would be nice to document that.

For this issue, I would say something like : .issue-details-nsfw ?

@marimeireles
Copy link
Member Author

@miketaylr Thanks for the question.
@magsout Sorry for that. When you said I should adapt it to css atomic I read a little bit about it on the internet and I thought I was fine.

I followed your recommendation in this new pr.

@magsout
Copy link
Member

magsout commented Oct 12, 2018

@marimeireles

@magsout Sorry for that. When you said I should adapt it to css atomic I read a little bit about it on the internet and I thought I was fine.

My bad, I should have been more specific.

Perfect for the css part 👍 good job.

Just one thing and after that i think we can merge, we need to update className in JS files :

.addClass("wc-Comment-content-nsfw");

"click .wc-Comment-content-nsfw": "toggleNSFW"

.addClass("wc-Comment-content-nsfw");

then same thing for all className wc-Comment-content-nsfw" in the functional test

assert.include(className, "wc-Comment-content-nsfw");

assert.include(className, "wc-Comment-content-nsfw");

assert.notInclude(className, "wc-Comment-content-nsfw--display");

assert.include(className, "wc-Comment-content-nsfw");

assert.include(className, "wc-Comment-content-nsfw--display");

assert.include(className, "wc-Comment-content-nsfw");

assert.notInclude(className, "wc-Comment-content-nsfw--display");

@karlcow karlcow requested a review from magsout October 14, 2018 22:40
@marimeireles
Copy link
Member Author

Sorry for taking so long and forgetting to change on the other files! :(

@magsout magsout merged commit 82aa32a into webcompat:master Oct 16, 2018
@magsout
Copy link
Member

magsout commented Oct 16, 2018

@marimeireles awesome. Good job, and thanks a lot.

capture d ecran 2018-10-16 a 16 15 40

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