You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After #5 and #7 were merged, I’m now thinking about the best way to style the line highlighter to make it render how it used to with full width background colors.
Previous behavior on eleventy-base-blog:
New behavior:
This is what it renders like without CSS (this is showing default styles for ins/del/mark, which are okay). I’ve added a few newlines in there just to see how #5 would look too (those were not in the previous behavior screenshot):
This is what it looks like on eleventy-base-blog after removing the ins/del/mark styles:
The display: block Problem:
When using .highlight-line { display: block; } to get full width highlights, the problem exhibits itself:
If I move the <br> inside of the highlight-line elements, I get what I want with display: block;
Would it be better to move the <br>? Or to use CSS to hide the <br> altogether when using display: block;
The text was updated successfully, but these errors were encountered:
After #5 and #7 were merged, I’m now thinking about the best way to style the line highlighter to make it render how it used to with full width background colors.
Previous behavior on eleventy-base-blog:
New behavior:
This is what it renders like without CSS (this is showing default styles for ins/del/mark, which are okay). I’ve added a few newlines in there just to see how #5 would look too (those were not in the previous behavior screenshot):
This is what it looks like on
eleventy-base-blog
after removing the ins/del/mark styles:The
display: block
Problem:When using
.highlight-line { display: block; }
to get full width highlights, the problem exhibits itself:If I move the
<br>
inside of thehighlight-line
elements, I get what I want withdisplay: block;
Would it be better to move the
<br>
? Or to use CSS to hide the<br>
altogether when usingdisplay: block;
The text was updated successfully, but these errors were encountered: