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
We had an issue that APE didn't detect where a page was valid HTML but had no content. Specifically, it had an empty (whitespace only) <main> tag. It may be useful to have an optional warning when certain tags have no content, if that is highly unlikely to be what the user intended.
There are probably other tags that are unlikely to have no content, like <body> and <nav>. But also smaller-scope tags: for example <b></b> is also suspect. Maybe it's even safe to say that most non-void elements that are empty are suspect? Although that runs the risk of false positives when an element is going to be populated by JavaScript.
The trade-off between false positives and false negatives could be handled by making this feature configurable, so the user can include and/or exclude tags.
I think this should be implemented as a plugin, since it's not a core feature.
The text was updated successfully, but these errors were encountered:
We had an issue that APE didn't detect where a page was valid HTML but had no content. Specifically, it had an empty (whitespace only)
<main>
tag. It may be useful to have an optional warning when certain tags have no content, if that is highly unlikely to be what the user intended.There are probably other tags that are unlikely to have no content, like
<body>
and<nav>
. But also smaller-scope tags: for example<b></b>
is also suspect. Maybe it's even safe to say that most non-void elements that are empty are suspect? Although that runs the risk of false positives when an element is going to be populated by JavaScript.The trade-off between false positives and false negatives could be handled by making this feature configurable, so the user can include and/or exclude tags.
I think this should be implemented as a plugin, since it's not a core feature.
The text was updated successfully, but these errors were encountered: