You *literally* cannot post this one
-
Continuing the discussion from You can't post this for some reason.:
<hr/> http://sonic.wikia.com/wiki/Amy_Rose
Try and post this. It cannot be done.
And I mean it cannot be done.
Meta'd:
https://meta.discourse.org/t/html-horizontal-rules-prevent-successful-oneboxing/28364?u=raceproukCovers this thread too:
http://what.thedailywtf.com/t/you-cant-post-this-for-some-reason/48374?u=raceprouk
-
-
You know damn well what I mean…
-
For once the stupidity of Discourse's quote mechanism makes life easier*
*For varying definitions of easy
-
I will just point out that XHTML is Doing It Wrong™, may it never leave the pit we threw it into.
However, browsers will deal with it, and so should Discourse. So the bug is still valid IMO.
-
I am actually suprised that oneboxed... as it did not onebox in the post being quoted. That goes against the whole "quoted posts should be stripped of everything!"-thing
The thing making my life easier was the pre-thing that markdown gives me. Because things in pre will not be validated or something? You can probably break stuff with that as well...
Filed Under: Just saying!
-
I think I found another bug.
Can anyone post this?
doesn't change the fact that this shouldn't be broken: <hr> http://sonic.wikia.com/wiki/Amy_Rose
-
What? How... WTF?! How does that even happen?
-
Nope
Currently putting something together on meta.d…
-
doesn't change the fact that this shouldn't be broken:
-
Markdown hr's still work ...
-
Just... wow.
<hr>
s, Discourse's greatest enemy. It breaks usercards, it breaks oneboxes, is there anything they cannot break?
-
<hr>s, Discourse's greatest enemy. It breaks usercards, it breaks oneboxes, is there anything they cannot break?
Their own reputation for breaking things?
-
I'd love to see the logs for the last few minutes. I wonder if we're causing an error or if something in Discourse is just returning a 500
-
If we get white screen of death in a few minutes, you know that we filled the hard drive with logs
Filed Under: We need a seperate server for the logs!
-
<hr>s ... breaks usercards
I'm sure they didn't, because my usercard has the issue and I don't use <hr>s. I do use <br>s though, and I'm thinking some or all HTML elements break usercards..
-
Code blocks break them, too.
Also, Jellypotato.
-
I'm sure they didn't
They used to; the fix was to strip thehr
s before displaying the usercard.Y'know, instead of fixing the bug.
-
I say we just ban all HTML. Who needs that shit anyway, we have BBDown!
-
[hr]
Yep, valid BBCode for
hr
isn't supported
-
-
They used to;
Hrm, let me clarify.
I'm sure they specifically didn't
Yeah, I'm sure <hr>s did/do break usercards, but obviously they aren't the only thing because they're still broken (again, my usercard as an example), and yes, they didn't fix it, they just tried a workaround that, y'know, didn't work.
-
Code blocks break them, too.
I don't remember what my findings were on that. I thought I had it narrowed down to HTML elements and entities causing jellypotatoing, but maybe the code blocks did too.
Eh, doesn't matter, they don't seem to care to fix it anyways.
-
What? How... WTF?! How does that even happen?
The regex DiscoMarkdownHTMLBBParser shat itself, methinks.
-
Yeah, I'm sure <hr>s did/do break usercards, but obviously they aren't the only thing because they're still broken (again, my usercard as an example), and yes, they didn't fix it, they just tried a workaround that, y'know, didn't work.
It's some bullshit broken jQuery plugin that doesn't properly tear down its garbage it leaves behind.
The fix is to rewrite the functionality for Ember with proper teardowns, which nobody has done yet.