-
Notifications
You must be signed in to change notification settings - Fork 27k
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
Drop user <script> tags #6688
Comments
Ideally this would be detected at compile time. |
I think we need a tag to determine if the page is an AMP page, so we can build both AMP and normal pages in one app. |
timneutkens
pushed a commit
that referenced
this issue
Mar 29, 2019
Drops user `<script>` tags and shows a warning in AMP mode. Right now they are only dropped in production mode and left in dev mode so the validator shows its warning since it looks like conflicting props log messages are being cleared causing them to not show. Closes: #6688
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When the user includes a custom
<script>
tag on an Amp page, we should remove it before streaming the response to the client.This should probably happen before we run Amp validation because we can give a better error to the user about what's going on. We can swap these orders in the future.
This will ensure users don't see behaviors which shouldn't be possible.
The text was updated successfully, but these errors were encountered: