well, it is also done for generic iframe, so I guess that comment is just wronghttps://github.com/ampproject/amphtml/blob/master/extensions/amp-iframe/0.1/amp-iframe.js#L136 …
maybe that isn't how it works in practice. How does a new publisher get "amp certified"?
-
-
also, has there been any thought about a subset of JS APIs that could run in an AMP context?
-
I designed DOMChangeList to be a reasonable fit for AMP-like contexts that want to restrict all JS on the UI thread.
-
maybe allowing blanket workers is acceptable?
-
@Medium cool! You should like DOMChangeList then. https://github.com/whatwg/dom/issues/270 … maybe an AMP polyfill can move us forward. -
@github the only two APIs that need this kind of treatment from AMP are DOM APIs and event handlers -
for event handlers, passing the event async to a worker and redispatching if not cancelled is probably enough.
-
but other than those two, Glimmer-based Ember is a good fit for OMT rendering and SSR for initial render.
End of conversation
New conversation -
-
-
#thanks for sharing about publisher, have a great Sunday :) (Want this? It's FREE! https://bit.ly/thankyou69 )Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.