Forum icons hard to hit on mobile?
djslack had a quick thing to say said8
Is it just me or are the little icons like edit, whisper, and reply much harder to hit on mobile lately?
I mean, I can get them to work but it often takes many tries, like the hit area is one or two pixels.
- 11 comments, 27 replies
Whisper must be easier to hit. I have received some whispers lately that look like they should be comments.
@yakkoTDI It is easier to hit, and that seems like a good analysis. I have caught myself in a whisper box that I had intended to be a reply instead several times lately.
Better than the reverse …
Confirm. Same here. The workaround is to use the two finger spread to enlarge the page, but then the text entry box pops up at the top of the page, requiring a scroll to get to it.
@werehatrack yep, I’ve done the same, but usually only after a half dozen attempts to just tap it normally.
I thought it was just me. Haven’t been able to hit reply on the phone. Have to power up the computer to respond to anyone. Everything looks grayed out on my phone.
Yep, I’ve been having the same problem, but I’ve been getting around it by turning to landscape, which is a giant pain in the ass. Thanks, @werehatrack, for mentioning the zoom method, i think that’ll be a lot less annoying!
That is also the easiest way to ‘like’ one of your own posts. When you hold the star to see who has liked a comment it is very easy to add your like instead.
@chienfou the great part is the scavenger hunt without clues to go and find it to remove it if you don’t notice when it happens.
I currently have 21 documented incidents of self love on here. Not bothering to go fix it
@chienfou @djslack I’ve only ever had one and I want to say it happened in my first 3 months here. I tried for ages to find and fix it. It seems to have been lost to the void.
@chienfou @djslack @ExtraMedium Same here, some un-findable star I clicked without knowing, from my first couple months, and now I have no Earthly way of tracking it down.
Well, I imagine I could figure it out if I had access to the database, but I expect that not even most employees get that.
@xobzoo Very true. I looked so hard for the mystery star that I decided it was on a reply that I ended up deleting for something because I’m just certain it doesn’t exist.
Somewhere, someone can be bribed to get this information. All we need to do is find out who that is and what they like.
No issues currently on my phone.
I’m on a iPhone, is everyone having issues on Android or is it a mix of Android and iOS?
@Ignorant I have an Android, but the reply button worked just now.
@gogrrl @Ignorant I’m on Android, and have also noticed sometimes the icons randomly work normally.
@gogrrl @Ignorant @ircon96 For me, on a Pixel 7 Pro, this is seldom the case.
@Ignorant Android Pixel 6. Same problem.
@Ignorant Pixel 7 here. I’ll have to try on iphone when I get a chance and see if it behaves differently.
Have a pen, so I don’t notice
Definitely not just you. I thought it was just me, too.
I’ve been doing some testing and I’ve also reached out to our dev team about this. Seems like you can get the reply and whisper option on Android most of the time if you are able to hit the very small space above those buttons but still under the text. The green area here:
@ExtraMedium ooh, you’re right! I didn’t think that hard about it but that seems to work reliably for me too, though it’s not the easiest to hit. Hopefully identifying that helps get to the bottom of it.
Thank you for digging into this!
@ExtraMedium this is because Apple compensates for your actual finger touch vs what our eyes perceive we’re pointing at. Hence the android little green space being higher than the icon itself. Little important details like this make a difference for user friendliness. I’ve never had an issue with accidentally hitting reply vs whisper on my iPhone.
@hammi99 That’s not the case at all in this situation. Not only does Android also correct for “intended vs actual” touches, but I was able to screen-record the inputs to see where the actual touches were registering to confirm the problem. That’s part of how I determined the effectively clickable zones I shared in my screenshot. I could see that the “touch targets” were not coded correctly on the site for all devices—nothing to do with the phone’s click handling, but rather how the site handles target information sent by the device. If this were related to how the phone registers touches, all Andoid users would expect that behavior from years of use, and would never have noticed it not working exclusively with those clicks on this site since it would be the standard behavior for the phone. That you’ve never had the issue just means the site was coded correctly for iphone. The same result happens when certain webpages look fine on Chome but not Firefox. It’s not that the computer viewing the page is doing something wrong.
Regardless, the team is working on it and I hope it’s already functioning better for some, and will be fully cleared up for everyone soon.
@ExtraMedium so you’re saying that the on-click area is different for different devices/OS/desktop/mobile?
@ExtraMedium @hammi99 yep, there can be different css for different browsers, viewport sizes, etc.
Thank you @ExtraMedium for your help running this down! I had no idea how you figured that out, recording the touch inputs is a cool idea.
@djslack @hammi99 Yeah, coding for iPhones is somewhat easier because they are all the same device to systems that see them. Physical aspects change, but functions are mostly the same across generations and certainly will be the exact same across two of the same model. Android is an open ecosystem so two Pixel Pro phones may be running fully different OS versions (not just ones provided by Google or the phone carrier, but totally custom ROMs built by mod teams). Think bios level alteration of the devices. I used to hack the crap out of my Nexus phones with custom ROMs and software. Most sites are built to handle default configurations of devices but those settings may change from version to version, so while the phone works as expected for users, websites can function totally differently. Our dev team does an amazing job of keeping them working across a wide variety of systems given that the site and forum are custom-built, line-by-line by them. This isn’t like a Squarespace or GeoCities setup. (Am I showing my age with the GeoCities reference?)
maybe? But CollegePark/3311 was a bangin site a quarter century ago.
Hey everyone, we’ve made a change to hopefully improve the touch targets for these buttons. Please let us know if things have improved. And if anything has gotten worse, I trust we’ll hear about it.
@mschuette Yes! It works for me!
/giphy yes yes yes
@ExtraMedium @djslack @mschuette It seems to be back to normal for me, too. Thank you to all involved with troubleshooting this issue & to all the Mehtizens who joined in the commentary to bring it to the attention of the techs in the first place!
@djslack @ExtraMedium @ircon96 @mschuette Same here, one tap and the reply box popped right up.
I can’t even edit/bold/italicize on mobile (unless I turn Desktop mode on)
@pakopako I can, if I can remember the tags for the attributes.
@werehatrack I think it has something to do with where the space goes after the “>” – gah, I have to juggle another CSS/IRC tag??
I posted something about this probably a month ago that certain functions like reply, whisper ect weren’t working unless I turned my phone to landscape mode. I see so many of you read it. A couple of us figured out it was a meh problem and mine was solved within couple of days. Hope you guys get yours fixed.