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

Developer can style content types output differently per viewport - Subtask 5 #626

Closed

Conversation

hannahnida
Copy link
Contributor

Description (*)

Changed css selectors in less files to be less specific (adminhtml)

Story

  • 558 Developer can style content types output differently per viewport - Subtask 5: Change css selectors in less files to be less specific (adminhtml)

Builds

Related Pull Requests

Manual testing scenarios (*)

  1. ...
  2. ...

Questions or comments

Checklist

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)

@hannahnida hannahnida linked an issue Sep 8, 2020 that may be closed by this pull request
7 tasks
@hannahnida hannahnida added the 2.4-develop: exclude 2.4-develop: exclude label Sep 8, 2020
@hannahnida
Copy link
Contributor Author

@magento run all tests

@hannahnida
Copy link
Contributor Author

@magento run Static Tests

@hannahnida hannahnida changed the title [WIP] Developer can style content types output differently per viewport - Subtask 5 Developer can style content types output differently per viewport - Subtask 5 Sep 9, 2020
@hannahnida
Copy link
Contributor Author

Closing PR - changes no longer needed.

@hannahnida hannahnida closed this Sep 10, 2020
@omiroshnichenko omiroshnichenko deleted the 558_5_content-type-style-attribute-removal branch December 7, 2020 18:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Developer can style content types output differently per viewport
1 participant