-
Notifications
You must be signed in to change notification settings - Fork 64
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 #558
Closed
7 tasks done
Comments
Hi @tkacheva. Thank you for your report. Please, add a comment to assign the issue:
|
Sub-tasks:
|
m2-community-project
bot
added
Progress: ready for grooming
and removed
Progress: ready for dev
labels
Aug 7, 2020
m2-community-project
bot
added
Progress: dev in progress
and removed
Progress: ready for grooming
labels
Aug 25, 2020
bluemwhitew
added a commit
that referenced
this issue
Aug 27, 2020
- Adding `removeAttribute()` Method
bluemwhitew
added a commit
that referenced
this issue
Aug 27, 2020
- Adding Converter to Remove `style` Attribute(s) from Page Builder
hannahnida
added a commit
that referenced
this issue
Sep 8, 2020
…rt - Added styles fixes for adminhtml area
4 tasks
m2-community-project
bot
added
Progress: PR created
and removed
Progress: dev in progress
labels
Sep 8, 2020
4 tasks
bluemwhitew
added a commit
that referenced
this issue
Sep 9, 2020
- Refactoring Using DOMDocument - Adding `generateDataAttribute` Method - Adding `generateInternalStyles` Method - Modifying Ordering of Expected vs. Actual in PageBuilderStripStylesTest
hannahnida
added a commit
to hannahnida/magento2
that referenced
this issue
Oct 20, 2020
…output differently per viewport - Added body id in Storefront, in tinymce4 in admin
Merged
4 tasks
hannahnida
added a commit
to hannahnida/magento2
that referenced
this issue
Oct 20, 2020
…output differently per viewport - Fixed quote marks
Merged
5 tasks
hannahnida
added a commit
to hannahnida/magento2
that referenced
this issue
Oct 20, 2020
…output differently per viewport - Fixed tinymce image selector
hannahnida
added a commit
to hannahnida/magento2
that referenced
this issue
Oct 20, 2020
…output differently per viewport - Fixed tinymce image selector
hannahnida
added a commit
to hannahnida/magento2
that referenced
this issue
Oct 20, 2020
…t types output differently per viewport - Fixed tinymce image selector" This reverts commit 754eb5a.
omiroshnichenko
added a commit
that referenced
this issue
Oct 20, 2020
- remove redundant layout - revert column-group styles back
omiroshnichenko
added a commit
that referenced
this issue
Oct 20, 2020
- remove redundant layout - revert column-group styles back
m2-community-project
bot
added
Progress: dev in progress
and removed
Progress: done
labels
Oct 28, 2020
dpatil-magento
added a commit
to magento/pwa-studio
that referenced
this issue
Nov 2, 2020
) * magento/magento2-page-builder#558: Developer can style content types output differently per viewport - convert style blocks to inline styles to prevent BIC changes * magento/magento2-page-builder#558: Developer can style content types output differently per viewport - fix code style Co-authored-by: Devagouda <40405790+dpatil-magento@users.noreply.github.com>
m2-community-project
bot
added
Progress: done
and removed
Progress: dev in progress
labels
Nov 2, 2020
This was referenced Dec 7, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Technical Vision
Test Plan
Manual Testing Scenarios
develop
branch of Page Buildercsso-alternative
branch of Page Builderbin/magento setup:upgrade
and re-deployUpdate working as expected.
No visual differences, and no inline styles after conversion to
csso-alternative
branch.Page:
https://588-manual-tests-dg3iscy-vzsrtettsztvg.us-4.magentosite.cloud/issue-558
Ghost Inspector:
https://ghostinspector-prod.s3.amazonaws.com/screenshots/bdf4afb7-bf2b-40f7-81d3-2c74cfa143a3-compareOriginal.png
Create a new Page (Content » Pages » Add New Page)
Click Edit with Page Builder
Add Heading and HTML Code content types, and configure with the following:
Click Save
Browse to your newly created CMS Page
Confirm Heading ("CSS Specificity") is aligned to the left
Edit the Page created in Step 1.
Click Edit with Page Builder
Replace HTML Code contents with:
Click Save
Browse to your newly created CMS Page again
Confirm Heading ("CSS Specificity") is aligned to the center
Page:
https://588-manual-tests-dg3iscy-vzsrtettsztvg.us-4.magentosite.cloud/css-specificity
Create a new Page (Content » Pages » Add New Page)
Click Edit with Page Builder
Add Heading and HTML Code content types, and configure with the following:
Click Save
Browse to your newly created CMS Page
Confirm Heading ("CSS Responsive Styling") is:
#00aaff
Confirm that Heading ("CSS Responsive Styling") has been appended with a viewport indicator:
#ffaa00
Resize the browser window below (or use device emulation to achieve the same result)
Confirm that Heading ("CSS Responsive Styling") appended viewport indicator changes according to the viewport size
Page:
https://588-manual-tests-dg3iscy-vzsrtettsztvg.us-4.magentosite.cloud/css-responsive-styling
Install Page Builder Examples
Create a new Page (Content » Pages » Add New Page)
Click Edit with Page Builder
Add Heading and HTML Code content types, and configure with the following:
Click Save
Browse to your newly created CMS Page
Confirm Quote appears centred, converted styles (to internal CSS)
Create a new Page (Content » Pages » Add New Page)
Click Edit with Page Builder
Add Heading and HTML Code content types, and configure with the following:
00aaff
Click Save
Browse to your newly created CMS Page within PWA Studio
Confirm Heading appears centred, and contains inline styles (not internal CSS)
Copy database field from Migration of Existing Page Builder Content Manual Test and verify each content type in Venia
Before:
After:
Automated MFTF Tests
N/A
Note: This list doesn't include modifications to existing Data, Action Groups, or Sections.
Manual Hip Tests
N/A
The text was updated successfully, but these errors were encountered: