|
baka kaba posted:So when you tapped the ... the post header would expand? Or do you mean tapping elsewhere made the header expand as normal, and tapping the ... had no effect at all? I'm assuming he had the same issue as me. And as far as I could tell, nothing would actually happen when tapping the ... button. However, you could get the post header to expand (and show the users reg date/custom text) by tapping the user name or just off the ... area. As for me, I don't keep automatic updates on and sometimes fall pretty far behind. I ended up updating the SA app on a whim and didn't even think about updating Chrome until someone mentioned it in here. I mean I probably would have just updated my whole phone at some point which would have fixed it, but being able to directly fix it by knowing I only had to update Chrome was nice.
|
#
?
Jan 21, 2019 23:03
|
|
|
|
| # ? May 10, 2024 17:22 |
|
|
Hrm ok, thanks! It's a weird bug because it's just a touch event like anything else. There's some slightly unusual CSS for that button which might be broken in one of the Chrome builds, but the fact the header isn't expanding means the box is seeing the event, something weird's happening Ideally people would just get the fix through the automatic update and it wouldn't be an issue (and honestly if you're turning updates off then your browser/system webview is one of the things to keep updated just for security)
|
|
#
?
Jan 21, 2019 23:14
|
|
|
I had that issue, and posted a few pages back about the Chrome update fixing it for me. I tend to keep wifi off, so my apps end up not updating as much. As to the header, clicking that would cause the post header/avatar to expand as normal. Clicking the '...' menu whether the header was expanded or not had no effect. It did not cause the header to expand for me. I had to tap in the header but not on the '...' menu for that to happen.
|
|
#
?
Jan 22, 2019 00:47
|
|
|
So when I tap the hamburger menu icon and then click the option to go to the last thread I was viewing it now takes me to page one of that thread. Previously it would take me to where I had left off. Is this a bug or is there an option to change that behavior? I appreciated being able to go back to where I was since I often fst finger my screen and accidentally leave the page I was on.
|
|
#
?
Jan 24, 2019 05:19
|
|
|
My app has started being super bad about staying in memory. Roughly 100% of the time that I open a link from it, pressing back dumps me to my homescreen and opening awful again it reloads, losing my position in a thread. Pretty sure it didn't behave like this last week, where pressing back in the browser would instead take me back to exactly where i was before pressing the link. Other apps seem to stay in memory fine and my phone has not received any updates as far as I know. The play store (https://play.google.com/store/apps/details?id=com.ferg.awfulapp) says it was updated on the 20th, so i would guess this started happening after installing that. It says i'm a beta tester. Maybe I should stop that? Nokia 7.1 is the phone, in case someone suspects the app is not actually at fault.
|
|
#
?
Jan 24, 2019 11:22
|
|
|
Phosphine posted:My app has started being super bad about staying in memory. Roughly 100% of the time that I open a link from it, pressing back dumps me to my homescreen and opening awful again it reloads, losing my position in a thread. Pretty sure it didn't behave like this last week, where pressing back in the browser would instead take me back to exactly where i was before pressing the link. Other apps seem to stay in memory fine and my phone has not received any updates as far as I know. The play store (https://play.google.com/store/apps/details?id=com.ferg.awfulapp) says it was updated on the 20th, so i would guess this started happening after installing that. It says i'm a beta tester. Maybe I should stop that? Nokia 7.1 is the phone, in case someone suspects the app is not actually at fault. I restart my phone and it fixes this problem for a few weeks.
|
|
#
?
Jan 24, 2019 12:23
|
|
|
Is there an option to view images in a different view so I can zoom in on them? Opening imgur links just makes them show up in their awful mobile site where I can't see the full resolution image.
|
|
#
?
Jan 24, 2019 13:16
|
|
|
Kazy posted:Is there an option to view images in a different view so I can zoom in on them? Once you open the imgur link in their mobile site, you should be able to press/hold on the image and get it to open in a new chrome tab. That's about the only way I've found to really get a good look at imgur links on my phone. It's more a problem with imgur having a terrible site.
|
|
#
?
Jan 24, 2019 15:54
|
|
|
TMMadman posted:Once you open the imgur link in their mobile site, you should be able to press/hold on the image and get it to open in a new chrome tab. That's about the only way I've found to really get a good look at imgur links on my phone. I tried that but it only opened the thumbnail. 
|
|
#
?
Jan 24, 2019 15:56
|
|
|
Kazy posted:Is there an option to view images in a different view so I can zoom in on them? Can't you press the image once and choose the Display Image option? That should load it in a zoomable viewer within Awful. Or do you mean images that aren't parsed in awful, and are just URLs?
|
|
#
?
Jan 24, 2019 19:20
|
|
|
Scaramouche posted:Can't you press the image once and choose the Display Image option? That should load it in a zoomable viewer within Awful. Or do you mean images that aren't parsed in awful, and are just URLs? Pressing them once opens them in the browser, on Imgur's site. Long pressing does nothing
|
|
#
?
Jan 24, 2019 19:31
|
|
|
Kazy posted:Pressing them once opens them in the browser, on Imgur's site. Long pressing does nothing Is this where someone's posted a link to an imgur page and not the actual jpg or whatever? We don't handle that, it's just an external website link like any other Raldikuk posted:So when I tap the hamburger menu icon and then click the option to go to the last thread I was viewing it now takes me to page one of that thread. Previously it would take me to where I had left off. Is this a bug or is there an option to change that behavior? I appreciated being able to go back to where I was since I often fst finger my screen and accidentally leave the page I was on. Apparently that's been added to the issues list as a bug! That one's probably my fault, I'll take a look
|
|
#
?
Jan 24, 2019 21:01
|
|
|
baka kaba posted:Is this where someone's posted a link to an imgur page and not the actual jpg or whatever? We don't handle that, it's just an external website link like any other Here's the post I was trying to check out the image: Distant Chicken posted:Um, hey Rocketlex. I think there's something wrong with my game. I think it's specifically timg that does it.
|
|
#
?
Jan 24, 2019 21:11
|
|
|
Go to settings -> posts and disable always open link at the very bottom.
|
|
#
?
Jan 24, 2019 21:16
|
|
|
Phosphine posted:My app has started being super bad about staying in memory. Roughly 100% of the time that I open a link from it, pressing back dumps me to my homescreen and opening awful again it reloads, losing my position in a thread. Pretty sure it didn't behave like this last week, where pressing back in the browser would instead take me back to exactly where i was before pressing the link. Other apps seem to stay in memory fine and my phone has not received any updates as far as I know. The play store (https://play.google.com/store/apps/details?id=com.ferg.awfulapp) says it was updated on the 20th, so i would guess this started happening after installing that. It says i'm a beta tester. Maybe I should stop that? Nokia 7.1 is the phone, in case someone suspects the app is not actually at fault. What are you actually doing when you see this? Got a link to a thread where it happens, and the link you click on? For what it's worth the "normal" app has been on the same version as the beta for a while, and the fix that went out on the 20th is literally a page load that happens one time, so it's definitely not that. I just profiled the app again and I can't see anything amiss, no memory leaks or any problems like that, it's always been pretty well behaved. But it's possible there's an edge case where that's not true, so links to a page would help just to rule that kind of thing out At the end of the day though, the app's basically a specialised browser, and heavy pages (lots of big images, embeds etc) are gonna take up more memory. And once an app is in the background, it's up to the system to decide whether it can stay in memory - that depends on what else you've got running, especially the app that's in the foreground (in this case, another web browser that might be loading some garbage site full of ads and videos and hundreds of megaborts of who knows what else) Ideally the app would save and restore your place on the page no matter what, that's on the feature list  not for lack of trying, it's really awkward for a bunch of reasons! But as far as the app getting kicked out of memory more often goes... not really sure if we can do anything about that. The app's memory use has been pretty steady over the years, maybe things like changes to the webview and other system stuff makes it heavier  might be able to try aggressively clearing memory in a couple of ways, but it probably won't do much!
|
|
#
?
Jan 25, 2019 00:50
|
|
|
Would reducing the number of posts per page help with particularly heavy threads? I'm on 10ppp and seldom see a reload.
|
|
#
?
Jan 25, 2019 01:10
|
|
|
LastInLine posted:Would reducing the number of posts per page help with particularly heavy threads? I'm on 10ppp and seldom see a reload. It's worth a try (it would definitely be good to see if it helps people having these issues) but just from doing a bit of profiling, the webview seems to be pretty efficient at managing its memory as far as I can tell, I'm only seeing like a 10MB difference or so at best. (This is using the Android Studio profiler and watching Native memory use, and running an Allocations profiler in Chrome's dev tools to see what's allocated and what's left alive, in case anyone has any better ideas for this stuff) If someone wants to throw a really heavy page at me I'll check that out too also is the site ok on 10 ppp? I thought there used to be a 30ppp minimum 
|
|
#
?
Jan 25, 2019 02:18
|
|
|
baka kaba posted:also is the site ok on 10 ppp? I thought there used to be a 30ppp minimum I have no complaints at all.
|
|
#
?
Jan 25, 2019 07:20
|
|
|
baka kaba posted:It's worth a try (it would definitely be good to see if it helps people having these issues) but just from doing a bit of profiling, the webview seems to be pretty efficient at managing its memory as far as I can tell, I'm only seeing like a 10MB difference or so at best. (This is using the Android Studio profiler and watching Native memory use, and running an Allocations profiler in Chrome's dev tools to see what's allocated and what's left alive, in case anyone has any better ideas for this stuff) If you look at some screenshot LP threads, and isolate the thread so you only see the OP posts, you can get some pretty heavy pages. Here's the Dangan Ronpa 2 LP that I tried on my Nexus 7 over the holidays: https://forums.somethingawful.com/showthread.php?threadid=3793286&pagenumber=1 It wouldn't crash out, but it would take close to 2 minutes to render a page sometimes. Was on default 40pp I believe when I looked.
|
|
#
?
Jan 25, 2019 19:04
|
|
|
LastInLine posted:I have no complaints at all. One of the recent speedup tweaks was noticing the thread page dropdown boxes have an <option> element for every drat page, so in big threads there are hundreds or thousands and they slow page parsing right down, so I yoinked them out Guess you were rolling with 4x as many, I hope your phone was fast at least!! Scaramouche posted:If you look at some screenshot LP threads, and isolate the thread so you only see the OP posts, you can get some pretty heavy pages. Here's the Dangan Ronpa 2 LP that I tried on my Nexus 7 over the holidays: Ok yeah, this is suitably insane, thanks! And do people actually browse like this? loving hell So my initial testing is that yeah, that uses a hell load of memory in the webview, and also it's not that bothered about garbage collection for some reason, so it happily climbed towards 1GB from scrolling through a few pages, and eventually cleared a bit (seems to keep steady on normal threads). That's definitely gonna make the system want to kick it out if it's trying to reclaim memory, so if you're reading these kinds of threads, it's probably not gonna behave but it's also an extreme case I'll play around and see if I can get my emulator to stop crashing (probably needs more memory ) and test it on there, but yeah - maybe we can get the webview to release memory more aggressively. Also yeah those pages are slow to load because of the sheer number of image tags to parse - I might have a tweak for that though
|
|
#
?
Jan 25, 2019 20:33
|
|
|
baka kaba posted:One of the recent speedup tweaks was noticing the thread page dropdown boxes have an <option> element for every drat page, so in big threads there are hundreds or thousands and they slow page parsing right down, so I yoinked them out Oh yeah I don't browse like that, you were asking for heavy use scenarios and that was the first one I thought of. I would say that a lot of the delay is probably purely bandwidth related too; I was using my old Nexus 7 which is only 2.4ghz wifi and that's probably a lot of megabytes coming down the pipe. Unless you were referring purely to page render time not including payload.
|
|
#
?
Jan 25, 2019 20:44
|
|
|
Nah I mean we have duration logging for different stages of the parsing process, while it's chewing through the HTML structure and pulling data out, and it's taking a while to get through a page that dense. This is before anything gets displayed or starts loading Someone's gotta be reading threads like that though, right? Even if they're not as bad, a heavy one is definitely gonna be an issue if the app goes to the background, especially if you're switching to a web browser. That's why it would help to know what the people getting reloads every single time are doing - what kind of threads it happens on, what they're switching to, if it happens on a freshly booted phone and how much memory it has, that kind of thing
|
|
#
?
Jan 25, 2019 21:02
|
|
|
Just wanted to bump my comment that the "keep screen on" toggle doesn't persist through multiple uses of the app. Once it leaves memory it unchecks itself.
|
|
#
?
Jan 25, 2019 21:32
|
|
|
Ohhhh yeah that probably does happen huh. It's only meant to be a temporary thing, not an app setting, but if the app keeps getting kicked out of memory...
|
|
#
?
Jan 25, 2019 21:43
|
|
|
baka kaba posted:One of the recent speedup tweaks was noticing the thread page dropdown boxes have an <option> element for every drat page, so in big threads there are hundreds or thousands and they slow page parsing right down, so I yoinked them out I read some large threads but have never noticed any slowdown to the point where I was annoyed. I guess I just assumed that if the app takes a while to load a page sometime that it was the connection or the site. This is on a Pixel XL first gen. Still, every bit helps.
|
|
#
?
Jan 26, 2019 01:12
|
|
|
Oh yeah I guess for context I'm not really encountering the swapping out of memory issue. Just threw in that example thread because I knew it would be a ball buster.
|
|
#
?
Jan 26, 2019 02:27
|
|
|
Sereri posted:Go to settings -> posts and disable always open link at the very bottom. That's perfect, thanks! (Though I wish there was a way to access the menu without having to turn the option off, it gets a bit old having every link take two taps)
|
|
#
?
Jan 26, 2019 11:16
|
|
|
Is there some mechanism in the app to cause page refreshes automatically? Sometimes, even with the app open and focused: turning my screen back on will cause the page to refresh and frequently lose my place. Stock Pixel 2 with the non-beta app.
|
|
#
?
Jan 26, 2019 20:36
|
|
|
I will hug you and kiss you if you can get my low end phone to stop telling Awful to get lost. Here, have a  anyway just for caring.
|
|
#
?
Jan 27, 2019 17:34
|
|
|
So I ate a fatty probe the other day, and it turns out you can't view the lepers colony in the app when you're probated. Steps to reproduce: 1. post badly 2. get probated 3. click on the arrow in the pink banner at the top of the screen Expected result: The leper's colony opens and shows you you your shameful, heinous crimes against postmanity Actual result: A message pops up saying you're probated and the screen remains black I'm on beta if that matters.
|
|
#
?
Jan 27, 2019 18:21
|
|
|
^^^ yeah someone reported that earlier, I haven't got round to insulting a mod yet. Need to find a good time to work on it!Nth Doctor posted:Is there some mechanism in the app to cause page refreshes automatically? I'll have to check to be sure, but I *think* that might happen if the thread list refreshes, and your current thread is in that list, and something on the page has changed (edits or new posts). Maybe not even if the thread is in the current thread list - and that refresh happens automatically, so yeah. It's all a bit screwy and spooky Also not that it's the issue here but fyi, if the screen is off then the current app isn't classed as "in the foreground" so it's vulnerable to the system reclaiming memory, same as if you swapped to another app! also on the link menu thing, not promising it will be changed but would people prefer tap = open it, long-tap = menu? That's how it works in things like browsers...
|
|
#
?
Jan 27, 2019 18:44
|
|
|
baka kaba posted:also on the link menu thing, not promising it will be changed but would people prefer tap = open it, long-tap = menu? That's how it works in things like browsers... Personally, I like it how it is now, and want browsers to do it that way.
|
|
#
?
Jan 27, 2019 18:58
|
|
|
baka kaba posted:also on the link menu thing, not promising it will be changed but would people prefer tap = open it, long-tap = menu? That's how it works in things like browsers... Every time, and I mean every. Single. Time. I open a picture in C-SPAM to zoom in I long press to get that menu and only after the haptic feedback and nothing happening do i remember that it's just a tap. Of course your proposed change still wouldn't help me, I'll still long press it only now I'll get the menu and the option I'll want won't be there and I'll be confused until I go back and tap. Nothing you do can cure my idiocy.
|
|
#
?
Jan 27, 2019 19:45
|
|
|
Kheldarn posted:Personally, I like it how it is now, and want browsers to do it that way. 
|
|
#
?
Jan 27, 2019 20:03
|
|
|
Leave it. If you change it I'll constantly be cursing myself every time I forget to long press it and it whisks me off.
|
|
#
?
Jan 27, 2019 20:19
|
|
|
Yeah let's not be changing the way stuff has worked for ever please
|
|
#
?
Jan 27, 2019 20:36
|
|
|
On the one hand I'm constantly accidentally tapping pictures while attempting to scroll and opening the menu. That wouldn't happen if it required long press even is there wasn't a link. On the other hand I hate change with a fiery passion.
|
|
#
?
Jan 27, 2019 20:36
|
|
|
What if it was changed so that the long press just went to the link, and the current setting was updated to allow you to choose to flip it? So the option becomes whether you want tap to link and long press for menu or the other way around? I'm perfectly happy the way it is but I would actually use the long press to go to the image sometimes if it was available.
|
|
#
?
Jan 27, 2019 21:17
|
|
|
We have waaaay too many settings as it is. The idea behind long press for a menu is we could ditch the "always open on tap" setting
baka kaba fucked around with this message at 21:29 on Jan 27, 2019 |
|
#
?
Jan 27, 2019 21:27
|
|
|
|
| # ? May 10, 2024 17:22 |
|
|
Can we have a setting for more or less settings
|
|
#
?
Jan 27, 2019 21:30
|
|