1897080 - Page stuck in loading at intel.com with ETP set to Strict

Status: RESOLVED FIXED

(Web Compatibility :: Privacy: Site Reports, defect, P3)

Description

[Andreea Zlata]

Environment:
Operating system: Windows 10
Firefox version: Firefox 127.0b2 (64-bit)/126.0 (64-bit)/128.0a1 (2024-05-15)

Steps to reproduce:

1. Access https://www.intel.com/content/www/us/en/search.html?ws=text#q=&sort=relevancy&f:@tabfilter=[Downloads]&f:@stm_10385_en=[Wireless]

2. Observe the page.

Expected Behavior:
The content of the page is loading.

Actual Behavior:
Dynamic page content does not load.

Notes:

• Reproduces in ETP Strict Mode only
• Reproduces in Firefox Nightly, Firefox Release/ Firefox Beta
• Does not reproduce in Chrome

Created from https://github.com/webcompat/web-bugs/issues/137022

Comment 1

[Andreea Zlata]

Attachment: Screenshot_10.png

Comment 2

[Emma Zühlcke [:emz]]

https://static.cloud.coveo.com/searchui/v2.10106/js/CoveoJsSearch.Lazy.min.js and related resources are being blocked which most likely leads to the search results page not loading. It works in ETP standard.
We could look into shimming this one given intel is a bigger site. Tom, do you think this could be shimmed?

Comment 3

[Emma Zühlcke [:emz]]

Looks like this is more widespread. We're taking known bugs under Bug 1898019.

Comment 4

[Thomas Wisniewski [:twisniewski]]

It looks like we'd have to shim dozens of Coveo scripts to get it working, with some of them being quite intricate. So unless we want to locally cache all of them in SmartBlock (and likely multiple versions), I think the only realistic way forward would be to funnel the Coveo static CDN through an anonymous proxy, or inform users that they rely on Coveo and let them opt into letting requests to that CDN through on a per-page basis.

Comment 5

[Emma Zühlcke [:emz]]

https://github.com/disconnectme/disconnect-tracking-protection/commit/25d7af6aa3f6c530b53800f706952a920e76a623 might fix this

Comment 6

[Manuel Bucher [:manuel]]

(In reply to Paul Zühlcke [:pbz] from comment #5)

https://github.com/disconnectme/disconnect-tracking-protection/commit/25d7af6aa3f6c530b53800f706952a920e76a623 might fix this

The website is fixed now.