Closed rmcilroy closed 7 years ago
Ilya, I made this change as suggested, however the links to the HTML spec don't work properly. They link to the title page of the multi-page version, so the fragment identifiers don't point to anything on that page (they are in one of the sub-pages). Any ideas?
Paging @marcoscaceres @siusin for x-ref guidance.. :-)
Comments addressed, thanks for the hints, that seemed to work.
Hmm, I'm seeing 4 warnings on this end. Preview: https://cdn.rawgit.com/rmcilroy/requestidlecallback/dependencies/index.html
Are you seeing same warnings?
I don't see those errors. This PR shouldn't have changed those links either. Did you try with the non-cdn version of rawgit?
Yep, cmd-F5 and I still see them.
Ditto if I view the blob URL linked in this PR: https://github.com/rmcilroy/requestidlecallback/blob/ad7f456c52831d49be6a22bcc09a4dffc0546132/index.html
I'm also not seeing any errors on: https://cdn.rawgit.com/rmcilroy/requestidlecallback/dependencies/index.html
What the.. Something really odd is happening here then. I'm using incognito + CDT disable cache and I keep seeing the same error. Here's the trace HAR trace: https://gist.github.com/igrigorik/ffdb787e5ad16e456b94d89bf7a30fbb#file-ric-har-json-L166
Screenshot from devtools:
igrigorik { ~ } > curl -s https://www.w3.org/Tools/respec/respec-w3c-common | md5 ffce5b58bff3c09934147abca2d7734a
Strange. Maybe let's just get this merged? If the warnings are still there, I can take over and do a markup cleanup and squash any remaining issues.
Seems good! No warnings on the gh-pages branch (https://w3c.github.io/requestidlecallback/).
🍾 to celebrate, I just used requestIdleCallback()
in ReSpec to schedule some low priority stuff 😀
Bizarro.. @marcoscaceres I'm still seeing same errors =\
So super weird. I've tried in multiple browsers, cleared caches, etc. Here is a screenshot from Chrome Canary:
@rmcilroy or anyone else, can you confirm that it's working?
Here is Safari - showing cache disabled (and cache cleared) and also no warnings (forced lots reloads, just to be sure):
Also checked on a different computer in Edge. Seems happy there too.
Seems the interwebs is trolling you, @igrigorik.
/me facepalm.. apparently, it's Ghostery! As soon as I disable it, everything is a-OK. Apologies for the noise.
Thanks everyone for investigating!
:champagne: to celebrate, I just used requestIdleCallback() in ReSpec to schedule some low priority stuff :grinning:
Awesome stuff :+1:
Addressing comment on #59