Tags: dolboBobo/amphtml
Tags
Upgrade DOMPurify to 2.0.7 (ampproject#25552) * Upgrade DOMPurify and refactor protocol sanitization. * Fix null attrValue case. * Allow safe uses of 'javascript:' etc. * Add tests to test-sanitizer.js too. * Fix presubmit.
Check if any remeasures are necessary when nested scrollers scroll (a… …mpproject#25479) Fixes ampproject#24929 (comment)
Revert "🐛Expose amp-form response from SSR in `submit-success` and `s… …ubmit-error` events. (ampproject#25242)" (ampproject#25470) This reverts commit 48d5ffd.
Narrow down script matching to avoid incorrect prefix matches (amppro… …ject#25441) * Narrow down script matching to avoid incorrect preffix matches * minor * Fix race condition on wait->reload * update script existence
Introduce AMP Live List Cache Busting (ampproject#25295) * Use a random number as a URL parameter for live list refreshes * JsonObject casting required * Is a dict * Add amp-live-list-random origin trial to gate adding a random identifier to each update of the live list * Changes based on PR feedback * Gu 8000 ard origin trial check in tri-state boolean * Add dep-check allowance * moved dep-check to correct segment * Only check for origin trial if the list is enabled
Fix visibility manager resolution in shadow doc mode (ampproject#25357) * Fix visibility manager resolution in shadow doc mode * lints
🐛 Upgrade shadow root contents when defining new CEs (ampproject#25337) * Upgrade shadow root contents when defining new CEs When we've already initialized the the custom element registry, it used to drop the list of shadow roots. When a new CE was defined, we would then only query the host `document` (since we dropped all the shadow roots from the array). Obviously, that query selector won't find CEs inside the shadow tree. So, we need to keep the list of shadow roots, that way we can query inside them when defining new custom elements. Note, this will mean leaking every shadow permenantly. Even if the shadow's host is removed from the document, we'll still have to keep its reference. We could setup a long running interval to find disconnected trees, but it wouldn't be able to tell the difference between a temporarily disconneded shadow and a destoyed shadow. * Fix comment * Remove unused private
🐛 Upgrade shadow root contents when defining new CEs (ampproject#25337) * Upgrade shadow root contents when defining new CEs When we've already initialized the the custom element registry, it used to drop the list of shadow roots. When a new CE was defined, we would then only query the host `document` (since we dropped all the shadow roots from the array). Obviously, that query selector won't find CEs inside the shadow tree. So, we need to keep the list of shadow roots, that way we can query inside them when defining new custom elements. Note, this will mean leaking every shadow permenantly. Even if the shadow's host is removed from the document, we'll still have to keep its reference. We could setup a long running interval to find disconnected trees, but it wouldn't be able to tell the difference between a temporarily disconneded shadow and a destoyed shadow. * Fix comment * Remove unused private
Use @example.com for email spec example (ampproject#25055)
Fix Custom Element instance creation in IE11 (ampproject#25245) When we transpile `super` in Custom Element subclasses, we change it to `superClass.call(this)` (where `superClass` is `HTMLElementPolyfill`). That `.call` value is inherited from `Function.prototype`. But, IE11's native HTMLElement hierarchy doesn't extend from Function! And because `HTMLElementPolyfill` extends from `HTMLElement`, it doesn't have a `.call`! So we need to manually install it.
PreviousNext