Episode Highlights

Benefits are being able to:

  • 1) apply functions which you couldn’t previously do in AMP
  • 2) share code across amp and non-amp content for efficiency.

Restrictions

  • Content jumping: To avoid unexpected content jumping, <amp-script> generally requires user gestures to change page content.
  • Page load: Since <amp-script> doesn’t change page content without user interaction, it doesn’t modify content on page load either.
  • Script size: The script used in a single <amp-script> must be smaller than 150kB. Please note that you’re welcome to use your favorite JS framework, but it must fit within that 150K limit.

Transcript

Rick: The last article today, Juan, what’s going on in AMPs?

Juan: They are actually allowing custom JavaScript to be added to AMP pages. You can make them all pretty now. No, I’m not just kidding. The actual limit to the amount of Java you can add is about 150 kilobytes and it’s actually based on user interaction. So you’ll still get the standard AMP pages from my understanding, but to avoid any kind of unexpected changes to the user, the user end, it has to be gestured or triggered by the user in order to load the AMP scripts. But now the option is there, and it looks like the rules are easing up on AMP.

Rick: Very nice. Well, if you liked today’s news, subscribe below. Have a great weekend. Thank you for joining us.

Juan: Thank you, guys.

Resources

More Recent News