Generate class-amp-allowed-tags-generated.php,
Using amp_wp_build.py.
Followed the instructions at the top of the file.
This is spec file revision 527.

Before, there was an error in:
tag_spec.also_requires_tag
This didn't always have the property.
Also, update the directory of the extensions.
The .protoascii file is no longer in the directory '0.1.'

Since the allowed tags and attributes are updated,
Several assertions failed.
Update them to reflect the new AMP spec.
Since there is no longer a protocol whitelist,
Remove the assertions for protocols.

This file was generated from a build script,
In the repo https://github.com/ampproject/amphtml
The spec file seems to require an empty value:
extensions/amp-ad/validator-amp-ad.protoascii
But examples of <amp-ad> seem to have the value.
Like <amp-ad data-multi-size=320x50.
@see examples/a4a-multisize.amp.html.
So remove the line in the PHP file that requires it to be empty.

Having generated a new file for the allowed tags and attributes,
Add these to the data for test_sanitizer().
Also, add unit test for is_missing_mandatory_attribute().
And rename that function from:
is_mandatory_attribute_missing().

Before, this was inside an 'else' block.
And it should be outside of this,
So it applies more broadly.
If there is a list of attributes, and one is missing,
Remove the node.
This was the previous behavior.

This was assigned a value that's used later.
There's no need to store it in a variable.

There was some missing documentation.
Add this for test_sanitizer and validate_tag_spec_for_node.

This has hundreds of errors and warnings.
It's generated from a Python script.

In response to the warnings in Travis.
And align an equal sign in test_sanitizer().

Before, there was a failed Travis build.
This used boolval(), which caused a fatal error.
Instead, simply compare the value to true.

In response to a failed Travis build.
Fix an error in an array not being aligned.
An move an = sign 2 spaces to the left.

There was an error in the Travis build.
A function accessed a DOMElement property as an array.
Instead, use the setAttribute() method.

….php

This describes how to use the new script amphtml-update.sh.
This is mainly modified from another open-source file.
It could probably use more information.
Including the workflow for submitting pull requests.

As harrisdavid mentioned, before this PR, the 'src' was mandatory.
But with the updated AMP spec, it's not.

Before, there was an issue in the file that created:
class-amp-allowed-tags-generated.php.
amphtml-update.sh had a conditional:
if isinstance(value, list)
But the allowed_protocol attribute has a type of:
google.protobuf.internal.containers.RepeatedScalarFieldContainer
So that conditional failed.
And allowed_protocol wasn't added.
So instead, make that an 'else' statement.
That change only resulted in 'allowed_tags' being added.

Add a point that this requires WP unit tests.
Also, begin with the welcome that Thierry suggested.
Props @ThierryA.

…tic/amp-wp into feature/804-allowed-tags

In phpcs.xml, retain edits from both branches.
There were several conflicts in:
class-amp-tag-and-attribute-sanitizer.php
These were mainly conflicts with 03c12.
Some were only DocBlocks, but some were logic.
I mainly resovled them in favor of this branch:
feature/804-allowed-tags.

When this has a type of 'application/json,'
There is a required ancestor.
So create an ancestor of <amp-analytics>.

In response to a failed Travis build.
Also, change == to ===.