I'd appreciate if you send a correction to the original tweet. Need to unit test my comments, so they stay accurate :)
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 -
-
-
yes, lots of thought on JS. No certification for publishers. You just publish and say: I am AMP
-
I'd be very interested in working on ways to expand the scope of acceptable JS so general purpose Ember apps could work.
End of conversation
New conversation -
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.