-
Notifications
You must be signed in to change notification settings - Fork 349
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
Vertical Alignment not removed #391
Comments
Please review the |
Correct. The reason why it allows all styles right now is that you have
font listed for "allowedAttributes" (correct and required for this) but you
don't have it listed in "allowedStyles" (you are missing a level, see the
docs as was mentioned).
…On Wed, Jul 29, 2020 at 3:27 PM Alex Bea ***@***.***> wrote:
Closed #391 <#391>.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#391 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAH27NUTDWOPUHQPKNJHGDR6BZZHANCNFSM4PLW4PBQ>
.
--
THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER
APOSTROPHECMS | apostrophecms.com | he/him/his
|
I want vertical-alignment to be gone in the style attribute on font. So it not being there in 'allowedStyles' should remove it. That's how I read the docs as well. (see expected output) |
I got it working by adding this:
|
PLEASE NOTE: make sure the bug exists in the latest patch level of the project. For instance, if you are running a 2.x version of Apostrophe, you should use the latest in that major version to confirm the bug.
To Reproduce
Step by step instructions to reproduce the behavior:
Expected behavior
Describe the bug
Details
Version of Node.js:
PLEASE NOTE: Only stable LTS versions (10.x and 12.x) are fully supported but we will do our best with newer versions.
~/code/testing-sanitize » node -v
v10.8.0
Server Operating System:
MacOS Version 10.15.4
Additional context:
I created this code snippet to extract the problem from the bigger service.
Screenshots
Terminal issue:
The text was updated successfully, but these errors were encountered: