Blakeyrat pointing out NodeBB problems
-
@bb36e We already have a perfectly fine arrangement where we offload those to Ben L and then he does absolutely nothing with them. Everything has to be broken at every level.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
I am illiterate.
Whose tentacles are you using with which to write your posts?
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
We already have a perfectly fine arrangement where we offload those to Ben L and then he does absolutely nothing with them.
That's not true at all.
He uses them to randomly seed his Dwarf Fortress AI.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
Well they're wrong.
No, it's not a bug, it's a feature. It just isn't the feature you want. Discourse had two features, one to ignore everything and another to ignore some things — background chatter — while not ignoring someone talking directly to you. You want one; other people want the other. Unfortunately, for some reason, :nod: only implements one. It's not the one you want, but that doesn't make it a bug, at least not in the mind of anyone but you. "They implemented a feature, but it's not the feature I want, so it's a bug. Waaaa." No, you're the one with the wrong definition of "bug."
That said, it would be nice to have both. Most of the time, I want the version that notifies me if someone is talking to me, but there's certainly a valid use for the other one.
Edit: However, if it says it does one but actually does the other, that's a bug a needs to be fixed.
-
@HardwareGeek said in Blakeyrat pointing out NodeBB problems:
Edit: However, if it says it does one but actually does the other, that's a bug a needs to be fixed.
As if they'd ever write documentation! Hah
-
@boomzilla said in Blakeyrat pointing out NodeBB problems:
@Zecc said in Blakeyrat pointing out NodeBB problems:
For the benefit of those on mobile, that's
:shrug_jaundiced:
For the benefit of those who have to use NodeBB, that's
:shrug_jaundiced:
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
@Tsaukpaetra How "fix"-y it is. Good job avoiding regressions, NodeBB.
It isn't a regression. It's just a fix that broke something else.
-
@Lorne-Kates
Sounds like the difference between ginger ale and ginger beer.
Let's just give that ginger girl another Guinness.
-
@Lorne-Kates Yeah well it's really fucking annoying.
-
@ben_lubar When is this regression going to be fixed? It's really fucking annoying.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
@ben_lubar When is this regression going to be fixed? It's really fucking annoying.
What do you suggest I do? Take buttons out of the header? Go back to the old way where it pushed itself off the screen and made reading the top of the page impossible?
-
@ben_lubar IT PUSHES ITSELF OFF THE SCREEN NOW! THAT IS THE EXACT BUG I AM REPORTING!
Why don't you collapse down the part where it says "What the DailyWTF?" that'll save a couple hundred pixels. Do we need SEVEN top-level navigation tabs? How about making 2 useful ones and putting the rest in an expando? I'm not Mr. Stylesheet, I just know the damned thing doesn't work right now.
Even a shitty horrible horizontal scrollbar would be better than how it works now.
-
in any case, no repro on the menu being too wide:
-
@ben_lubar Blakey isn't real, stop arguing with him I am waving a stopwatch in front of your eyes in order to hypnotize you.
-
Red = Useless
Orange = Mostly Useless
Yellow = Useless if you're not using the feature
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
Red = Useless
Orange = Mostly Useless
Yellow = Useless if you're not using the featureThe What the Daily WTF text isn't useless, that is how I get to the homepage.
-
@XanderTheGamer said in Blakeyrat pointing out NodeBB problems:
the homepage.
What's that?
Seriously though the icon already links there. You can just click the icon.
And again: I AM NOT A UX DESIGNER, I do not know what it should look like. I just know if you were trying to fix "it goes off the screen" then you UTTERLY FAILED TO FIX IT BECAUSE IT STILL GOES OFF THE SCREEN.
-
@XanderTheGamer said in Blakeyrat pointing out NodeBB problems:
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
Red = Useless
Orange = Mostly Useless
Yellow = Useless if you're not using the featureThe What the Daily WTF text isn't useless, that is how I get to the homepage.
did not know the text works too, I use
-
@dse said in Blakeyrat pointing out NodeBB problems:
@XanderTheGamer said in Blakeyrat pointing out NodeBB problems:
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
Red = Useless
Orange = Mostly Useless
Yellow = Useless if you're not using the featureThe What the Daily WTF text isn't useless, that is how I get to the homepage.
did not know the text works too, I use
I just find it easier, since I just need to go to the upper left of the page.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
Red = Useless
Orange = Mostly Useless
Yellow = Useless if you're not using the featureYou forgot to put red around the magnifying glass.
Search is useless...
-
Why the hell was I sent to the Evil Ideas Thread after submitting the previous post?
-
@Zecc Maybe it's trying to tell you something.
-
@blakeyrat the text is not useless. I use it to get to the forum homepage. If anything, the category button is useless because I never use it.
-
@bb36e said in Blakeyrat pointing out NodeBB problems:
If anything, the category button is useless because I never use it.
I use the category button a lot. When I was doing the stuff for ignoring threads, some people over at community.nodebb.org wondered why I was wasting my time because Unread was useless and nobody uses it.
-
@boomzilla said in Blakeyrat pointing out NodeBB problems:
Unread was useless and nobody uses it.
-
@blakeyrat I have more buttons than you, and even when I'm zoomed in, I still have all the buttons visible.
-
@ben_lubar Ok well I don't, so the forum's buggy.
Not sure what kind of reply you're looking for here.
-
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
@blakeyrat I have more buttons than you, and even when I'm zoomed in, I still have all the buttons visible.
There are size ranges where the CSS is faulty and hides buttons.
@ben_lubar : Try making your window narrower, starting from full screen width. You'll notice it.
-
@aliceif said in Blakeyrat pointing out NodeBB problems:
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
@blakeyrat I have more buttons than you, and even when I'm zoomed in, I still have all the buttons visible.
There are size ranges where the CSS is faulty and hides buttons.
@ben_lubar : Try making your window narrower, starting from full screen width. You'll notice it.~764 to ~880 px on 100% zoom is a pretty fucking huge range of brokenness. Wouldn't that mean that having two windows on a 1680x1050 screen side-by-side would lead to unusability?
-
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
I have more buttons than you, and even when I'm zoomed in, I still have all the buttons visible.
I think the recent changes aren't playing nice with unresponsive desktop mode.
-
@aliceif Ben L seems to think anybody who uses the zoom feature of their browser is a horrible monster who deserves death. That adds to the difficulty here.
-
@blakeyrat For what it's worth, you're not the only one. I also use browser zoom. At the highest resolution (which is also the only one where shit actually looks right), everything tends to get very small. Most noticeably, stuff in web browsers. I have to jack it up to 125% so I can actually read things comfortably.
-
So what should we do? Go back to having the header hide the page? Go back to cutting off tooltips?
-
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
So what should we do
Maybe start by figuring out why
@aliceif said in Blakeyrat pointing out NodeBB problems:
~764 to ~880 px on 100% zoom is a pretty fucking huge range of brokenness.
and fix that?
-
@Yamikuronue said in Blakeyrat pointing out NodeBB problems:
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
So what should we do
Maybe start by figuring out why
@aliceif said in Blakeyrat pointing out NodeBB problems:
~764 to ~880 px on 100% zoom is a pretty fucking huge range of brokenness.
and fix that?
764px: looks fine to me
768px: avatar off the side, but that can be fixed by removing menu buttons or changing the site title in the header
880px: looks fine to me
-
@Yamikuronue I assume part of the problem lies with using the Unresponsive plugin, mainly in that, in order to stop "mobile mode" from happening, it has to strip out all width conditional CSS, which includes the CSS to make the top nav items narrower, so certain window widths that wouldn't have issue with the plugin off do have the same issue when it's on.
For reference, this is the CSS for that:
@media (max-width: 1199px) .nav>li>a { padding-left: 5px; padding-right: 5px; }
-
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
768px: avatar off the side, but that can be fixed by removing menu buttons or changing the site title in the header
880px: looks fine to meDo those widths really need the navigation controls at both the top and the bottom of the viewport?
-
@ChaosTheEternal said in Blakeyrat pointing out NodeBB problems:
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
768px: avatar off the side, but that can be fixed by removing menu buttons or changing the site title in the header
880px: looks fine to meDo those widths really need the navigation controls at both the top and the bottom of the viewport?
Oh, oops. I'll fix that in today's update.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
seems to think
I thought you didn't have telepathy.
-
https://what.thedailywtf.com/topic/20381/mafia-8-club-ded/143
It's impossible for me to ignore this thread, because every time I scroll down to use the Ignore menu, the page skips back up to post 143. I don't know what's so special about post 143.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
I don't know what's so special about post 143.
Weird. I've seen that from time to time, and waiting on that post for a while for the jellypotato to catch up usually eventually let me scroll farther. I can't repro it on that thread, though.
Anyone else I'd ask if they were willing to replace 143 in the address bar with 1040, which is almost the last post, but I know you don't like unsolicited suggestions, so...don't do that.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
every time I scroll down to use the Ignore menu, the page skips back up to post 143.
No repro on scrolling down (or up) redirecting to post 143. By the way, how'd you read 100+ posts in a topic you wanted to ignore and not notice the ignore button was at the top of the thread?
-
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
and not notice the ignore button was at the top of the thread?
Liar. There are two ignore buttons in topics with more than 1 post. Blakeyrat did NOT look at the wrong end of the topic.
And until now, I didn't know that there was one at the top.
-
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
By the way, how'd you read 100+ posts in a topic you wanted to ignore and not notice the ignore button was at the top of the thread?
I guess because I'm a stupid fucking retard moron. If a person doesn't find a widget in the software, obviously the person is to blame because software is always perfect and godlike.
Here's a question for you: why does ignoring a topic require using widgets in EITHER the top or bottom posts? Why isn't the ignore widget ON THE PAGE AND NOT PART OF THE SCROLLABLE AREA? Like makes sense?
"Oh I need to close this Chrome tab."
"Well the tab close box is either at the bottom of the page or top, so start scrolling."
"But the operation applies to the entire page, why should it be inside the page content?"
"IT JUST IS SHUT UP!"
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
https://what.thedailywtf.com/topic/20381/mafia-8-club-ded/143
It's impossible for me to ignore this thread, because every time I scroll down to use the Ignore menu, the page skips back up to post 143. I don't know what's so special about post 143.
Ignore the "latest game" category.
-
How, @ben_lubar , how? How!
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
How, @ben_lubar , how? How!
Maybe because tables don't have borders by default? This isn't a NodeBB problem...
-
@Tsaukpaetra So the table has no border, and this explains why the text I typed in the input box under the table appears in the preview box over the table?
Or are you just being a stupid retarded moron right now?
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
@Tsaukpaetra So the table has no border, and this explains why the text I typed in the input box under the table appears in the preview box over the table?
I don't see a
</table>
in your screenshot.
-
@ben_lubar And therefore all rules of time and space go out the window?