Abusing <big> tags
-
Continuing the discussion from The Official "Likes" Thread: Blazing Mahjong Saddles:
It seems putting some <small> tags in amongst <big> tags will stop whatever rule limits max font size by abusing <big> tags. I wonder how far it can go...
The quick brown fox jumped over the lazy dogs.
-
The End key is broken in this topic. Just FYI.
-
The <kbd>End</kbd> key is broken in this topic. Just FYI.
It goes to the beginning of the last post.
-
There is still some kind of limit, if I add any additional size tags they are ignored and the content is not displayed.
-
This seems to have broken chrome. There is a horizontal black line that appears sometimes as you scroll down, and it moves randomly on top of other elements afterward.
-
The best part is, if they actually didn't implement the rule for the tag, it would make it better.
-
Off to admin I go...
-
The End key is broken in this topic. Just FYI.
Not for me. But then, that's with several posts now. J / K to the rescue.
-
As posted in the Likes thread:
Under the DIV containing the post, everything goes into a paragraph tag. Then, from there, if you nest 19 or more tags of any type, the 19th tag and up will be hidden.
Best link I can find doing a Discosearch regarding it is here.
-
congratulations. i had to use the jump to post selector hidden in the post counter slider green widget thing for the first time ever just to navigate to the next post (page Down is also broken for that post)
-
Ah okay. I was just trying all kinds of things to let me put more tags in but couldn't get anything to work past 19.
-
Not for me. But then, that's with several posts now. J / K to the rescue.
I think it was only broken with a single post. The first reply fixed it.
-
-
-
*_
Sadness
-
more than two nested bigs forces size to 14px
big
bigger?edit: nope..... must be misreading the CSS. either way props to @pjh for fixing your monstrosity.
-
Fixed.
must be misreading the CSS.
You saw it 1/2 way through the change.
Now - who's going to raise the issue over on Meta where they don't have the fix?
-
@PJH fixed it by making <big> and nested <big>s all do 14px. Not even being slightly incremental like he did with <small> (which dropped by 1px each increment until a minimum of 6px).
And Hanzo'd...
-
Now - who's going to raise the issue over on Meta where they don't have the fix?
SUSPENSION TIME! I notice that @Matches isn't currently suspended over there.
-
Now - who's going to raise the issue over on Meta where they don't have the fix?
not me! i've not got a burns avatar!
-
@PJH fixed it by making <big> and nested <big>s all do 14px.
That was 1/2 way through the fix. It now mirrors the smalls which were done in response to this.
/* Revert small+small+small http://what.thedailywtf.com/t/quickly-save-the-nested-smalls/4661 */ small { font-size: 10px; small { font-size: 9px; small { font-size: 8px; small { font-size: 7px; small { font-size: 6px; }}}}} /* Stop big+big...+big abuse http://what.thedailywtf.com/t/abusing-big-tags/5566 */ big { font-size: 14px; big { font-size: 16px; big { font-size: 18px; big { font-size: 20px; big { font-size: 22px; }}}}}
-
-
i'm not willing to take that risk!
-
I found a bug This Big
-
Try it over on Meta - it might be bigger...
-
according to the edit-history you didn't close any of the tags. Is that correct or is Discourse-Edit-Raw-thingy broken?
Filed Under: Completely ignoring the big-tag-problem
-
I didn't close any of them because I'm lazy. Surprisingly, Discourse will auto-close them and not screw up the rest of the page.
-
-
Did you start a timer before you posted it?
Actually 2 timers: 1 for suspension and 1 for deletion of the topic
You can also maybe look at a calendar for a fix [AS DESIGNED WON'T FIX]Filed Under: We need to time those things down to microseconds
Addendum: To give this post some meaning: Why do browsers even allow these text-sizes? Is there ANY use to them? EVER?
-
Takes breath....
Bye.
-
Did you start a timer before you posted it?
No, but the timestamp over there says this:
Dec 17, 2:03 PM
That's EST.
-
Nice:
-
That is Discotime...
adding a post so once can use means to scroll past the beginning as pagedown and end are broken by @boomzilla's post.
^ using End on that post with Opera worksFiled Under: Discotime and a not working bug sigh
-
If anyone wants to see what the thread looks like without my CSS hack in.
-
Now - who's going to raise the issue over on Meta where they don't have the fix?
Not me. I only go over there in extreme cases anymore.
-
-
<big><big><big><small><big><big><big><big><big><big><big><big><big><big><big><big><big><big>The quick brown fox jumped over the lazy dogs.
-
You can see what I put in there on my profile page:
-
What the
Was that a Hanzo edit or does Discourse no longer follow one-directional linear time?
-
yay! my flag lead to a badge!
not for me of course, but still.
-
Was that a Hanzo edit or does Discourse no longer follow one-directional linear time?
Yes.
-
If anyone wants to see what the thread looks like without my CSS hack in.
Chrome doesn't like pointing the URL to subsequent posts:
-
Not me. I only go over there in extreme cases anymore.
I don't even have an account there...
-
i do and i encountered this error while editing my response to the bug report:
what the? how did discourse break my fonts like that?
-
-
it is my rule to not hand out gremming and spellar flags for pointing out spellar and gramming errors in my own posts (like shooting fish in a bathtub that is) but i'm making an exception here....
I'll just let my flag text speak for itself:
-
Did you take down the entire site? I get nothing there, not even a timeout error. Not even the homepage will load for me.
-
On mobile? It's working fine for me, but I don't have a web capable phone.
-
Nope, on desktop.
-