Downvote stalkers can't downvote this
-
This post is deleted!
-
I got a downvote in before it was deleted :P
-
This post is deleted!
-
@Jaloopa said in Downvote stalkers can't downvote this:
I got a downvote in before it was deleted :P
I got a downvote in after it was deleted :P
-
@ben_lubar something something mod abuse.
-
oh, he's at it again........
-siiiiiiiiiiiiiiiiiiiiigh-
DAMNIT
FBNECROMACWHARGARBL!
-
@accalia a) this topic is 11 days old
b) BenLubar "necro'd" it. So you should demand that he gets fired for this!
c) that's some pretty big text you got there
Filed Under: d) I am filing this under
-
@Kuro said in Downvote stalkers can't downvote this:
@accalia a) this topic is 11 days old
i am very behind on my reading, okay?
-
@accalia Wow, hadn't seen FF screw up big fonts so badly before...
-
@dcon The
<h1>
tag fixes the line height at 40px for some raisin
-
@RaceProUK I'd seen the top line being cut off before - but I don't think I'd ever seen the multiple overlap before... And with the ins and
del, its ... special.
-
@dcon said in Downvote stalkers can't downvote this:
its ... special.
-
@dcon Eh, at least it isn't
fa-spin
;)
-
@ben_lubar said in Downvote stalkers can't downvote this:
@Jaloopa said in Downvote stalkers can't downvote this:
I got a downvote in before it was deleted :P
I got a downvote in after it was deleted :P
Yup... it only used to have a score of -1.
I wonder, do votes on deleted posts still count toward someone's reputation?
@Kuro said in Downvote stalkers can't downvote this:
c) that's some
prettyugly big text you got thereFTFY.
@RaceProUK said in Downvote stalkers can't downvote this:
@dcon The
<h1>
tag fixes the line height at 40px for some raisinEms would've been a more logical choice.
The post actually looks halfway okay in Chrome; Firefox's natural
<big>
sizes are drastically different from Chrome's. It's an obsolete element in HTML5, but even in the HTML 4.01 spec, it merely said:...along with the caveat, "Rendering of font style elements depends on the user agent."
Firefox interprets both
<big>
andfont-size: larger;
from one absolute named size as a step up to the next larger absolute named size. Chrome devs, on the other hand, completely ignored the absolute named sizes for this, and instead pulled "larger" font sizes out of their ass for both<big>
andfont-size: larger;
. As far as I can tell, Chrome is DOING IT WRONG AND BAD. The CSS standard forfont-size
says:A <relative-size> keyword is interpreted relative to the table of font sizes and the font size of the parent element. Possible values are: [ larger | smaller ]. For example, if the parent element has a font size of 'medium', a value of 'larger' will make the font size of the current element be 'large'.
So according to the CSS spec, based on the example given in it, these should produce exactly the same font size:
-
<span style="font-size: medium;"> <span style="font-size: larger;"> Text </span> </span>
-
<span style="font-size: large;"> Text </span>
In Firefox, they do produce the same size (18px), but in Chrome, the first one is not the same size (19.2px). In fact, even though Chrome has the named sizes (which are the same size as they are in Firefox), all of the larger sizes given by using either
<big>
or by usingfont-size: larger;
are wrong.
-
-
This post is deleted!
-
@RaceProUK said in Downvote stalkers can't downvote this:
@dcon The
<h1>
tag fixes the line height at 40px for some raisinAnd once again, it isn't FF, it's NodeBB shitty development. "Why do something right when you can do something complex and wrong?"
-
@anotherusername said in Downvote stalkers can't downvote this:
I wonder, do votes on deleted posts still count toward someone's reputation?
I dunno. Let's delete all your posts and find out.
-