See this village pump discussion for more background:
https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Kindle_problem_reported_to_OTRS
It seems what is happening is a javascript error is occurring breaking the site for Kindle 4 users.
Version: unspecified
Severity: normal
I've grabbed a Kindle 3 (version 3.2.1) and a (5th-gen?) Kindle (version 4.1.0) and section collapsing/expanding *appears to work* on both, without a JavaScript error, on https://en.m.wikipedia.org/wiki/Madeira_Firecrest
However, it's hard to position the cursor over the section titles, which makes it difficult to use. If they were turned into links when collapsed, the cursor would position over them much more easily.
It's possible that there is a JavaScript error that occurs intermittently, or only on certain versions of the software...
It turns out that the Kindle 4 problem only occurs when JavaScript is *disabled*. Bug reporter with this model also had software 4.1.1, but model B00E (mine is 9023).
With JavaScript *enabled*, the collapsible sections work as expected, as long as you can figure out where to click.
It sounds like the Kindle browser's "disable JavaScript" is not doing a good job of... disabling JavaScript, as some must be running in order to trigger the collapsed/gray sections... whafu?
My suspicion is that inline scripts are still run when javascript is disabled on Kindle 4. Weird but logical reason.
We should move inline javascript to the startup module for RL anyway to remove this problem..
I can't actually reliably replicate this. On Brion's Kindle 4 the alpha (Dragon mode) was enabled in settings which is known to be javascript dependent (see bug 42746).
On Wikipedia on first load I saw grayed out sections that were not clickable. Refreshing the page fixed the problem.
I suspect this was a caching issue which has now been fixed. I'm tempted to close as RESOLVED WORKSFORME but will let this stew for a day or two in case the original reporter is still having this problem!
Yeah I tried alpha, beta, and regular modes and could reproduce the bug in all when JS was disabled. Can't repro it anymore either, so either code updates or something falling out of cache are possibilities.
I asked [[User:Ukexpat]] who relayed the info from OTRS to reply on the ticket and check with the original reporter if any problems are still continuing.
UKExpat please reopen this or message Brion to reopen this if the problem still persists.
Thanks!