-
Notifications
You must be signed in to change notification settings - Fork 110
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
Speculative Loading: Two <script type="speculationrules">
tags?
#1910
Comments
Ah yes, the issue is that we haven't yet released a new version of the Speculative Loading plugin that accounts for the feature in 6.8-beta1. See #1883. |
Totally makes sense, my bad! I had checked the code here in the repo and was confused that this was happening despite seeing I assume that a new release will happen in time for WP 6.8 so that this issue can probably be closed, unless it should serve as a reminder. |
Yes, we'll be releasing the new version of the plugin in a couple weeks. I'll try to make a ZIP build of the plugin later and attach it here later today for you to use in the meantime. |
@TobiasBg Here's a build of the plugin from |
Thanks, @westonruter! |
Bug Description
I just tested the Speculative Loading plugin, version 1.4.0, on WP 6.8-beta1-59953 (because I'm interested in the
moderate
eagerness).Now, I might be misunderstanding something, but it doesn't seem right that the plugin adds a second
<script type="speculationrules">
tag (forprerender
, withmoderate
) in addition to the one (forprefetch
withconservative
) that WP 6.8 adds. I would have expected that the plugin replaces the one from WP?This is what I'm getting in the frontend HTML:
(The
prerender
withmoderate
works fine, according to the Chrome Dev Tools, it's just the duplicated<script>
tag that I find odd. Or is that because of the slightly different"not":{"selector_matches":...}
rules?)The text was updated successfully, but these errors were encountered: