Yes. YES.

So good.

If you notice any bugs, big or small, post em here or on github. I'll try to sneak em in as I fix the bigger issues that crept through during the update.

Re: @Zren:

sneak em

No shoes allowed! ;)

Re: @Marti:
Really need to remember to double lf with md quoting until editing an existing reply is fixered. :)

The new design is really nice! Kudos to you ;)
I especially like the new editor with the little WYSIWYG function (although its design/CSS is still a little buggy) - makes things much easier for me! You might wanna extend that like in this script:

https://github.com/jerone/UserScripts/tree/master/Github_Comment_Enhancer

Regards,
Quack

We're currently using https://toopay.github.io/bootstrap-markdown/ for an editor. Adding new buttons looks mildly complex, but I'll look into it.

https://github.com/OpenUserJs/OpenUserJS.org/issues/168

Testing markdown Fenced code blocks

original JS::

// Add the old object onto the stack (as a reference)

ret.prevObject = this;

ret.context = this.context;

if ( name === "find" ) {

ret.selector = this.selector + (this.selector ? " " : "") + selector;

} else if ( name ) {

ret.selector = this.selector + "." + name + "(" + selector + ")";

}

return ret; /* Slash-star comment */

}

four spaces in the beginning of line::

// Add the old object onto the stack (as a reference)
ret.prevObject = this;
ret.context = this.context;
if ( name === "find" ) {
  ret.selector = this.selector + (this.selector ? " " : "") + selector;
} else if ( name ) {
  ret.selector = this.selector + "." + name + "(" + selector + ")";
}
return ret;     /* Slash-star comment */
}

same code, enclosed in backticks::

    // Add the old object onto the stack (as a reference)
    ret.prevObject = this;
    ret.context = this.context;
    if ( name === "find" ) {
      ret.selector = this.selector + (this.selector ? " " : "") + selector;
    } else if ( name ) {
      ret.selector = this.selector + "." + name + "(" + selector + ")";
    }
    return ret;     /* Slash-star comment */
    }

the result is somewhat surprising

Re: @trespassersW:

yup. In a few days I might try to tackle this. Until then use markup.

Re: @trespassersW:

Looks good now.

Re: @sizzle: and now tables are broken... Interestingly, preview is perfect, result is poor.

Re: @sizzle: no images allowed! :(

Re: @trespassersW:

It will get fixed but I'm not at my dev machine. I did post how to have another dev fix it though at #192 (comment). Patience please. ;) :)

Re: @trespassersW:

Fixed. I posted this image with:

<img src="https://i.imgur.com/LFRKMhl.png" alt="trespassersW" title="trespassersW" />

Re: @Marti:

Or encouraging md...

![trespassersW](https://i.imgur.com/LFRKMhl.png "trespassersW")

Re: @Marti:
Yes, allowing HTML for formatting is merely a courtesy. Markdown is recommended.

First discussion page is disordered by this post.
For myself, I solved this problem using stylish and next css:

  .tr-link td, .tr-link-a, .tr-link .label, 
  .td-fit
  { white-space: normal !important;
    word-wrap:break-word !important;
  }
  .td-fit { width:auto !important; }
  .table .tr-link td { max-width: 600px !important;}

Re: @trespassersW:

Thanks for the report. We do have a few issues open now here and here for this. In the middle of a refactor that is delaying things until they get finished. You can try out the rule set in the pr at this user.js script for the time being.

Drawing html tables is such an esoteric matter..

Re: @trespassersW:

Can be. The Categories column also has a dependency issue about being modified for sorting so not sure what will be done which is why I said "One of many" because I know there will probably be more. Btw what is "next css" ??

Re: @Marti:

Btw what is "next css" ??
the following css code; lost in translation

and here is a patch: OUJS forum fix