| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Hi @masonf
I have found this other bug while investigating the Adoption Algorithm issue.
It seems that WebKit's parser doesn't know about the <command> element either, so I think we could align with that.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Nice catch! I'm amazed I hadn't seen that.
As much as I hate to say it, we should probably add a runtime enabled feature for this too, since it's possible someone depends on it or something. I think the changes are small, but better safe than sorry. Otherwise, looks good to me.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Oh one more thing, you should remove `"command"` from third_party/blink/renderer/core/html/html_tag_names.json5
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Oh one more thing, you should remove `"command"` from third_party/blink/renderer/core/html/html_tag_names.json5
I'm not sure how to do this while we still admit the <command> tag when the runtime flag is disabled. The html_tag_names.json5 has a "runtimeEnabled" field, but I think it works in the opposite direction to what we want.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Javier FernandezOh one more thing, you should remove `"command"` from third_party/blink/renderer/core/html/html_tag_names.json5
I'm not sure how to do this while we still admit the <command> tag when the runtime flag is disabled. The html_tag_names.json5 has a "runtimeEnabled" field, but I think it works in the opposite direction to what we want.
Oh shoot, you're right. See my comment above - let's just add a comment to not forget.
if (GetHTMLTag() == html_names::HTMLTag::kCommand) {For speed, let's actually stick this into the `switch` below as a case.
// Early exit: reject command elements when removal is enabledditto
// This shipped in M147 and the flag can be removed in M149.sorry - now M148 and M150.
{Maybe just add a comment right here:
```
// NOTE: when this flag is removed, be sure to also remove "command"
// from third_party/blink/renderer/core/html/html_tag_names.json5.
```
status: "experimental",This can be set to `"stable"` immediately. This is just in case of problems.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Thanks for the review.
I have applied the suggested changes.
For speed, let's actually stick this into the `switch` below as a case.
Done
// Early exit: reject command elements when removal is enabledJavier Fernandezditto
Done
// This shipped in M147 and the flag can be removed in M149.sorry - now M148 and M150.
Done
Maybe just add a comment right here:
```
// NOTE: when this flag is removed, be sure to also remove "command"
// from third_party/blink/renderer/core/html/html_tag_names.json5.
```
Done
This can be set to `"stable"` immediately. This is just in case of problems.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
The <command> element should be treated as invalid in HTML parsing.
The WHATWG HTML spec removed <command> as a known element long ago. It
should be parsed as an ordinary unknown element (non-void, can have
children). We are still treating it as a void head element and a
"special" element.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |