Does anybody actually use this site on mobile :fire:
-
@pie_flavor Sorry, I seem to have tagged your Canuck cousin back there...
-
@pie_flavor said in Does anybody actually use this site on mobile :
old university WiFi
Comparable to milwaukeepc?
-
Can I request an informal UX test-run of the new sidebar menus? They're not on here, they're on our community forum right now, and we're on the verge of merging it in.
Does it work well on phones? Does it make sense to you?
-
I mobile almost exclusively. The biggest issue I have is with inadvertantly partially pulling out the right tray and it getting fucking stuck.
-
Can you repro that on the new sidebar?
-
New menu seems snappier, otherwise similar in look and feel to what we have here.
I did get a couple of cases when it didn't register my swipe, but not regularly reproducible
-
@jaloopa But more importantly, I didn't see the new one pop out unintentionally.
-
Thanks @hungrier
@Jaloopa the new sidebar purposely doesn't register swipes on one half of the screen if you're going the other way (e.g. swipe from right to left, you have to start on the right hand side of the screen.)
That kind of didn't make sense, so if you try again, the swipe should register all over (like before)
-
@julianlam I think it should only register swipes coming from off-screen, but maybe that's hard to detect as compared to any swipe starting anywhere. Either way, as long as it doesn't happen when you don't expect it (like when scrolling vertically), that's good enough.
-
Off topic, but I'm overly enthusiastic that we get the red boob on mobile soon!
-
@tsaukpaetra said in Does anybody actually use this site on mobile :
Off topic
Boobs are never off topic!
-
@luhmann said in Does anybody actually use this site on mobile :
@tsaukpaetra said in Does anybody actually use this site on mobile :
Off topic
Boobs are never off topic!
Red boob though? Sounds like it's diseased
-
@zemm said in Does anybody actually use this site on mobile :
@luhmann said in Does anybody actually use this site on mobile :
@tsaukpaetra said in Does anybody actually use this site on mobile :
Off topic
Boobs are never off topic!
Red boob though? Sounds like it's diseased
No, just one that's been stimulated a lot.
-
@tsaukpaetra said in Does anybody actually use this site on mobile :
@zemm said in Does anybody actually use this site on mobile :
@luhmann said in Does anybody actually use this site on mobile :
@tsaukpaetra said in Does anybody actually use this site on mobile :
Off topic
Boobs are never off topic!
Red boob though? Sounds like it's diseased
No, just one that's been stimulated a lot.
Pink is for stimulated. Red is for slapped.
-
@pie_flavor said in Does anybody actually use this site on mobile :
@tsaukpaetra said in Does anybody actually use this site on mobile :
@zemm said in Does anybody actually use this site on mobile :
@luhmann said in Does anybody actually use this site on mobile :
@tsaukpaetra said in Does anybody actually use this site on mobile :
Off topic
Boobs are never off topic!
Red boob though? Sounds like it's diseased
No, just one that's been stimulated a lot.
Pink is for stimulated. Red is for slapped.
I posit that slapping is just a different form of stimulation. ;)
-
@tsaukpaetra
Someone should stimulate some sense into you then
-
@luhmann said in Does anybody actually use this site on mobile :
@tsaukpaetra
Someone should stimulate some sense into you thenDidn't work. Also found that, no, that is not one of my kinks...
-
@topspin said in Does anybody actually use this site on mobile :
But I definitely do see this jumping around when the forum loads an image and it makes scrolling really annoying on mobile.
When I proposed delay loading stuff above where you came in, the devs also decided to delay loading below for bandwidth purposes. I still think that's a terrible decision since you really have to turn that off or risk very weird jumping around as you scroll to different posts.
Then there's the stuff that iFramely does, which further complicates things, but ought to be amenable to the same (if requiring a different implementation) solution.
-
@boomzilla said in Does anybody actually use this site on mobile :
@topspin said in Does anybody actually use this site on mobile :
But I definitely do see this jumping around when the forum loads an image and it makes scrolling really annoying on mobile.
When I proposed delay loading stuff above where you came in, the devs also decided to delay loading below for bandwidth purposes. I still think that's a terrible decision since you really have to turn that off or risk very weird jumping around as you scroll to different posts.
I guess it's a moot point since it's not what is actually implemented, but in an ideal world, shouldn't the browser decide what to delay load when off screen? It can decide better
- if I care for the bandwith savings (cell vs wifi),
- if it needs to unload old pictures again due to memory pressure, because on these sites it usually doesn't.
And if it does, it would probably do predictive loading of images that will be visible before I reach them. The current implementation (I'm guessing) seems to behave more like "oh shit, he's trying to display that part we delayed. Better load that image now"
Then there's the stuff that iFramely does, which further complicates things, but ought to be amenable to the same (if requiring a different implementation) solution.
I have no idea what that is.
EDIT: Oh, the oneboxing stuff. Yes, agreed.
-
@topspin said in Does anybody actually use this site on mobile :
if I care for the bandwith savings (cell vs wifi),
IME, this is only important for video or music. Images on the forum don't seem significant enough to worry about.
@topspin said in Does anybody actually use this site on mobile :
The current implementation (I'm guessing) seems to behave more like "oh shit, he's trying to display that part we delayed. Better load that image now"
Yep.
@topspin said in Does anybody actually use this site on mobile :
I have no idea what that is.
iFramely displays previews of links. So you get a box with a picture from an article instead of just a link. Depending on what the site sends back to iFramely (it's an open standard, though the name of it escapes me at the moment) the preview could be a link with the site's favicon (?) and the title of the page as a link, an actual iFrame or something else. That stuff is mostly generated by js on the client.
For instance, for a tweet, js fetches the styling and whatever from twitter instead of displaying it super simplified. Or maybe you get an embedded imgur album that you can navigate right there in the post.
-
@boomzilla said in Does anybody actually use this site on mobile :
IME, this is only important for video or music. Images on the forum don't seem significant enough to worry about.
That's why I still think a more old-school / static page would be a lot smoother to browse.
The iframely stuff is actually pretty cool, so I guess I'm wrong, but everybody's entitled to his wrong opinion.
-
@julianlam said in Does anybody actually use this site on mobile :
Can I request an informal UX test-run of the new sidebar menus? They're not on here, they're on our community forum right now, and we're on the verge of merging it in.
Does it work well on phones? Does it make sense to you?
Tried it out quick on my Nexus 5 (stock Android 6.0.1):
Opera Mobile 43: I get the desktop version.
Firefox 57: it tells me my browser doesn't support Javascript.
Chrome 62: seems to scroll OK and not accidentally bring out the sidebar or hang afterwards.
-
@topspin said in Does anybody actually use this site on mobile :
The current implementation (I'm guessing) seems to behave more like "oh shit, he's trying to display that part we delayed. Better load that image now"
You know, you're completely right, and I think in the end it's not something we should handle. It smells a little bit like NodeBB mucking around with parts of the DOM that are better handled in the browser.
For example, we could better leverage browser preloading of assets by loading page 2 images if you navigate to page 1... or something like that (just )
I also recall that Chrome was beta testing some code in their browser that would compensate for jellypotato, and it wreaked bloody havoc on my code because Chrome would fix the scroll shift, and then NodeBB would fix it again, making things worse.
If Chrome has this in stable, and another big browser picks it up (FF?), then I'll ditch delayed image loading ASAP. Let me know
@boomzilla said:
the devs also decided to delay loading below for bandwidth purposes. I still think that's a terrible decision since you really have to turn that off or risk very weird jumping around as you scroll to different posts.
Yes, and it seems like my code isn't stable enough to stand the test of time, so I think it's time for it to go.
-
@julianlam got to give you one thing, the attitude of that post is the exact opposite of what would have been.
-
Good lord, that Mozilla issue is 18 years old...
-
@julianlam said in Does anybody actually use this site on mobile :
If Chrome has this in stable, and another big browser picks it up (FF?), then I'll ditch delayed image loading ASAP. Let me know
Looks like Opera has it too.
-
@julianlam Is it upstream in Chromium? If so it might be that all Chromium-based browsers have it (assuming they're using a sufficiently recent version of it). Then again, if it's a flag, then who knows.
-
Yeah it looks like it became default enabled in Chrome 56, which is neat
-
w̠̙̙̱̓̏ͨ̿ͯ̇̎̿t̞͓̗͙̖͇͈̤̔ͣ̀̄̂ͧ̓̽f̦̈́ͨ ̮̩̼̗̗ͫ̐͛h̫̘̘̆̓a̲͕͕͉͎͈̳̗ͨ̾́̋p̦̯̝̞̗͛͛ͪ̈́p̭̲̮̦͕̰͕̌ͨ̆̈ͫ͒͆̊ẹ̤ͬ̑n̖͖̐͒͊ͭͧḛ̱ͩ̓̓̆d̪̳̺̳̪͍̙̩̽̊̈͛ͅ ͎̩͈̪̹͉̱̼̒͆h̰͚͒ͪͩ̔ȅ͉̜̖̖̬̒r̻ͩͤ͑ͦ̀̎̅̚ȇ̤̟̪̖̈ͯ̄̊͊̾
-
@bb36e said in Does anybody actually use this site on mobile :
w̠̙̙̱̓̏ͨ̿ͯ̇̎̿t̞͓̗͙̖͇͈̤̔ͣ̀̄̂ͧ̓̽f̦̈́ͨ ̮̩̼̗̗ͫ̐͛h̫̘̘̆̓a̲͕͕͉͎͈̳̗ͨ̾́̋p̦̯̝̞̗͛͛ͪ̈́p̭̲̮̦͕̰͕̌ͨ̆̈ͫ͒͆̊ẹ̤ͬ̑n̖͖̐͒͊ͭͧḛ̱ͩ̓̓̆d̪̳̺̳̪͍̙̩̽̊̈͛ͅ ͎̩͈̪̹͉̱̼̒͆h̰͚͒ͪͩ̔ȅ͉̜̖̖̬̒r̻ͩͤ͑ͦ̀̎̅̚ȇ̤̟̪̖̈ͯ̄̊͊̾
-
@bb36e said in Does anybody actually use this site on mobile :
w̠̙̙̱̓̏ͨ̿ͯ̇̎̿t̞͓̗͙̖͇͈̤̔ͣ̀̄̂ͧ̓̽f̦̈́ͨ ̮̩̼̗̗ͫ̐͛h̫̘̘̆̓a̲͕͕͉͎͈̳̗ͨ̾́̋p̦̯̝̞̗͛͛ͪ̈́p̭̲̮̦͕̰͕̌ͨ̆̈ͫ͒͆̊ẹ̤ͬ̑n̖͖̐͒͊ͭͧḛ̱ͩ̓̓̆d̪̳̺̳̪͍̙̩̽̊̈͛ͅ ͎̩͈̪̹͉̱̼̒͆h̰͚͒ͪͩ̔ȅ͉̜̖̖̬̒r̻ͩͤ͑ͦ̀̎̅̚ȇ̤̟̪̖̈ͯ̄̊͊̾
The forums' emoji things hadn't refreshed for you yet, so it's displaying the alt?
-
@julianlam said in Does anybody actually use this site on mobile :
pie_flavour
sips tea, adjusts monocle
-
@hungrier said in Does anybody actually use this site on mobile :
I think it should only register swipes coming from off-screen
The problem with that is that depending on the device, your finger will touch the screen first in a place that might not be the left-most or right-most pixel, and there's no way to detect a touch that isn't on the touchscreen.
-
@julianlam said in Does anybody actually use this site on mobile :
I also recall that Chrome was beta testing some code in their browser that would compensate for jellypotato, and it wreaked bloody havoc on my code because Chrome would fix the scroll shift, and then NodeBB would fix it again, making things worse.
I remember back when we were on Discourse and Chrome had that feature hidden in chrome://flags, it would get stuck scrolling down forever until you closed the tab or navigated away from the page using the address bar.
-
I saw similar comments in the Google blog post about scroll fixing... I assume it was something that happened in nightly versions and was addressed
In any case, it does seem to be default enabled now, so if this still happened, I'm sure we would've heard about it by now.
-
Boy, do I love it when I've finished a decently sized post, and notice an error, so I tap to reposition the cursor, but a notification appears at that exact moment, and I tap it instead and go to a completely different thread, and quickly go back but I've already lost my post entirely.
-
@pie_flavor not sure what/if you applied any updates recently, just anecdotally posting has become much worse. I now have similar issues as other people described.
It's so slow that I sometimes enter multiple words before they appear, the post screen generally just freezes sometimes, and trying to navigate (long tap) the cursor position just creates a huge mess. Sometimes I "select" words/paragraphs where there aren't even words, or the selection isn't even correctly aligned with a line.
On the other hand, the hamburger menu still has issues, but it's no longer literally driving me insane, so that's a plus.
-
@topspin Repro'd, but the general bugginess has caused me to not see it as anything out of the ordinary; I only really noticed that anything was different just now.
-
@pie_flavor You mean you actually had an error that wasn't obscured by the big red boob? Murphy must be nice to you! All my problems are behind the boob.
-
@the_quiet_one The red boob is all that lets me multi quote, though if you're already going full retard with making a giant header appear when you scroll, you may as well control the red boob when you scroll as well. I do however wish that actually using the boob did not cause page scroll to reset.
-
@pie_flavor The submit button is all that lets you actually post your reply, too. But that isn't stupidly blocking the text in my reply.
-
What's driving me nuts lately is are the menus pulling in left and right. It seems to occur especially when it takes a while loading the page.
@julianlam How hard would it be to rip out the "detect a swipe" and replace it by "tap the icon"? As a nodebb-plugin or as an option in core? I just don't ever want a swipe give me the menu/chat on mobile. (Note that it probably also requires a "close" button on the panel, i'd like to get rid of the fiddly "close it by swiping, but don't swipe too much else you'll go back/forward, so swipe three times closing it a little each time" as well).
I've never done any nodejs dev, but with a bit of direction where to start I wouldn't mind trying...
-
@robo2 pretty sure @ben_lubar added exactly that option
-
@robo2 said in Does anybody actually use this site on mobile :
close it by swiping, but don't swipe too much else you'll go back/forward, so swipe three times closing it a little each time"
- That sort of thing is exactly why I'm glad I don't use a stupid system that uses swipes for back/forward
- Just tap on the part of the screen that's not the menu
-
@jaloopa I... I... I like @ben_lubar even more now... And somehow I missed the announcement of this awesome option, but I've enabled it now, and am at the moment a happy man.
-
@robo2 Ditto. Actually went to the settings menu just now. If everything works as advertised, no more swiping or delay-loading for me.
Hooray.
-
@jaloopa said in Does anybody actually use this site on mobile :
That sort of thing is exactly why I'm glad I don't use a stupid system that uses swipes for back/forward
It actually works just fine if the site doesn't decide to hijack a feature that's already used for something else by a browser.
-
@robo2 said in Does anybody actually use this site on mobile :
@jaloopa I... I... I like @ben_lubar even more now... And somehow I missed the announcement of this awesome option, but I've enabled it now, and am at the moment a happy man.
Just for parade-raining purposes: I complained, and he decided to immediately turn it off site-wide. It was only turned into an option after blowback.
-
@topspin what if the site isn't optimised for mobile so you have to scroll horizontally? What if you've zoomed in on an image? There are so many legitimate reasons to want to scroll sideways I see it as the browser hijacking a common gesture
-
@jaloopa we must be talking past each other here.
Both of these things are how the browser reacts to your gestures per default, unless the site uses some JS to intercept it and does something different. Large images or websites, as long as they're static and don't hijack the gestures, work exactly as intended.Scrolling sideways and swiping from the edge of the screen, i.e. to go back to the last page, as done by the browser is something I've never unintentionally mixed up. It pretty much just works correctly.