AMP Component Updates

• Updated our amp-jwplayer documentation on  amp.dev including all the attributes mentioned in the release notes. 
• To the amp-jwplayer component, added support for a new attribute, data-config-json, which accepts a full JSON configuration using any key values listed in the web player configuration reference, with the exception of media, which should use the media ID or playlist ID attribute, and the floating player, which should use the amp-video-docking component and the dock attribute on the player element. 
• Added support for appending the iframe source url before player setup, to support token signing for example, with new attributes data-player-param-* and data-player-querystring. 
• Added an attribute, data-ad-cust-params, which supports a JSON string of custom parameters that will be appended to the end of an ad tag on ad request. 
• Added an attribute, data-config-skin-url, which accepts a url to an externally-hosted CSS file that will be loaded inside of the iframe, and can be used to target JWP elements. You can also load this file as skin.url in your JSON setup configuration using data-config-json. See our documentation on how to create your own CSS file. 
• Added an attribute, data-config-plugin-url, which accepts a url to an externally-hosted Javascript file that will be loaded inside of the iframe, and can be used to apply custom Javascript to the player. 
• Added support for populating ad tag macros in AMP with a new attribute, data-ad-macro-*. The following macros are supported: An attribute used to override the default value of macros in ad tags. Supported macros include: domain, referrer, page-url, item-{custparam}, and item-{custparam}-list. For example, setting data-ad-macro-domain=jwplayer.com would ensure the requested ad tag populates the domain parameter with the defined page url. See our ad tag macro documentation for more information. 
• In AMP, added support for the amp-consent component, which a way for publishers to collect and store user’s consent through a UI and is a way to block AMP components based on the user’s consent. Added a new attribute, data-block-on-consent, which if set blocks the player from loading until the consent state is resolved. The consent data will then be passed to the player's iframe as query parameters for use with advertising implementations. See the amp-consent blocking behaviors documentation for possible values that this attribute accepts. 
• Fixed an issue in amp-jwplayer where play events erroneously fired when an ad played. 
• Remove existing logic which was manually sending additional pause events during ads with AMP, which are no longer needed. 

General Improvements

• Added the aria-expanded attribute to the settings menu button to improve accessibility. 
• When hovering over the timeline where there are chapter markers, the chapter's name and the current time will always be shown. 

Fixes

• Reintroduced a fix from 8.20.5: Fixed a bug preventing a floating player with auto pause configured from pausing when the tab is backgrounded while an ad is loading.
• Removed a demo key value from customTargetingKey in the Freewheel ad client.
• Fixed an accessibility issue where upon exiting the settings menu the focus did not return to the settings menu icon in the control bar.