…r-page

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.'

Close #807

…ll posts and pages.

…lytics changes

…draft and previews)

* Use query var in permalinks containing query vars, instead of endpoint slug.
* Remove needless and unslightly 1 value.
* Add tests.

…ping to true

Add admin screen for managing which post types have AMP support

…eature/709-block-amp-per-page

…t skipped.

* Restore focus on edit link for AMP status edit for accessibility.
* Do not add AMP preview button if AMP has been disabled.
* Change postmeta to be flag indicating whether AMP is disabled.
* Fix spelling and clean up phpdoc.

…MP_Post_Template for sake of preview

…een reader text

…ned before use

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.

…nslatable tooltip strings.

… control UI.

Add post preview for AMP and allow AMP to be disabled on a per-post basis

…draft and previews)

* Use query var in permalinks containing query vars, instead of endpoint slug.
* Remove needless and unslightly 1 value.
* Add tests.

…rotected or skipped

… (for now)

…template parts

….php

…_load_classes() and amp_load_fasterimage_classes(), created /include/templates/ directory for template-related classes, and Options Manager out of the views subdirectory.

…) does not accept a 2nd parameter.

…availability.

…enable AMP toggle if users selects mobile device.

…pport_errors()

…ability are exhausted

Add page support

…hin Customizer.

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.

* Include more Customizer preview logic from manager in AMP preview
* Ensure scripts and styles are enqueued when preview opened for controls app; this ensures AMP validation can pass when using frontend preview link.
* Restore previous add_preview_scripts method.
* Include more logic behind
* Add PHP doc.
* Improve WPCS adherence.
* Skip outputting Customizer preview JS if user cannot customize.
* Use wp_print_footer_scripts()` instead of doing wp_footer.

Fix obsolete method references and improve placement of add_action() calls

… prevent fallback refreshes