Interested in how the modern web works? Think #webperf is important? Then check out my book “HTTP/2 in Action” with @ManningBooks at https://t.co/YtMJCZsLMq
And if you’ve ever considered writing a book then check out the story behind the book at https://t.co/qKpeRS3Dwn
#http2
@Toufeeq86531438@ChromiumDev Testing https://t.co/8BFlsV8w0n on Chrome Canary 13.3.0 Lighthouse in DevTools doesn't show the CSS as render-blocking for me.
I agree it does show on PageSpeed Insights but, as that runs slower machines, it's entirely possible it will show different as it loads differently.
Track exactly when blocks of content load in our new origin trial → https://t.co/eDQyzZEIUs
Container Timing extends Element Timing so you can measure when entire components like widgets or sidebars are available to your users.
@xopek59 FYI, we (Chrome) are changing the values of this and this will start to be rolled out to users from next week:
https://t.co/tR0sfik6bj
If you are blocking based on values of 16 or 32, then this will block real users going forward!
Don't suppose anyone in my circle knows anyone working at X engineering? Need to discuss a potential issue preventing some users from Chrome 146 logging in. @XDevelopers@engineering
Is there anything more frustrating in the world that trying to create a child's @EA games account? Inconsistent login options (Google sometimes appears, sometimes doesn't), you need a desktop app not a mobile app, you can't login using EA ID online, but can't set an email. Sigh…
@NigelWhitworth You have both `height` and `width` set to `auto`, meaning the browser doesn't know how to use those supplied dimensions.
You only need to use `auto` if setting a max-width (or max-height) and should only set `auto` to whichever you aren't setting a max value for.
@iSaumya I’m not aware of a general issue where cookies are randomly not sent. And I’ve helped a lot of people implement Speculation Rules on a lot of sites. So something specific must be happening that triggers this for your site.
@iSaumya I would suggest:
1) Reading that doc in full.
2) Trying to figure out how/why this is happening. It may seem random but there will be a reason.
3) Creating a minimal reproducible test case so we can investigate further.
Unfortunately without that, it’s difficult to help further.
@iSaumya No, not necessarily. I’m saying prefetch usually has less consequences than prerender, as JavaScript doesn’t execute (e.g. if basket count is fetched dynamically from client-side API call).
If the basket count is in the HTML then both prefetch and prerender can have this issue.
@iSaumya And can you explain what you mean by the cookies being missing? They aren’t there in the prerender HTML request in the Network tab in DevTools? Or they are no longer in the cookie store in the Application tab in DevTools?
@iSaumya Of if the page with 0 basket is cached from previous visit? Do you allow caching of your HTML pages?
(I’m not that familiar with Woocommerce to be honest but is the basket count part of the HTML? Or fetched by an API call on page load?)