1781

Not for me, it isn’t. Clicking home only works intermittently too.

1782

Heh, they closed the meta thread with some mysterious talk about broken CSS.

/shrug

1783

Ask not what the software can do for you, ask what you can do for the software.
–Albert Einstein

1784

That proves it. Fix the css already stusser. Jeez.

1785

Christ, that was such a wumpus way of closing an issue. An issue which, if that thread is anything to go by, affecting a lot of people.

1786

To be fair, CSS is where hope goes to die.

1787

You’re giving him too much credit. There are other plenty of other software developers that run their public ticket systems this way. I have to put a plug in for Atlassian every time he does this.

1788

I have no idea what thought process would lead to the conclusion that a problem that is exclusively but broadly affecting Discourse, on a specific browser and operating system, is caused by improperly written CSS. Like, wut.

Also the idea that it’s somehow Android losing track of network status. On Discourse boards on Chrome, only.

1789

Switch to Firefox already.

1790

I can still reliably fix the issue (for a session) by reloading. shrug

1791

1792

They may have a fix, I’ll update to it when it’s in.

1793

So, not CSS.

1794

My long Discourse nightmare is almost over!

1795

Sucka, I’ve been on Brave for months.

1796

Brave is Chrome. Vivaldi is Chrome too. Edge will soon be Chrome. Opera is Chrome.

Only Firefox and Safari are not Chrome.

1797

Looks like it might be in now.

1798

Great, then it should be fixed here.

1799

Appears to be fixed for me. Yay!

1800

w00t