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
[AMP Stories] Make sure that the frontend and editor view match #1967
Comments
See also discussion about how we should include styles on the frontend: #1958 (comment) |
Note that this also affects the reordering UI. |
I'm wondering what would be the best approach for font sizes -- for example if the default font size is 16px in the editor and is displayed in two rows then the same font size in the frontend might still be in one row -- since the font size is not responsive. We could add some different sizes based on the screen width for the default font sizes, however, what if the user selects a specific font size? @swissspidy @westonruter Thoughts? |
@miina What if the specific font sizes were stored in |
@westonruter: Just updated the PR to use |
Closed within #2015. |
verified in QA |
AC: All the allowed blocks in the editor look visually the same (or very similar) to how they look like in the frontend. This does not include animations.
The text was updated successfully, but these errors were encountered: