@ben_lubar shouts at @accalia
-
@ben_lubar said in @ben_lubar shouts at @accalia:
WOULD YOU LIKE TO JOIN ME IN SHOUTING, @BOOMZILLA? HOW HAS YOUR DAY BEEN TODAY?
IT'S SO NICE THAT YOU MADE THIS "EASY TO READ" TOPIC FOR THE OLD TIMERS LIKE @boomzilla
-
@Arantor said in @ben_lubar shouts at @accalia:
I got 1.1875 in Mobile Safari, iOS 9.3.5 I think it is.
inb4 idiot, kthx.
You didn't say "Surface" or Win10, so no idiot for you.
-
So far:
I got 1.1875 in Mobile Safari, iOS 9.3.5 I think it is.
1.2, Crome 53.numberz
1.2 on mobile chrome
1.5, Firefox Developer Edition (v50)
1.5, Firefox for Android (v48)
FF 48 — 1.5.
1.5 ff22
1.170625 IE1134 different results across34 different browsers. (sidenote: The one time I was willing to accept it was just ff22... ha, vindicated again).Anyways... the
big
ger question for me is-- why does it matter?What weird css crap is NodeBB doing that means the text in my original screenshot gets cut off? Aren't
h1
andbig
block elements? Shouldn't the top of their box model be the top?Or is NodeBB making some buttumptions about what it feelz the font size should be, and is hard coding some negative margin somewhere because raisins?
-
@ben_lubar said in @ben_lubar shouts at @accalia:
https://jsfiddle.net/qeLoo6xv/
Let's do an experiment: click on the Result tab and post the number it says here with your browser and browser version.
1.170625 IE11
Edge have exactly the same result.
-
Btw, here's a message from the W3C.
[quote]
The element is a non-standard element.
No, really, don't use it.
[/quote]The size of H1 doesn't matter as long as it can show the section rank with H2, H3, etc. correctly. Using it for the purpose of shout is
Explicitly use font-size CSS instead.
-
@ben_lubar said in @ben_lubar shouts at @accalia:
Let's do an experiment: click on the Result tab and post the number it says here with your browser and browser version.
FF 48 — 1.5.
-
@cheong said in @ben_lubar shouts at @accalia:
No, really, don't use it.
http://i.imgur.com/zlrc6aR.png
Now, in all fairness, the
<big>
tag is being used by us, rather than NodeBB. As in we manually type it in to be abusive.#
translates to<h1>
.It did expose the "cut off the top of the post" thing, though.
-
1.2 ON OPERA MOBILE I AM YELLING AND NOT USING PUNCTUATION BECAUSE THERE IS SUCH A LARGE DEMOGRAPHIC USING IT THAT IT'S VERY IMPORTANT GUISE!!!
ALSO, ALL POSTS ARE PERFECTLY READABLE, YOUR BROWSERS ARE TEH SUCK!
I AM SO BORED RIGHT NOW!
-
@Lorne-Kates said in @ben_lubar shouts at @accalia:
What weird css crap is NodeBB doing that means the text in my original screenshot gets cut off? Aren't h1 and big block elements? Shouldn't the top of their box model be the top?
Or is NodeBB making some buttumptions about what it feelz the font size should be, and is hard coding some negative margin somewhere because raisins?More importantly, the first thing any sane CSS design should do is reset all of the default user agent stylesheets to consistent values.
-
@error said in @ben_lubar shouts at @accalia:
@Lorne-Kates said in @ben_lubar shouts at @accalia:
What weird css crap is NodeBB doing that means the text in my original screenshot gets cut off? Aren't h1 and big block elements? Shouldn't the top of their box model be the top?
Or is NodeBB making some buttumptions about what it feelz the font size should be, and is hard coding some negative margin somewhere because raisins?More importantly, the first thing any sane CSS design should do is reset all of the default user agent stylesheets to consistent values.
Yes.
Because WHY THE EVERLOVING FUCK AREN'T THEY THE SAME TO BEGIN WITH AAARGH?
-
@ben_lubar said in @ben_lubar shouts at @accalia:
https://jsfiddle.net/qeLoo6xv/
Let's do an experiment: click on the Result tab and post the number it says here with your browser and browser version.
hmm...... 1.2 on my left and right monitors (in landscape) ....... 1.195 on my center monitor (portrait)
chrome 52.numbers on Windows 10
... ???
-
@ben_lubar said in @ben_lubar shouts at @accalia:
HELLO! HOW ARE YOU DOING, @ACCALIA?
You know, if you added just two more
<big>
tags, that would've become even bigger!
whaddayamean, . D'ya think I give a rip about that?
-
-
-
@anotherusername said in @ben_lubar shouts at @accalia:
@ben_lubar said in @ben_lubar shouts at @accalia:
HELLO! HOW ARE YOU DOING, @ACCALIA?
You know, if you added just two more
<big>
tags, that would've become even bigger!
whaddayamean, . D'ya think I give a rip about that?Typography: how do it werk?
-
-
-
@anotherusername well... shit. That's nowhere near as fun in Chrome as it is in Firefox.
Reference FF screenshot for all the people who can't appreciate it because they're on Chrome:
-
Custom CSS for bold for the win:
-
@ben_lubar 1.5
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 Iceweasel/38.2.1
-
@Yamikuronue is that in Chrome? I don't think your custom bold style is making a whole lot of difference actually.
Mostly it just appears that Chrome is using a 6/5 multiplier (120%) for
<big>
, but Firefox is using a 4/3 multiplier (133%). So the resulting text is a lot bigger in FF.
-
@anotherusername Yes it's Chrome, but my custom style makes it blue :D
-
@accalia said in @ben_lubar shouts at @accalia:
1.2 on my left and right monitors (in landscape) ....... 1.195 on my center monitor (portrait)
:/
Okay, there's no way anyone accidentally wrote css that shitty. The NodeBB devs HAVE to have done this on purpose, with malice.
-
@anotherusername There's just so much special going on here.
-
@Lorne-Kates said in @ben_lubar shouts at @accalia:
@accalia said in @ben_lubar shouts at @accalia:
1.2 on my left and right monitors (in landscape) ....... 1.195 on my center monitor (portrait)
:/
Okay, there's no way anyone accidentally wrote css that shitty. The NodeBB devs HAVE to have done this on purpose, with malice.
Nope, that's the browser trying to adjust DPI.
-
@Lorne-Kates said in @ben_lubar shouts at @accalia:
@accalia said in @ben_lubar shouts at @accalia:
1.2 on my left and right monitors (in landscape) ....... 1.195 on my center monitor (portrait)
:/
Okay, there's no way anyone accidentally wrote css that shitty. The NodeBB devs HAVE to have done this on purpose, with malice.
i'm actually blaming windows DPI scaling on that one. the centre monitor has a slightly higher DPI than the other two.
Chrome deals pretty well with highdpi screens, but it's aparently not perfect.
still i'm not going to complain about a difference of five parts in a thousand difference in font size between two different screens.
-
@accalia said in @ben_lubar shouts at @accalia:
@Lorne-Kates said in @ben_lubar shouts at @accalia:
@accalia said in @ben_lubar shouts at @accalia:
1.2 on my left and right monitors (in landscape) ....... 1.195 on my center monitor (portrait)
:/
Okay, there's no way anyone accidentally wrote css that shitty. The NodeBB devs HAVE to have done this on purpose, with malice.
i'm actually blaming windows DPI scaling on that one. the centre monitor has a slightly higher DPI than the other two.
Chrome deals pretty well with highdpi screens, but it's aparently not perfect.
still i'm not going to complain about a difference of five parts in a thousand difference in font size between two different screens.
Honestly, how crappy the entire thing is makes me want to burn the concept of DPI in a fire. Everything relating to DPI (at least in desktop apps) is always shitty.
-
@anotherusername said in @ben_lubar shouts at @accalia:
@Yamikuronue is that in Chrome? I don't think your custom bold style is making a whole lot of difference actually.
Mostly it just appears that Chrome is using a 6/5 multiplier (120%) for
<big>
, but Firefox is using a 4/3 multiplier (133%). So the resulting text is a lot bigger in FF.Correction: no, FF is using 4/3 for the first
<big>
, 16/11 for the second, and 3/2 for the third and onward...<h1>
: 22px
<h1><big>
: 29.3333px
<h1><big><big>
: 42.6667px
<h1><big><big><big>
: 64px
<h1><big><big><big><big>
: 96px
<h1><big><big><big><big><big>
: 144px
-
HEY GUYS I FIGURED OUT WHY WE'RE SHOUTING
HTTPS://WWW.REDDIT.COM/r/NINTENDO/comments/52v0dv/THROWDOWN_THURSDAY/
ACTUALLY IT'S PROBABLY JUST A COINCIDENCE BUT WHATEVER
-
@anotherusername said in @ben_lubar shouts at @accalia:
FF is using 4/3 for the first , 16/11 for the second, and 3/2 for the third and onward...
goddamit mozilla
-
@coderpatsy said in @ben_lubar shouts at @accalia:
HEY GUYS WHAT'S GOING ON IN THIS THREAD
Apparently, r/okcupid is leaking.
-
@ben_lubar 1.2
Version 52.0.2743.116 Built on Ubuntu , running on elementary OS 0.3.2 (64-bit)
-
@ben_lubar said in @ben_lubar shouts at @accalia:
https://jsfiddle.net/qeLoo6xv/
Let's do an experiment: click on the Result tab and post the number it says here with your browser and browser version.
Well great, now due to some user we have to actually click that link in order to know what you were talking about...
@boomzilla said in NodeBB Updates:
Blacklisted jsfiddle.net in iFramely (required restart).
Filed under: Thanks, @error!