Looking for:
Join zoom meeting with id & password reset
We apologize for the inconvenience caused. Please try again later. The amp-script component allows you to run custom JavaScript. To maintain AMP's performance guarantees, your code runs in a Web Worker, and certain restrictions apply.
Your code can access that virtual DOM as document. But amp-script gives your code access to a virtual DOM. For design details, see the "Intent to Implement" issue. DOM elements and their properties are generally supported, with a few limits.
So, document. See the code for details. Presently, the History API is not implemented, and neither are cookies. If there's an API you'd like to see supported, please file an issue or suggest and contribute the change yourself. To keep bundle sizes small, we recommend using Preact. Other frameworks may work but have not been thoroughly tested; if you're looking for support, please file an issue or contribute here.
You can use amp-script to add an amp-img or amp-layout component to the DOM. Other AMP components are presently unsupported. If you need to create a different AMP element, please upvote on and add a comment describing your use case. This lets amp-script interact with other AMP elements on the page via amp-bind bindings. If you invoke AMP. Otherwise, state will be set, but binding will not occur similar to amp-state initialization.
For more information, see the section on user gestures. This example shows how it can affect the DOM:. The promise resolves with the stringified value of the state variable it's passed. These examples demonstrate its use with different types:. Here's another example. The syncing process is unidirectional. Thus it's best to avoid code like the following:. In order to maintain AMP's guarantees of performance and layout stability, amp-script imposes some restrictions.
In some cases, amp-script will not apply DOM changes triggered by your JavaScript code unless the code was triggered by a user gesture - say, a button tap. This helps keep content layout shift from causing a poor user experience. The rules are less restrictive for amp-script containers whose size cannot change.
This is the case when the layout is not container and when the dimensions are specified in HTML. Let's call such containers "fixed-size".
Containers whose size can change, we'll call "variable-sized". Since custom JS run in amp-script is not subject to normal Content Security Policy , you need to add a script hash:. Here are a few ways to build the hash:. Similar to the iframe[sandbox] attribute, the value of the attribute can either be empty to apply all restrictions, or space-separated tokens to lift particular restrictions:. Requires the script attribute. This attribute is optional, but required for signed exchanges if script is specified.
The max-age attribute specifies the maximum lifetime in seconds the local script is allowed to be served from the time of signed exchange SXG publishing.
A longer max-age increases the potential security impact of a SXG downgrade. Note that there's currently no reason to select max-age longer than 7 days seconds , due to the maximum set by the SXG spec. If set, this will signal that worker-dom should activate sandboxed mode. In this mode the Worker lives in its own crossorigin iframe, creating a strong security boundary.
It also forces nodom mode. Because of the strong security boundary, sandboxed scripts do not need to provide a script hash. This element includes common attributes extended to AMP components. No inline script can exceed 10, bytes. See Size of JavaScript code above.
The total of all non-sandboxed scripts used by a page cannot exceed , bytes. The total of all sandboxed scripts see Sandboxed Mode used by a page cannot exceed , bytes. For local scripts and cross-origin scripts, you need to add a script hash for security.
Again, you need the script hash. To avoid undesirable content layout shift, amp-script disallows DOM mutations under certain conditions. See User gestures above. If a script attempts too many disallowed DOM changes, amp-script may halt the script so that it doesn't get too far out of sync with the DOM.
If you modify a state variable in a variable-sized container before a user interaction, amp-script will not upate the DOM to avoid undesirable content layout shift. See Referencing amp-state above. Form elements This attribute is required for security. See common attributes above. You've read this document a dozen times but it doesn't really cover all of your questions?
Maybe other people felt the same: reach out to them on Stack Overflow. The AMP project strongly encourages your participation and contributions!
We hope you'll become an ongoing participant in our open source community but we also welcome one-off contributions for the issues you're particularly passionate about. We use cookies to understand how you use our site and to improve your experience. By continuing to use our site, you accept our use of cookies and privacy policy.
We could not find any results matching your search query. Select your format for a more streamlined experience. Supported Layouts container fill fixed fixed-height flex-item intrinsic nodisplay responsive. Examples amp-render amp-script. For a set of samples showing amp-script in use, see here.
To use AMP. See here for more information about AMP's layout system. If the hash of remote. During development, you can disable the JavaScript size and script hash requirements by adding a data-ampdevmode attribute to either the amp-script element or the root html node. Adding this attribute to the root html node will suppress all validation errors on the page.
Adding it to the amp-script element will simply suppress errors about the size and the script hash. Need more help? Go to Stack Overflow. Got it!
No comments:
Post a Comment