Correctly handle siblings_disallowed from spec#7597
Conversation
|
Plugin builds for 7fca058 are ready 🛎️!
|
|
No idea why those The Bento tests and the ones for Any help appreciated. |
|
@swissspidy I think failing tests can be the result of the removal of bento extension from allowed tags. When the expected string is bento optimized (or bento component markup) but bento is not actually present in the allowed tags and attributes, the results of a few tests may differ. We can re-generate |
|
Hmm I guess, but that's tricky unless I do it manually, because Maybe now's simply the time to remove Bento here? |
Yes, that should be done. However, that would probably add too much scope to this PR. How about reverting the changes to Bento in Then we can update the spec generator and remove Bento in another PR. |
Co-authored-by: Weston Ruter <[email protected]>
Co-authored-by: Weston Ruter <[email protected]>
Co-authored-by: Weston Ruter <[email protected]>
Summary
Elements like
<amp-story>usesiblings_disallowed: trueto ensure they don't have any sibling elements.https://github.com/ampproject/amphtml/blob/db9d5dbd9a1b5e21eba496e791829308dbb19c7e/extensions/amp-story/validator-amp-story.protoascii#L104
Due to a bug report for the Web Stories plugin we noticed that the existing sanitizers were not removing any disallowed siblings of
<amp-story>Turns out, this information was not being used at all in
bin/amphtml-update.pyandAMP_Tag_And_Attribute_Sanitizer.This PR is an attempt at fixing that.
I had to tweak the Python script a bit to get the generation working again, as Bento has now been removed and also
amp-redbull-playerwas deprecated.Checklist