test: permit multiple <h1> tags in a document - #4741
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## main #4741 +/- ##
==========================================
- Coverage 88.51% 88.50% -0.01%
==========================================
Files 296 296
Lines 39840 39845 +5
==========================================
+ Hits 35263 35266 +3
- Misses 4577 4579 +2
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
larseggert
approved these changes
Nov 10, 2022
rjsparks
approved these changes
Nov 10, 2022
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Eliminates the failure here: https://github.com/ietf-tools/datatracker/actions/runs/3421760702/jobs/5700738094
The prohibition on multiple h1 tags is not needed - it was mostly an SEO concern and is outdated by HTML5. The code setting off the validation failure there is not new but was newly exercised by the test case added in PR #4734.