Skip to content

[Story] Developer can style content types output differently per viewport #621

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

Merged
merged 216 commits into from
Oct 22, 2020

Conversation

omiroshnichenko
Copy link
Contributor

@omiroshnichenko omiroshnichenko commented Aug 27, 2020

…n full-screen mode only

Description (*)

Added changes for overlay, when PageBuilder field is disabled.

Story

  • 558 Developer can style content types output differently per viewport

Related Pull Requests

magento/magento2#30565
https://github.com/magento/partners-magento2ee/pull/387
https://github.com/magento/magento2-page-builder-ee/pull/171

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)

Test Plan

TBD

- replace ko-style binding for preview.html with pbStyles
- override ko-style for master format rendering in iframe
- convert styles block for saved content to inline styles for correct master format parsing
- add csso library
@omiroshnichenko omiroshnichenko added the 2.4-develop: exclude 2.4-develop: exclude label Aug 27, 2020
@omiroshnichenko
Copy link
Contributor Author

@magento run all tests

bluemwhitew and others added 4 commits August 27, 2020 19:04
- Adding `removeAttribute()` Method
- Adding Converter to Remove `style` Attribute(s) from Page Builder
- add stage to bindingContext
- extend style binding
- revert pbStyle to ko-style
@omiroshnichenko
Copy link
Contributor Author

@magento run Functional Tests EE

- replace class with attribute
- add minified library
- fix style adding in preview style binding
@omiroshnichenko
Copy link
Contributor Author

@magento run Functional Tests EE

bluemwhitew and others added 3 commits September 9, 2020 15:25
- Refactoring Using DOMDocument
- Adding `generateDataAttribute` Method
- Adding `generateInternalStyles` Method
- Modifying Ordering of Expected vs. Actual in PageBuilderStripStylesTest
- add id to body
- make generated styles selectors more specific with body id
@omiroshnichenko
Copy link
Contributor Author

@magento run Functional Tests EE

hannahnida and others added 4 commits September 10, 2020 12:14
…rt - Removed inline styles from column group
#7 - Added ValidateContentTypeStyles action group
#7 - Added ValidateContentTypeStyles action group
#7 - Added ValidateContentTypeStyles action group
@omiroshnichenko omiroshnichenko changed the title [WIP] Implement inline styles conversion [WIP] [Story] Developer can style content types output differently per viewport Sep 10, 2020
bluemwhitew and others added 3 commits September 10, 2020 18:38
- Amending Integration Tests
- Preparing to Utilise DOMDocument for Testing
…eBuilderCatalogProductAddAndEditRowColumnSlideTest test
Hanna Hnida and others added 2 commits October 16, 2020 15:13
@omiroshnichenko
Copy link
Contributor Author

@magento run all tests

- Extending MFTF Tests for CSS Specificity
- Extending MFTF Tests for CSS Responsive Styling
- Removing Heading Type in CSS Specificity
 - remove redundant layout
 - revert column-group styles back
@omiroshnichenko omiroshnichenko changed the title [WIP] [Story] Developer can style content types output differently per viewport [Story] Developer can style content types output differently per viewport Oct 20, 2020
@omiroshnichenko
Copy link
Contributor Author

@magento import pull request to magento-obsessive-owls/magento2-page-builder

@magento-engcom-team
Copy link
Contributor

@omiroshnichenko the pull request successfully imported.

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