Au contraire...
They want to lose them so that the Starmfurher has to do unpopular things to counter all the seeds of disaster already sown, so that in 5 years time the Tories will be back in for the foreseeable future. You read it here first.
Au contraire...
They want to lose them so that the Starmfurher has to do unpopular things to counter all the seeds of disaster already sown, so that in 5 years time the Tories will be back in for the foreseeable future. You read it here first.
If it was an SSD... Its possible you have an SSD that claims to be say 256Gb but actually has a 32Gb chip inside (or smaller) that lies about how big it is and just wraps the writes so they complete... However the format is broken, as is the drive.
And another thing.. It appears to be drawing the post about to scroll on to the screen at the bottom over the top of the one scrolling off at the top.
Phone is a Huawei P20 Pro running emui 12 if that makes any difference
Yup. Never loses place at all
Here is a better screen capture that shows it happening... Its really not all threads that show the behaviour and manifestations don't seem to be related to the number of posts in the thread.
It appears I can upload it to imgur but it does involve a lot of dark muttering (sorry old guy here...) it's the first few seconds of the screen recording you are interested in - the glitch only happened once but I scrolled a bit more to see if it would do it again.
I think I have a screen recording showing it. What host do people use for gifs?
Well it was installed from the play store... So it might be a pwa but I don't think so... Nothing indicates it is anything other than a native Android app.
Or is that a whooshing noise in my ears?
It's hard because it is a dynamic effect... Perhaps a screen recording might do it.
OK. Version 1.44.0
Managed to make it glitch - it's not easy! And the original issue was happening much more.
If you flick a comment thread up and down, sometimes on reply will get rendered twice... And go away when you touch the screen
Just updating now...
Eta:
No wait - that's an older version. I can say it seems to be 1.43 that has the issue - not noticed it before.
Yup.
Boing will only fix it when the cost of compo for px deaths and FAA penalties looks like exceeding the cost of recalling/fixing during scheduled maintenance for all the engines...