pelican-theme: Strip tags from <title> element - #271
Open
cjwatson wants to merge 2 commits into
Open
Conversation
A reader of my blog reported a rendering bug (https://mastodon.social/@sil/117146095868899305), which looks similar to getpelican/pelican#1930. The Pelican maintainers said that this was a theme issue, so I think the `m.css` theme should be tweaked to handle this properly.
cjwatson
force-pushed
the
title-striptags
branch
from
August 23, 2026 18:34
ec9b733 to
578b3f5
Compare
Author
|
I don't think the remaining CI issues are my fault. I fixed the JS failure as a drive-by, but I don't really know where to start with the weird |
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
1 participant
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.
A reader of my blog reported a rendering bug
(https://mastodon.social/@sil/117146095868899305), which looks similar to getpelican/pelican#1930. The Pelican maintainers said that this was a theme issue, so I think the
m.csstheme should be tweaked to handle this properly.