New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Master Feature] Leaner AMP #16745
Comments
The first effort related to Task#2 to was remove existing polyfill for a module build. |
This is a high priority issue but it hasn't been updated in awhile. @kristoferbaxter Do you have any updates? |
1 similar comment
This is a high priority issue but it hasn't been updated in awhile. @kristoferbaxter Do you have any updates? |
@jridgewell For item #5, how close are we to shipping layers and removing the older custom elements polyfill? @erwinmombay For item #1, how close are we to shipping CC Advanced? |
This is a high priority issue but it hasn't been updated in awhile. @kristoferbaxter Do you have any updates? |
4 similar comments
This is a high priority issue but it hasn't been updated in awhile. @kristoferbaxter Do you have any updates? |
This is a high priority issue but it hasn't been updated in awhile. @kristoferbaxter Do you have any updates? |
This is a high priority issue but it hasn't been updated in awhile. @kristoferbaxter Do you have any updates? |
This is a high priority issue but it hasn't been updated in awhile. @kristoferbaxter Do you have any updates? |
Some folks have been asking about this, and I believe this effort is still underway... can someone provide an update? |
This effort is still underway, @erwinmombay – can you provide an update here on the progress of Single Pass Compilation? Single Pass Compilation is the blocking factor for the remainder of the already complete work to land. |
We're still on a slow roll out for single pass compilation, Im going to target the end of this Month (March 2019). There's no easy way currently for us to verify that everything is good w/o a more comprehensive e2e, and integration tests story (especially for ads and analytics where the issues are prominent). On a brighter note, I finally figured out how to retrieve all the possible locations where possible obfuscations errors may occur due to JsonObject and TypeDefinitions casting. Working on it this sprint and will bring my findings to the Ads and Analytics team. |
Gradually JavaScript payloads for libraries tend to increase in size as features and capabilities are expanded. Occasionally, these increases pass thresholds where devices take a noticeably longer time to parse and evaluate code leading to lower boot up performance.
This Master Feature aims to:
Timeline: End of Q4 2018.
Effort Tracking: https://github.com/ampproject/amphtml/projects/45
Q3 Goals
The text was updated successfully, but these errors were encountered: