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
Excluding other extensions when an extension is present #21723
Comments
When discussing this I was thinking of |
I agree. |
+1 for
|
@zhouyx I think this got forgotten. Is this still important to you? |
I think the issue still exist. But I not urgent because there's no incentive for one to include two components either from different service provider (amp-skimlink vs amp-smartlink) or designed for the same purpose (amp-access vs amp-subscriptions). |
Thanks for the update. I'll keep it around, but let it remain at P3 for now. Would be nice for a fixit. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
Is anyone still interested in this being done? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
Right now we have some extensions that don't work well together. For example when
<amp-skimlink>
and<amp-link-rewrite>
works together, the ladder component can affect what the previous component does.It would be useful to have a feature that only allow one component on a page among a list of mutual exclusive extensions.
@ampproject/wg-caching
The text was updated successfully, but these errors were encountered: