Good jorb NodeBB
-
@ben_lubar said in Good jorb NodeBB:
As far as I know, browsers do not expose their zoom level to the page's CSS.
THEREFORE IT IS NOT A BUG!!!!!
Is that what you're trying to say Ben?
Look, I'm sorry they picked such a shitty display layer for their app, but they made their bed and now they have to fucking lie in it. Don't make excuses for bugs. You're the reason we have buggy shitty software all over the place.
-
@ben_lubar said in Good jorb NodeBB:
@blakeyrat said in Good jorb NodeBB:
Because the shitty code the morons who wrote this site uses doesn't account for browser zoom which calculating its pixel widths.
As far as I know, browsers do not expose their zoom level to the page's CSS.
Which is probably why sites shouldn't use pixel-based
windowviewport width for layouts, natch .
-
@boomzilla said in Good jorb NodeBB:
@jbert said in Good jorb NodeBB:
@boomzilla said in Good jorb NodeBB:
@blakeyrat said in Good jorb NodeBB:
- Be logged in
- Have some amount of unread topics (possibly requires more than 9 so it's a 2-digit number)
- Click the "Recent" link in the header
This does not seem to happen in "Desktop Mode," but I can reproduce when I go back to the broken default responsive mode.
(To switch, click on your avatar in the upper right corner to bring up the menu. The desktop / responsive options should be below the Logout entry.)
Interesting. I could enable the "Desktop Mode" but now I can't go back because the menu no longer shows the radio buttons.
So... How do you switch back to responsive?
Um...they should still be there! But...this is all stored in local storage, so you should be able to remove the plugin's entries...with are...um...
responsive
andunresponsive-settings
. Then try refreshing.Alternatively, do you have any errors in the console? FYI, code for this is here.
Oh damnit, my console appears to be full of errors about missing the
Nodelist.forEach
function defined in some version of the living HTML standards, that thingy still hasn't made it into PaleMoon yet which apparently triggers all kinds of funky behaviour. One of them is that the "user menu" builds as usual but stops just short of the responsive radio buttons.Do you ever test on Internet Explorer or PaleMoon BTW?
EDIT: And now I think about, even if Lorne would like to come back he won't be able to open this site in FF 22 thanks to fun stuff like that.
-
@blakeyrat said in Good jorb NodeBB:
No; I had the zoom set to 125% so it wasn't 3 pixels, it was something like 300 pixels, which made the window wide enough so that paragraphs didn't flow right and were too difficult for me to read.
'Doctor, it hurts when I do this!'
'Then don't do that.'Guys, I found a new bug. If you make the browser window only a few pixels tall, then all you can see is the title bar.
-
@boomzilla said in Good jorb NodeBB:
@izzion said in Good jorb NodeBB:
@jbert
I can't switch to Desktop Mode successfully via Safari on my iPhone, but when I switch on my computer, the option for switching back is located under the user icon menu.You pretty much should not switch to desktop mode on a phone. That's why there's a popup dialog where you have to confirm the switch. I guess that isn't being rendered correctly there?
It is for me, iOS 11.1.2 safari, iPhone 6.
-
@masonwheeler said in Good jorb NodeBB:
@izzion said in Good jorb NodeBB:
@boomzilla
It feels oh so good. I warm my soul with the flames of rage from all the lesser mortals who cannot afford an iPhone and pretend that Android is better so they don't feel depressed about about their non-iPhonedness.I can afford an iPhone. I choose to use Android instead, because I don't want a horrible device made by iDiots for iDiots.
There are 4 things that will always be true when it comes to @masonwheeler:
- He will always get triggered about hyper trains.
- He will always get triggered about tests.
- He will always downvote you.
- He will always look for an opportunity to repeat his lame iDiots joke.
Hah! I have you pretty much nailed down, mister! :smiling_face_with_open_mouth:
-
@kt_ one might say he's hyper loopy
-
@jbert said in Good jorb NodeBB:
Do you ever test on Internet Explorer or PaleMoon BTW?
I don't think any of my code uses
Nodelist.forEach
. Not explicitly. I'm too lazy for shit like that. I just use jQuery for shit like that.
-
@ben_lubar said in Good jorb NodeBB:
WHY DO WE NEED A SPECIFIC GROUP THAT PRESUMABLY MEETS TO DO THIS
It made more sense when it got started several decades ago.
-
@boomzilla said in Good jorb NodeBB:
@jbert said in Good jorb NodeBB:
Do you ever test on Internet Explorer or PaleMoon BTW?
I don't think any of my code uses
Nodelist.forEach
. Not explicitly. I'm too lazy for shit like that. I just use jQuery for shit like that.Is there something like a static analyzer for TypeScript that will tell me if something I'm doing doesn't work in a specific browser? I feel like that would be the perfect way to develop JS for the web. Strong typing, plus you don't need compatibility shims.
-
@ben_lubar said in Good jorb NodeBB:
@boomzilla said in Good jorb NodeBB:
@jbert said in Good jorb NodeBB:
Do you ever test on Internet Explorer or PaleMoon BTW?
I don't think any of my code uses
Nodelist.forEach
. Not explicitly. I'm too lazy for shit like that. I just use jQuery for shit like that.Is there something like a static analyzer for TypeScript that will tell me if something I'm doing doesn't work in a specific browser? I feel like that would be the perfect way to develop JS for the web. Strong typing, plus you don't need compatibility shims.
So basically CanIUse in intellisense form?
-
@ben_lubar said in Good jorb NodeBB:
As far as I know, browsers do not expose their zoom level to the page's CSS.
It's easy as fuck to find out.
static getResolution(): ResolutionData { if (this.resolutionCache) { return this.resolutionCache; } // Create 1" square div using points var resolutionDiv: HTMLDivElement = document.createElement("div"); resolutionDiv.style.height = "72pt"; resolutionDiv.style.width = "72pt"; resolutionDiv.style.visibility = "hidden"; document.body.appendChild(resolutionDiv); // Retrieve pixel measurements var result: ResolutionData = <ResolutionData> { horizontalResolution: resolutionDiv.offsetWidth, verticalResolution: resolutionDiv.offsetHeight, } // Remove the test element resolutionDiv.parentNode!.removeChild(resolutionDiv); this.resolutionCache = result; return result; }
You're fucking welcome.
-
@blakeyrat said in Good jorb NodeBB:
@ben_lubar said in Good jorb NodeBB:
As far as I know, browsers do not expose their zoom level to the page's CSS.
It's easy as fuck to find out.
static getResolution(): ResolutionData { if (this.resolutionCache) { return this.resolutionCache; } // Create 1" square div using points var resolutionDiv: HTMLDivElement = document.createElement("div"); resolutionDiv.style.height = "72pt"; resolutionDiv.style.width = "72pt"; resolutionDiv.style.visibility = "hidden"; document.body.appendChild(resolutionDiv); // Retrieve pixel measurements var result: ResolutionData = <ResolutionData> { horizontalResolution: resolutionDiv.offsetWidth, verticalResolution: resolutionDiv.offsetHeight, } // Remove the test element resolutionDiv.parentNode!.removeChild(resolutionDiv); this.resolutionCache = result; return result; }
You're fucking welcome.
Except that doesn't work and will never work according to the spec:
-
@ben_lubar Ok well then I guess it's ok that it's broken shit garbage all the time.
-
@blakeyrat have you tried making a pull request?
-
@pie_flavor Yes.
-
@boomzilla said in Good jorb NodeBB:
Why would Germans want to say that?
You are right. It's 2018! They should use Das Das Das and stop assuming the gender of the.
-
@luhmann said in Good jorb NodeBB:
It's 2018! They should use Das
It's 2018, nobody uses CLI anymore
-
For what it's worth, I've seen another thread about the same bug but in the notification icon (here).
Also I am with @blakeyrat on this one, I have the issue on both the unread and the notifications and it is (mildly) annoying. Yes, it does go away if I reduce the zoom factor of the browser (and therefore switch back to desktop, I assume?), but that is no excuse for it. Especially since it was working a few weeks ago, so it's a regression, not something that never worked.
-
So, has anyone seen this since I removed our header customizations?
-
@ben_lubar I don't think I saw it, but I do know the topic bar thing tends to overlap in-topic-search controls.
-
@polygeekery said in Good jorb NodeBB:
@blakeyrat said in Good jorb NodeBB:
This is still a hugely critical bug for NodeBB that completely and utterly destroys their first-run experience for a large proportion of users that they've never made any attempt to fix.
A large proportion of users have their windows 3px too narrow?
I tend to be the type of developer that tries everything, somehow.
When I was with that web dev outfit, I was working on a web page and was resizing the window width to make sure my page stayed consistent. I hit a certain width and everything borked. EVERYTHING.
When I showed it to them, "No one is going to use that width."
Right, but all it will take is someone dragging the window size down, seeing that, and being totally thrown off by the page.
@blakeyrat said in Good jorb NodeBB:
decided that they'd determine whether you were on a desktop computer based on the width of the window.
Far far far too common, sadly enough.
So, when tablets get large enough pixel widths, it will all break... oh wait, my phone already breaks those websites. It's not like anyone could see it coming though... right?
-
@ben_lubar For me it seems fixed. Thanks!
-
@xaade there is more shitty websites than decent ones, even accounting only for the popular ones.
-
@boomzilla said in Good jorb NodeBB:
m...they should still be there! But...this is all stored in local storage, so you should be able to remove the plugin's entries...with are...um...responsive and unresponsive-settings
...
...
...
so the same bullcrap that produced a completely separate bug I reported the instant I decided to try to use the forum again?
...
NodeBB!
-
@lorne-kates said in Good jorb NodeBB:
so the same bullcrap that produced a completely separate bug I reported the instant I decided to try to use the forum again?
It would seem to be so.
-
@boomzilla said in Good jorb NodeBB:
@lorne-kates said in Good jorb NodeBB:
so the same bullcrap that produced a completely separate bug I reported the instant I decided to try to use the forum again?
It would seem to be so.
Good jorb.
-
-
@boomzilla said in Good jorb NodeBB:
Works on my morbchine.
Is that where Morbs is being held prisoner?
-
@masonwheeler Bring morbs back, he was crazier than blakey and boomzilla combined.
-
@pie_flavor said in Good jorb NodeBB:
I have never met a single person who uses their web browser in anything other than maximized.
Hello there. Now you have met one.
Unless you are using a very small screen, running a web browser maximized is retarded. Double Extra Retarded on my 32 inch 4k monitor.
-
@topspin Why are you telling me to bring him back? I'm not the one holding him prisoner in a morbchine!
-
@ben_lubar said in Good jorb NodeBB:
Right now I'm using a Chromebook (Edgar) to interact with my Windows 10 computer (GODZILLA) over remote desktop, through which I am using an SSH session to an Ubuntu Xenial (16.04) machine (australium) which is currently connected to a Docker container (wtdwtf-nodebb-postgres) running Debian Stretch (9).
-
@masonwheeler said in Good jorb NodeBB:
@topspin Why are you telling me to bring him back? I'm not the one holding him prisoner in a morbchine!
Ah, he's in your dhromebook, then?