Open
Conversation
|
There is no change log for this pull request yet. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I noticed that
<u>(underline) and<cite>(citation style) tags were not rendering correctly in Pug'sprettymode: I was getting extra spaces around them. Example:Expected:
Actual:
This results in a space between "two" and "three" text, which is inconsistent compared to the lack of space before
<span>.This PR adds the inline elements from MDN's list, in particular fixing the issue with
<u>.I was surprised by some items on this list, such as
<iframe>,<canvas>and<script>. I left<script>out as this should rarely cause rendering issues (<script>ought to be in<head>anyway...), but included the others as their layout could be affected by adjacent spaces. I'm open to tweaking this list.Because the list got substantially longer, I also replaced the
Array.indexOfcheck with anObject.hasOwnPropertycheck, which should be faster (though I did not test this).As another example, consider these two versions of a form (taken from one of the tests):
They render very differently:
There are ways for Pug to add spaces, but no ways to remove them in these settings, so I believe the latter behavior is far superior (it's also how things would render without
prettymode).