Skip to content

Commit

Permalink
Merge pull request ampproject#225 from powdercloud/patch-2
Browse files Browse the repository at this point in the history
couple more <a name= ids and fixing one style amp-custom.
  • Loading branch information
cramforce committed Sep 19, 2015
2 parents f65cfcb + 08b3a6b commit bfa007b
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions spec/amp-html-format.md
Original file line number Diff line number Diff line change
Expand Up @@ -143,10 +143,10 @@ Most HTML tags can be used unchanged in AMP HTML. Certain tags, however, have eq
| embed | Banned. |
| form | Banned. |
| input elements | Banned. Includes input, button, textarea, select, option. |
| style | [Required style tags for adjusting opacity](#opacity) One additional style tag is allowed in head tag for the purpose of custom styling. This style tag must have the attribute `amp-custom`. |
| <a name="cust"></a>style | [Required style tags for adjusting opacity](#opacity) One additional style tag is allowed in head tag for the purpose of custom styling. This style tag must have the attribute `amp-custom`. [🔗](#cust) |
| link | Allowed for certain values of rel: `canonical`. `stylesheet` is generally disallowed, but some values may be whitelisted for font providers. |
| meta | The `http-equiv` attribute is banned. Otherwise allowed. |
| a | The `href` attribute value must not begin with `javascript:`. If set, the `target` attribute value must be `_blank`. Otherwise allowed. |
| <a name="ancr"></a>a | The `href` attribute value must not begin with `javascript:`. If set, the `target` attribute value must be `_blank`. Otherwise allowed. [🔗](#ancr) |

Validator implementations should use a whitelist based on the HTML5 specification with the above tags removed.
TODO(malteubl): Add addendum with whitelist.
Expand Down

0 comments on commit bfa007b

Please sign in to comment.