-
Notifications
You must be signed in to change notification settings - Fork 383
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.6 Release to master #896
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.'
…ll posts and pages.
Remove workaround that was fixed in WordPress 4.4
…ort may be enabled later
Improved page default status logic and add overwrite ability; ensure front page and page for posts can be served as AMP when enabled
…-tag Remove erroneous additional allowance of script[type=text/javascript]
As Weston mentioned, adding this to the post content: Hello <script>document.write('world');</script> Produced: This looks to be related to how process_node() gets the $attr_spec_list. In some cases, all will have an equal 'score,' As indicated in $spec_ids_sorted. And sometimes, all of them will be missing a mandatory attribute. In that case, $attr_spec_list will be empty. If it is, use the first spec list in: $rule_spec_list_to_validate. This will need regression testing.
There was an error on the Travis build: Can't use function return value in write context. So store the result of reset() in $first_spec_list.
This has a mandatory attribute. And per the previous commits, It should fail validation.
Address an issue where <script> tags aren't stripped.
westonruter
approved these changes
Jan 24, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.