Blakeyrat pointing out NodeBB problems
-
@fbmac said:
@RaceProUK I am still shocked he uses chrome instead of IE
I am still shocked he is able to hold down a job and communicate here on the forums with Bill Gates' cock perpetually in his mouth.
-
@Polygeekery he would be great or at least a lot of fun at mafia
-
-
@RaceProUK said in Blakeyrat pointing out NodeBB problems:
You're
@fbmac said in Blakeyrat pointing out NodeBB problems:
am
@Polygeekery said in Blakeyrat pointing out NodeBB problems:
cock
I hate you guys SO MUCH. I'm just trying to read some posts on this god damn forum, but instead all this zero-content nattering.
@boomzilla said in Blakeyrat pointing out NodeBB problems:
out
-
@Buddy said in Blakeyrat pointing out NodeBB problems:
all this zero-content nattering.
The worst part is I have no way of muting or ignoring the goddamned thread.
-
@blakeyrat I read your complaints imagining your tone like in your videos, were you seem to be having lots of fun trash talking those games
-
I actually liked the information-less YouTube URLs better than the information-less grey box with play button YouTube embeds. Both are equally information-less, but the former takes up a lot less space.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
The worst part is I have no way of muting or ignoring the goddamned thread.
That's not entirely true, though, is it?
-
@blakeyrat Yeah, the plugin we're using didn't seem to do a good job picking the picture to show. I think it is hard coded to link the big one whether it exists or not.
When I get back to a keyboard, I'm planning on taking a look at that.
-
On this thread:
https://what.thedailywtf.com/topic/19489/just-thanks
Either my read marker got erased, or the code to "auto-scroll" down to the last-read position failed, and there's no more pop-up to allow me to skip to the last-read position.
-
For some reason "Mark All As Read" has started taking forever. I just tried it and the browser was locked-up for a good 9-10 seconds.
-
Prefect!
-
Uh, on that note, wtf is it sending the full sized images as avatars? Would it not make sense to send scaled down versions more suited to how they're going to be displayed?
-
@calmh Depends on whether they are being displayed on a HighDPI display or not. High-res images are very nice to have when you've got the pixel density to make good use of them (and network bandwidth to cope).
-
@dkf Well... I'm on a high DPI display, but the images sent are 360x360 and rendered at 46x46 which is a tad higher multiplication factor than my display has.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
The bug is simple: I do not want to see mobile view on a desktop computer
It's not a mobile view, it's a small screen/viewport view. It happens to be mostly seen on a mobile, but the point is to be usable in a small window. This particular implementation goes overboard in that attempt and mostly fails, but the intention is there.
@sloosecannon said in Blakeyrat pointing out NodeBB problems:
Yeah, he's been saying that. I'm not quite sure if he realized he's doing the math for that backwards
He's saying that when you're zoomed the change kicks in at 1237 pixels, not 990, surely? You all seem to be talking about the number of reported pixels when the browser is at 990, which is irrelevant because that's not when the layout change happens
-
@Jaloopa There seems to be a lot of confusion about browser sizes, not helped by a complete misunderstanding of how the browser zoom affects it.
What is happening is, with a browser window that is 1000px wide, the viewport is 1000px wide*. When browser zoom is enabled, the viewport is still 1000px wide. However, if you're using a WebKit browser, there is a bug where it applies the browser zoom incorrectly; at 120% zoom, where Firefox, IE, and Edge all have a viewport of 1000px, Chrome, Safari, and Opera (all the WebKit browsers) mistakenly thinks its viewport is 800px wide. This falls below the 992px transition point, so the 'mobile' view appears.
TL;DR: there's a WebKit bug that messes up the CSS media queries.
And now to wait for His Ratiness to scream about how it's nothing to do with browser widths and how a bug in WebKit is the responsibility of the NodeBB team and how Firefox, IE, and Edge are also affected by the WebKit bug, even though they use either Gecko or Trident instead.
*I'm ignoring window borders to keep things simple.
-
@RaceProUK said in Blakeyrat pointing out NodeBB problems:
where Firefox, IE, and Edge all have a viewport of 1000px, Chrome, Safari, and Opera (all the WebKit browsers) mistakenly thinks its viewport is 800px wide
Yeah, so the 990px transition doesn't happen at 990px but at 990+n where n is some number I can't be arsed to work out right now because I have a 6 week old baby and therefore very little sleep.
Seems like that's the number @blakeyrat is talking about, but other people are determined to misunderstand him and are taking his assertion precisely the wrong way.
-
@Jaloopa said in Blakeyrat pointing out NodeBB problems:
Yeah, so the 990px transition doesn't happen at 990px but at 990+n where n is some number I can't be arsed to work out right now because I have a 6 week old baby and therefore very little sleep.
That's not what I said, but I'll let you off ;)
I'll try to make it a bit clearer:
- The transition happens at a viewport width of 992px (it's a standard Bootstrap rule).
- When the window is 1000px wide, Firefox, IE, and Edge correctly think the viewport is 1000px wide.
- However, Chrome, Safari, and Opera (all WebKit browsers) mistakenly think the viewport is 800px wide, when it's actually 1000px.
Ultimately, it's a bug in WebKit triggered by the fact Bootstrap 3 has to rely on pixel widths in media queries because IE8.
-
@RaceProUK said in Blakeyrat pointing out NodeBB problems:
However, Chrome, Safari, and Opera (all WebKit browsers) mistakenly think the viewport is 800px wide, when it's actually 1000px.
How is that different to what I said? Webkit browsers think the viewport is 992 pixels when the actual window is somewhere north of 1000. So to a user with a zoomed Webkit browser, the transition to mobile mode doesn't happen when they size it down to 992, it happens at 1200 odd. Which is exactly what @blakeyrat was saying and other people are deciting to misrepresent.
To be clear, I'm not arguing that this isn't a Webkit bug, just trying to clarify soem shit that seems to be going at cross purposes
-
This post is deleted!
-
@Jaloopa said in Blakeyrat pointing out NodeBB problems:
How is that different to what I said? Webkit browsers think the viewport is 992 pixels when the actual window is somewhere north of 1000.
I guess it isn't different to what I said; I just used different numbers
-
Huh.
-
If you use the mousewheel to scroll the notifications pull-down, when that scrollbar hits the bottom the entire window scrolls, which also happens to close the notifications pull-down.
-
This happens to me too on Chrome, but not on IE and Firefox. Basically, you scroll down and it just goes poof.
[EDIT: Firefox too, so just IE is working now. (never thought I'd actually say that O.O)]Firefox, however, does seem to mess up a lot of CSS. (unrelated issue, of course.)
-
@RaceProUK said in Blakeyrat pointing out NodeBB problems:
it's a bug in WebKit
But Firefox and Chrome switch at essentially the same point.
Here are Firefox (at 120%) and Chrome (at 125%). Firefox on top, Chrome behind.
This is the point they both switch to mobile view - it's only slightly wider for Chrome, and by the time the difference in zoom level is accounted for, then it's essentially the same.
-
@loopback0 Firefox on OSX, right? Is that one of those Firefoxes that actually uses WebKit? I know the iOS one does.
-
@RaceProUK Yes but I got the same when I tried it on Windows the other day.
I don't think OSX is subject to the same retarded lockdown as iOS so I think Firefox is actually Firefox.
edit: Yes, Firefox OSX is Gecko not Webkit.
-
@loopback0 Hmm... I will admit that article I linked to above isn't the freshest; it's possible Gecko has subsequently been changed to match WebKit.
I wonder if the same happened to Trident...
-
@RaceProUK And Windows, for reference.
Firefox and Chrome:
IE11 and Chrome (both at 125%) switch at the same point:
That's about 1200px for it to switch to mobile if zoomed to 120/125%.
-
@loopback0 Awesome.
So not only was RaceProlapse bitching about something entirely unrelated to my bug, but she was also DEAD WRONG.
I love this forum.
-
@blakeyrat Ah yes, I forgot that software never changes and never gets updated
-
Personally, I don't care if the switch from "desktop" to "mobile" mode happens at 992 actual pixels, 992 pretend pixels, or 99.2 unicorns : I'm on a fucking desktop machine, and I want a desktop view. I do not want a retarded touch-specific view.
For mobiles, use a different fucking URL, or something in the URL "path" to trigger mobile view.
-
I have a magic notification I can't see. The notifications menu is blank. The "See All Notifications" page is also blank. Yet there is a little red "1" there, taunting me.
-
@blakeyrat they turned them off because some think the notifications might be the cooties causer
-
@darkmatter Then why is the "1" there?
-
@blakeyrat stale notification from before they zapped it maybe.
-
@darkmatter I had a "1" too, but once I clicked the icon the "1" vanished.
-
@darkmatter Gee, it's almost as if this post in "pointing out NodeBB problems" points out a problem in NodeBB. But that's unpossible.
-
@blakeyrat interestingly, it sent me a notification telling me that you responded, and a "1" very briefly appeared in the box.
so notifications only seem to be very partially neutered....
-
@darkmatter Quick! Better come up with a new way to call me wrong and stupid! The old one isn't working anymore.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
Gee, it's almost as if this post in "pointing out NodeBB problems" points out a problem in NodeBB.
This is the only way we could get your input on new forum software.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
The old one isn't working anymore.
Works for me.
-
@blakeyrat I don't recall saying anything like that, in fact I agreed with you.... has it been so long since you said something that was right that you entirely forgot what it's like to have someone agree?
-
@darkmatter You did not agree with me that it was a bug. You "explained" it away by saying that notifications are off, without bothering to engage enough neurons to realize that if notifications really are off showing me the red 1 is a goddamned bug.
But whatever. Go ahead and rewrite history.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
You "explained" it away by saying that notifications are off
I told you notifications are off, because a person in control said that they turned them off. I even included a picture of them saying such, so you'd know I'm not just speculating or explaining away your "bug".
But go ahead, rewrite history.
-
@darkmatter Point of note: I'm not in control of anything here (and I want it to stay that way!); I was just reporting what @ben_lubar had done
-
@blakeyrat I'm pretty sure that "notifications are off" is an intentional hackjob fuck-its-broken-in-production workaround, not a feature.
If it's any consolation, it's driving me positively insane too.
-
@RaceProUK well whatever. Blakey said it's broke, i told him why it's broke. It's pretty simple really.
-
@Weng i deem them permanotifications.