hbr.org - Subscribe page broken for Harvard Business Review
Categories
(Web Compatibility :: Privacy: Site Reports, defect, P1)
Tracking
(Not tracked)
People
(Reporter: dmehic, Unassigned)
References
()
Details
(Keywords: webcompat:platform-bug, webcompat:site-report, webcompat:tracker-blocking, Whiteboard: [etp-pbm][etp-feature-tb-analytics][etp-rc-content-blocked])
Environment:
Operating system: Desktop (Mac OS X) and Android
Firefox version: Firefox 135
Preconditions:
- Strict ETP enabled
- Clean profile
Steps to reproduce:
- Go to https://hbr.org/
- Click Subscribe
Expected Behavior:
The page elements load correctly. User can complete subscription steps.
Actual Behavior:
Page is broken. 'We're experiencing a connection error. Sorry for the inconvenience. Please try again later.' error appears.
Notes:
- Reproduces in ETP Standard, Strict Mode
- ETP toggle OFF does not help. Same error appears.
- Reproduces in Firefox Nightly on desktop and Firefox Beta on Android
Comment 1•1 year ago
|
||
Unblocking c2.piano.io,buy.tinypass.com,cdn.tinypass.com all classified as analytics-track-digest256 unbreaks the website.
Comment 2•10 months ago
|
||
Tim, do we need to shim these to unbreak this usecase?
Comment 3•9 months ago
|
||
There are several resources loaded via buy.tinypass.com, including scripts, HTML content, and images. These are used to display the subscription content on the page. So, we need to shim all of them to unbreak the use case.
And the shim will break in the future if the site updates its subscription content. So I am not sure how feasible it is to shim this case.
Tom, do you think a shim is feasible for this case? Thanks.
Comment 4•9 months ago
|
||
I wouldn't recommend shimming such a case, as these sorts of things always end up being more fragile, and a deeper rabbit hole, than anticipated. I would rather suggest detecting it and allowing the user to opt into allowing just the specific content.
Updated•7 months ago
|
Comment 5•7 months ago
|
||
This bug has been fixed by a permanent intervention.
This is an automated assessment, if this bug still reproduces for you in the most recent Nightly version, please reopen.
Description
•