search

adobe / aem-core-wcm-components

Standardized components to build websites with AEM.
https://docs.adobe.com/content/help/en/experience-manager-core-components/using/introduction.html
Apache License 2.0
743 stars 750 forks source link

[Page][AMP] Allow customers that use AMP Page (v1) to keep using clientlibs that do not load well in async mode #2113

Closed github-jira-sync-bot closed 2 years ago

github-jira-sync-bot commented 2 years ago

With https://github.com/adobe/aem-core-wcm-components/commit/59ffc3a6f51359fa6abc3ec3aa010b09bd704314#diff-37fc35c92d090e308b6609c14873ca2cd7617918e5106750b12cd727b655f452R22 AMP Page (v1) component was switched to inherit from Page (v3) instead of Page (v2).

This is not a backwards-compatible change and causes issues for Ernst & Young (they had to rollback in SKYOPS-27331) and possibly other customers too.

We have several possible solutions:

  1. switch it back and create AMP Page (v2) that will inherit from Page (v3)
  2. overlay HTL script that includes clientlibs to use synchronous mode
  3. add a page policy in Page (v3) that controls how clientlibs are being loaded (default sync, can be switched to async by customers)
github-jira-sync-bot commented 2 years ago

The issue was exported from the internal Jira. The original Jira issue: SITES-5564.