In which DiscoMarkHTML is discussed. Again.



  • @Onyx said:


    // -----> Assign and bail out of the loop.
    theView = theEnum[ idx ].getView();
    // -----> break
    break;


    // -----> Not a valid view? (A bit redundant, but you never know...)
    if ( theView == null )
    ----->
    return;

    FTFY.

    Well, tried, Duckhorse is being an asshole again.

    Markdown is TR :WTF:? This surprises me...


  • BINNED

    :facepalm:

    Discourse... Just... Can you just try, really try to break shit at least seemingly consistently?

    I need a drink... Gonna check if there's any šljivovica left. If we didn't use it all up for fuel.



  • Holy shit, that's bollocks, isn't it? It looks consistent in the Preview window...

    THIS IS A FONT
    THIS IS A FONT


  • That's just shit. :(
    This software is a shit. :(


  • BINNED

    @tar said:

    This software is a shit.

    This surprises me.



  •     <div class='post'>
            <p>Holy shit, that's bollocks, isn't it? It <em>looks</em> consistent in the Preview window...</p>
    
    <p><aside class="quote"><blockquote>
    <p><code><p></p>
    <pre>THIS IS A FONT</pre></code></p>
    <p><code><pre>THIS IS A FONT</pre></code></p>
    </blockquote></aside></p>
        </div>
    

    :wtf:. WTF is <p><code><p></p> and what is it doing in my post...


  • BINNED

    Oh FFS. That's probably what breaks it. There are probably ::after and / or ::before pseudoclasses defined for <code> blocks inside quotes.

    One minute, checking default CSS.



  • I also want to point out that I just grabbed that code from the Ctrl+U and pasted it, the wonky formatting/whitespacing is exactly how it's being 'rendered'.

    Some quality work there, demonstrates attention to detail...


  • BINNED

    Not perfect, but at least there are no font differences.

    @PJH - seems that nesting <code> and <pre> tags breaks them in quotes. Not sure how to fix it though, assuming what I posted above. :empty won't really work.

    EDIT: Fuck your greyscale image bug, Discourse!


  • BINNED

    I think it's our custom CSS this time. I think I know what PJH wanted to do, but it fails when combining <code> and <pre>.



  • Nevertheless, doing anything remotely complex with "code" inside a quote is basically impossible AFAICT...


  • BINNED

    @tar said:

    Nevertheless, doing anything remotely complex with "code" inside a quote is basically impossible AFAICT...

    FTFY. Sadly.



  • *sighs*
    *remembers that if anyone tries to quote him, they'll get italicized text*
    *sighs again*


  • BINNED

    @tar said:

    *sighs*
    *remembers that if anyone tries to quote him, they'll get italicized text*
    *sighs again*

    Hey! Wait... The preview is lying, isn't it?

    *This will*
    *Get italicized though. Pretty sure at least*
    *I shall now flag for Jeffing*



  • Demonstrating once again that any discussion on Discourse eventually becomes a discussion about Discourse.


  • BINNED

    Because we keep finding shit. Each. And every. Fucking. Day. At least.



  • @Onyx said:

    Because we keep finding shit.

    If you work with shit, guess what you find.



  • @tar said:

    *sighs*
    *remembers that if anyone tries to quote him, they'll get italicized text*
    *sighs again*

    @tar said:

    sighsremembers that if anyone tries to quote him, they'll get italicized textsighs again

    Well, what do you know, it all depends on how you quote...


  • BINNED

    Oh, right. Sorry, my brain keeps trying to reject the overflow of stupid by forgetting such things.


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.