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

[WIP] #558 #7 Developer can style content types output differently per viewport - fix broken tests #627

Closed

Conversation

lbvaimo
Copy link

@lbvaimo lbvaimo commented Sep 11, 2020

Story

As a developer I want to easily create themes and customizations to existing Page Builder content types to enable me align their visual output with my desired theme

Business Value

ability to style content with CSS classes not using !important

Acceptance Criteria

  • Developers are no longer required to use !important to style CSS properties

Technical Vision

  • Remove the usage of style attributes
  • Utilize style block generation and include a single block per instance
  • Consider including an optimizer to further decrease the size of the payload: https://github.com/css/csso

Story

#558

Related Pull Requests

https://github.com/magento/magento2-page-builder-ee/pull/173

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)

Lukasz Borowiec added 4 commits September 10, 2020 15:17
#7 - Added ValidateContentTypeStyles action group
#7 - Added ValidateContentTypeStyles action group
#7 - Added ValidateContentTypeStyles action group
…eBuilderCatalogProductAddAndEditRowColumnSlideTest test
@lbvaimo lbvaimo changed the base branch from develop to csso-alternative September 11, 2020 11:50
@lbvaimo lbvaimo changed the title 558 7 content type style attribute removal [Story] Developer can style content types output differently per viewport #7 fix broken tests Sep 11, 2020
@lbvaimo lbvaimo linked an issue Sep 11, 2020 that may be closed by this pull request
7 tasks
@lbvaimo lbvaimo changed the title [Story] Developer can style content types output differently per viewport #7 fix broken tests #558 Developer can style content types output differently per viewport #7 fix broken tests Sep 11, 2020
@lbvaimo lbvaimo changed the title #558 Developer can style content types output differently per viewport #7 fix broken tests #558 [Story] #7 Developer can style content types output differently per viewport - fix broken tests Sep 11, 2020
@lbvaimo lbvaimo changed the title #558 [Story] #7 Developer can style content types output differently per viewport - fix broken tests [WIP] #558 #7 Developer can style content types output differently per viewport - fix broken tests Sep 11, 2020
@m2-community-project
Copy link

@lbvaimo unfortunately, only members of the maintainers team are allowed to assign developers to the pull request

@m2-community-project
Copy link

@lbvaimo unfortunately, only members of the maintainers team are allowed to assign developers to the pull request

1 similar comment
@m2-community-project
Copy link

@lbvaimo unfortunately, only members of the maintainers team are allowed to assign developers to the pull request

dhaecker and others added 7 commits October 5, 2020 12:07
…onents are always nested in a Contained component

 - Fixing MFTF CR feedback
…onents are always nested in a Contained component

 - Fixing filename
…lder into imported-magento-magento2-page-builder-631
…gento2-page-builder-631

[Imported] MC-35402: [Page Builder] New top-level Full-Width and Full-Bleed comp�
…ew groups, changed name in Pascal caps format
@petrovsa
Copy link
Contributor

petrovsa commented Oct 8, 2020

@magento run Functional Tests EE

@petrovsa
Copy link
Contributor

petrovsa commented Oct 8, 2020

@magento run Functional Tests EE

1 similar comment
@petrovsa
Copy link
Contributor

petrovsa commented Oct 9, 2020

@magento run Functional Tests EE

 - fixed bugs in test generation and changed all references on groups
@hannahnida
Copy link
Contributor

@magento run Functional Tests EE

1 similar comment
@petrovsa
Copy link
Contributor

@magento run Functional Tests EE

 - I changed references in PB-EE in PR 173
 - I made refactoring follow groups:
 ValidateAdvancedConfigurationWithAlignmentActionGroup
 ValidateAdvancedConfigurationWithBorderColorActionGroup
 ValidateAdvancedConfigurationWithCssClassesActionGroup
 ValidateAdvancedConfigurationWithNoAlignmentActionGroup
 ValidateAdvancedConfigurationWithNoAlignmentEmptyBorderRadiusActionGroup
 ValidateAdvancedConfigurationWithNoBorderActionGroup
 ValidateAdvancedConfigurationWithNoBorderRadiusActionGroup
@petrovsa
Copy link
Contributor

@magento run Functional Tests EE

…magento2-page-builder into 558_7_content-type-style-attribute-removal
@hannahnida
Copy link
Contributor

@magento run Functional Tests EE

hannahnida and others added 3 commits October 12, 2020 17:45
 - I made refactoring follow groups:
 ValidateAdvancedConfigurationWithNoBorderWidthActionGroup
 ValidateAdvancedConfigurationWithNoMarginsActionGroup
 ValidateAdvancedConfigurationWithNoPaddingActionGroup
…te-removal' into 558_7_content-type-style-attribute-removal
@petrovsa
Copy link
Contributor

@magento run Functional Tests EE

 - I made refactoring follow groups:
 ValidateAdvancedConfigurationWithNoMarginsActionGroup
 ValidateBackgroundConfigurationWithNoImageActionGroup
@petrovsa
Copy link
Contributor

@magento run Functional Tests EE

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

Successfully merging this pull request may close these issues.

Developer can style content types output differently per viewport
8 participants