Skip to content
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

Enable a4a friendly iframe css splitting for prod #23933

Merged
merged 1 commit into from Feb 10, 2020

Conversation

powerivq
Copy link
Contributor

@powerivq powerivq commented Aug 13, 2019

Remove experiment related code and release the feature.

closes #22418

Copy link
Contributor

@lannka lannka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

actually, let's turn on flag first and clean up in a separate PR when things become stable.

@lannka
Copy link
Contributor

lannka commented Jan 28, 2020

@powerivq is this launch stable now? We can move forward with this clean up?

@powerivq powerivq force-pushed the enable-css-split branch 2 times, most recently from bea3f28 to f39ade3 Compare January 28, 2020 22:16
@powerivq
Copy link
Contributor Author

powerivq commented Jan 28, 2020

@dvoytenko for approval of friendly-iframe-embed.

@lannka Should we change to make ampproject/wg-ads own that file?

@lannka
Copy link
Contributor

lannka commented Feb 10, 2020

Is this PR ready to go?

@powerivq
Copy link
Contributor Author

@lannka Yes. I was waiting for dima's owner approval, but my other PR made wg-ads an owner, so it is unblocked.

@dvoytenko
Copy link
Contributor

Sorry, missed this PR. What does it do exactly? Is it simply cleaning up the launched feature?

@powerivq
Copy link
Contributor Author

@dvoytenko Yes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Having separate CSS for amp4ads runtime
5 participants