@timmse
They caused 2 404 extra requests.
Chrome Network Tab:
The below image is taken from YogaDNS, which logs all traffic requests. It clearly shows 2 extra requests made to w3(dot)org
Appreciate this thread says solved but I’m getting the same svg%3E request 404 response as @masoodalam51 when using the Products element. Other such svg requests seem to get 200 response. No such 404 response when not lazy loading.
Chrome dev tools network tab info below
Initiator for one of the successful requests:
data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%20380%2057'%3E%3C/svg%3E
Initiator with 404 response:
https://www.w3.org/2000/svg'%20viewBox='0%200%20380%20342'%3E%3C/svg%3E
The initiator path for 404 response seems to be rejected:
Is that 404 response expected and not causing any delay?
I think you have to open new thread for getting proper attention.
Hey guys,
Bricks 1.6 beta contains a fix for this problem. However, we would be happy if you could briefly test whether the problem is fixed so that we can include it in Bricks 1.6 stable.
You can find the beta version in your account:
https://bricksbuilder.io/account/?v=1.6-beta
Best regards,
timmse
I’ll try to do so in the next couple of days, just need to get something out first.
I’ve updated to 1.6 beta and checked on one page on my test server and the issue no longer appears so think it will fix the issue. Thanks.