Hahah it's still shit
-
Ok, we need a thread to bitch about NodeBB glitches. "Hahaha it's still shit" thread, I PICK YOU.
What's the point of the pull down menu on the Submit button? Is there ever anything here except the repeated submit button?
-
There's nothing hidden in the HTML
-
@Mention intellisense is immediately activated, you don't have to wait a minute, like on Discourse.
Good.
However, why aren't these users sorted by recent activity? I need to scroll through 10000 dead accounts to find one of the 20 active people I might ever mention in my posts.
So this is both better and worse than Discourse. Do we need another thread for that? "It's still shit, just different kind of shit" thread?
-
Don't appear to be able
-
That's @ben_lubar's sanitiser at work ;)
-
@cartman82 said:
Ok, we need a thread to bitch about NodeBB glitches. "Hahaha it's still shit" thread, I PICK YOU.
What's the point of the pull down menu on the Submit button? Is there ever anything here except the repeated submit button?
Yes.
No idea why, say, SUBMIT AS NEW TOPIC isn't in there.
-
@aliceif
That's kinda stoopid ... the dropdown should only be there for people with the right to lock it
-
@aliceif said:
No idea why, say, SUBMIT AS NEW TOPIC isn't in there.
That's on the reply button - but only on the topic one, not on the per-post ones.
-
@cartman82 said:
Ok, we need a thread to bitch about NodeBB glitches. "Hahaha it's still shit" thread, I PICK YOU.
What's the point of the pull down menu on the Submit button? Is there ever anything here except the repeated submit button?
Ick. d
-
@PJH @aliceif They should either hide the pulldown if there's only one option, or display "Submit and Lock" grayed out. They chose the worst of both worlds.
-
Right now I am seeing “150 out of 150” on the status-bar, 150 posts on the bottom bar, but the URL ends with 160. Something has a long lead here.
Filed under: The ⊕ is really obvious, yes.
-
Oh, it is not long lead. It is excluding the Deleted Posts™. Now it Makes Sense®.
-
@Bulb No, it doesn't. My bar now shows "161 out of 162", and I'm at the bottom of the thread.
-
@asdf Hm, mine does now too (161 out of 163), so it does have a long lead indeed.
-
Worked on refresh.
-
@CoyneTheDup that's because the server crashed and came back up before you refreshed.
-
Having to clear each individual notification is getting old very fast. Can it be set to clear them all when you open the menu (like Windows Phone does, for example)?
-
When you reply to someone it adds the arrow-with-name link and adds a mention at the front of the message.
Consequently, you get a notification that someone mentioned you when they actually replied to you.
If you remove the mention the reply doesn't generate a notificstion at all.
-
And some more.
Lists. It's a forum, there's loads of lists. Lists of threads. Lists of messages in threads. Lists of users. Lists of groups. Lists of users in groups. Lists of messages by users, etc. This is all list format, tabular data.
None of it has column headings, and none of it is sortable.
-
@coldandtired said:
Can it be set to clear them all when you open the menu
did it on close of the menu…
Holy heck, that's a terrifying horse emoji…
-
Is there a way to make the notification drawer taller? On Discourse it was based on screen night but it seems to be fixed height in NodeBB.
-
-
@ben_lubar Yeah, discourse had that too. I guess I really should save minor gripes like this for after all the more major stuff is dealt with...
-
@LB_ yeah, but unlike Discourse, the one on NodeBB actually loads within an average human lifetime.
-
Ah good point. I guess it's worth the extra click if the page loads so much faster.
-
@LB_ said:
Is there a way to make the notification drawer taller? On Discourse it was based on screen night but it seems to be fixed height in NodeBB.
You could adjust
max-height
for.notification-list
in CSS.
-
/notifications is almost useless. It reloads every time a notification arrives, which is almost constantly, so it's blank much of the time. (Thanks, @ben_lubar , for all the notifications for upvoting everything in The Official Likes Topic.)
-
@HardwareGeek I'm like 1/7 of the way caught up. And the forum hasn't shown a single 503, so that's a good sign at least.
-
@HardwareGeek said:
/notifications is almost useless. It reloads every time a notification arrives, which is almost constantly, so it's blank much of the time. (Thanks, @ben_lubar , for all the notifications for upvoting everything in The Official Likes Topic.)
You know... Maybe we shouldn't refresh the page if mouse is over the main content div...
-
- Upload an avatar
- Later, go in to upload another avatar
Two variations
- Select upload new picture
- Picture changes back to original avatar
- Save
- Still shows old avatar until you refresh
Second variation
- Select avatar picture
- Delete old picture
- Upload new picture
- Save
- Restores display of old avatar, the one deleted, until you refresh
-
@julianlam Any regrets yet?
-
@julianlam said:
You know... Maybe we shouldn't refresh the page if mouse is over the main content div...
Do you have something against injecting stuff into DOM other than it being slightly harder to do? I notices quite a few situations where there's a refresh that could probably be avoided with some smart template management.
-
@Onyx said:
Do you have something against injecting stuff into DOM other than it being slightly harder to do?
If one is going to do that, one has to be careful. Discourse used Ember to do the HTML manipulation, and that was Bad because that was the cause of the jellypotatoing. The problem was that it was triggering some sort of reparse by the browser, and that was in turn triggering a scroll up to the top of the current visible content and that in turn caused the rest of the trouble because scrolling to the top triggered a load of more content which triggered the parsing problem again.
The was by far the worst user-visible aspect of DC towards the end.
-
"Return to last unread post" toaster took me to three posts from the bottom of the Status thread (which I hadn't caught up with in over 24 hours and I did scroll up to check we hadn't just stopped posting in it).
It occurs to me that it did say last unread post, not first, so maybe it is behaving as designed, but...
-
I agree with @tufty. this is just more responsive shit.
*edit pic from just after first login. Not very impressed.
-
@Onyx said:
I notices quite a few situations where there's a refresh that could probably be avoided with some smart template management.
he could use ember and handlebar
-
@asdf said:
@RaceProUK said:
Darkly's a good theme; dark without being like staring into the infinite abyss
It is, but it breaks the "go to last unread post" toaster. That one's just white now.
Same problem with Cyborg. Clicking/tapping the white toaster still works though.
-
@julianlam said:
Maybe we shouldn't refresh the page if mouse is over the main content div...
I think not automatically refreshing the page at all would be good. Like how if you're looking at the list of unread topics, you get a little bar saying, "There are new posts." Or whatever. So you can click to refresh it if you want, or just use the list as-is until you're ready for that.
-
@boomzilla said:
Like how if you're looking at the list of unread topics, you get a little bar saying, "There are new posts."
About that, it has a habit of appearing in the exact millisecond before I click on the first topic in the list, meaning I click on it instead. It shouldn't shift the topics around.
-
@LB_ Yes, though if we didn't use that bar, and updated the topics list every time a new post was made, then you'd really never be able to click on a post with confidence that the DOM element will actually stay put under your mouse
-
Perhaps that element should just be invisible, taking up space? Then I imagine people would complain about the extra space being taken up
-
@julianlam A compromise: Make it smaller but keep it invisible.
-
@julianlam They would. IIRC, we had the same issue on Discourse. Not having stuff jump away is definitely worth a little whitespace.
-
@boomzilla said:
IIRC, we had the same issue on Discourse.
Discourse shows it over the header row.
I guess we don't have one here but there's plenty of empty space there to fill.
-
-
@DogsB See, I have that too, I assumed it was due to browser zoom being on which is a science-fiction new-fangled invention the NodeBB developers are apparently not aware of
-
@boomzilla said:
Like how if you're looking at the list of unread topics, you get a little bar saying, "There are new posts."
That's great, except for it moves links out from under your mouse cursor, causing you to click the wrong link.
-
@julianlam How about you just don't move widgets out from under the mouse at all? I know, I know, crazy idea.
-
@boomzilla said:
@julianlam said:
Maybe we shouldn't refresh the page if mouse is over the main content div...
I think not automatically refreshing the page at all would be good. Like how if you're looking at the list of unread topics, you get a little bar saying, "There are new posts." Or whatever. So you can click to refresh it if you want, or just use the list as-is until you're ready for that.
If you no longer automatically update the page (whichever page that is), and instead require the user to take an action, you are doing the same as the "toxic hellstew" forums "of old" which require the user to click the reload button / F5 / ⌘-F. The only enhancement you're providing is a "refreshing now will load new content" indicator, which actually becomes a "reload content NOW!"
-
@tufty said:
If you no longer automatically update the page (whichever page that is), and instead require the user to take an action, you are doing the same as the "toxic hellstew" forums "of old" which require the user to click the reload button
Not at all.
@tufty said:
The only enhancement you're providing is a "refreshing now will load new content" indicator, which actually becomes a "reload content NOW!"
It also loads faster (generally) than a full page refresh. Plus you don't have to guess that something has changed.