guardian / guardian/dotcom-rendering

[Bug]: Show/Hide button not appearing consistently

Open
#12,972 1 comment 0 reactions 0 assignees View on GitHub
Bug Rota
Dominant language
TypeScript
Stars
274
Forks
34
Avg merge
2d 22h
Merged PRs (30d)
121

Description

### What happened?

For a while now I have felt like the Show/Hide button for containers works inconsistently, for example the page loads and the Show/Hide buttons are visible, but when you click them nothing happens. I always figured it was just something weird on my device because usually if I switched devices or browsers or reloaded a few times it would mysteriously start working again. But in the past week or two the inconsistent behavior has gotten even worse, in that the buttons don't even appear at all. This is very annoying because it means I have to scroll past a bunch of sections I am not interested in on the front page. I know it's not that the feature has been removed, because when you first load the page the button is visible briefly, but then a second or two later the button disappears - it's not even visible in the Inspect Elements view.

Things I have tried:

- logged in/logged out
- Android/Windows
- Chromium/LibreWolf/Edge
- extensions enabled/disabled
- private tab (no cookies etc)/normal browsing
- refresh with clean cache
- full size window/skinny window

I can't seem to find a repeatable way to trigger it, although there are a lot of errors in the console. Most of the console errors on desktop are due to blocked tracking requests (ophan), but I know they are not required to make the button work because when the page loads in a way where the button does appear and work, same requests were blocked and it's fine. Also that wouldn't explain why it also intermittently doesn't work on different browsers and devices.

### Where is this happening?

https://www.theguardian.com/international

### What is the impact?

All sections are expanded, even if previously you had hidden them.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.