Normalize h1 text to permit leading, trailing, and wrapping whitespace
#4831
Conversation
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
The build system already supports wrapping whitespace in the level-1 heading of techniques. However, as you point out, it is not handling leading/trailing whitespace correctly. If you look a few lines later than where you adjusted, This PR, as written, ends up undoing the functionality that I pointed out lower in the file. I have created #4846 to fix this without regressions. |
|
Got it — thanks for the explanation and follow-up PR, @kfranqueiro. 🙏🏻 |
This fixes the issue reported in #4831 while avoiding regressions to existing link text truncation logic. (This does cause some whitespace changes in output, but they are not noticeable in the rendered HTML.)
3 participants
While developing #4829, I discovered that my
h1text for the new page wasn’t successfully retrieved by the build system because I’d hard-wrapped the lines like so:@kfranqueiro, would it be alright to tweak the build system to permit wrapped heading text like this?