Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[darkhog]

The single return no workYou have to press twice.The hope is dying.

[anewaname]

The single Return, means the Return key?

[scriver]

Does it not work?

Like it's always worked?

[King Zultan]

I haven't noticed anything on the forum not working right, except the search function which was broken before I got here.

[Magmacube_tr]

What are you talking about?

[darkhog]

The fact that a single enter doesn't result in a new line when making a thread, you have to press it twice.It doesn't do it on modify either, likely something is wrong with the full editor. The text in OP was supposed to be a haiku.

[Magmacube_tr]

The fact that a single enter doesn't result in a new line when making a thread, you have to press it twice.It doesn't do it on modify either, likely something is wrong with the full editor. The text in OP was supposed to be a haiku.

That's... strange. I am having no such problems.

[anewaname]

I don't see anything in forum account settings for this sort of thing. I would theorize that in the problem mode, the forum code is treating your Enter key as something other than the ascii(10)+ascii(13) that it should be. SimpleMachineForums code could have legacy code for accepting communications from pre/early-http that says "their Enter key means ascii 10 and two ascii 10s means the display should show linefeed+carriagereturn".

Or your Return key is sticking. Is the problem consistent?

[King Zultan]

Starting to sound like it might be his keyboard that's not working right.

[darkhog]

IfI useA singleEnter, BadThingsHappen
However if I do double enter, it somehow puts a new line correctly. How it looks in the editor (a screenshot): https://i.imgur.com/M4V8cgr.png - seems to affect the full editor only though.https://i.imgur.com/M4V8cgr.png

[darkhog]

...aaaaand it messed up the post in a brand new way, lol.

[McTraveller]

What browser, OS, and localization are you using? What character encoding are you using?

Every way I look at what the forum is sending... there are no characters (printable or otherwise) in the place where your screenshot shows a newline... so the editor "ate" whatever it was your system put there.

EDIT: added in part of the sentence that I forgot to type...

[darkhog]

Windows, Firefox. Must be some modification to the forum made specially for this board, since I haven't encountered such issue on other SMF-based forums in the past. Only the "full" editor seems to be affected (after clicking "reply" link at the bottom or when making a new thread/editing a post). If I am correct, the very next line will show that Quick Reply form is unaffected.
Is it?

[WealthyRadish]

Windows, Firefox. Must be some modification to the forum made specially for this board, since I haven't encountered such issue on other SMF-based forums in the past. Only the "full" editor seems to be affected (after clicking "reply" link at the bottom or when making a new thread/editing a post). If I am correct, the very next line will show that Quick Reply form is unaffected.
Is it?

If you're curious what exactly your system is writing into in the browser's text area when you type, this TamperMonkey script will check:

Code: [Select]

// ==UserScript==
// @name         Read Bay12 text
// @namespace    http://tampermonkey.net/
// @version      1.0
// @description 
// @author       
// @match        http://www.bay12forums.com/smf/index.php?action=post*
// @icon         data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==
// @grant        none
// @run-at       context-menu
// ==/UserScript==

(function() {
    'use strict';

    let msg_box = document.getElementById("message");
    let contents = msg_box.value;
    let output_string = "";

    for (let i = 0; i < contents.length; ++i) {
        let c = contents.charCodeAt(i);
        let hex_char = c.toString(16);
        if (c > 31 && c < 127) { output_string += contents.charAt(i); }
        else if (c > 127) {
            output_string += "{UTF-16:";
            output_string += hex_char;
            output_string += "}";
        }
        else if (c === 0x0A) { output_string += "{NEWLINE}\n"; }
        else {
            output_string += "{ASCII:";
            output_string += hex_char;
            output_string += "}";
        }
    }
    alert(output_string);
})();
To use, add TamperMonkey to firefox, create a new userscript with that text, then right click somewhere on the 'post replies' page and select "TamperMonkey > Read Bay12 text" after typing something in. It should output something like this in an alert box:

the quick
brown fox
jumps

over the
lazy dog
保大

the quick{NEWLINE}
brown fox{NEWLINE}
jumps{NEWLINE}
{NEWLINE}
over the{NEWLINE}
lazy dog{NEWLINE}
{UTF-16:4fdd}{UTF-16:5927}

[darkhog]

Yeah, it adds newlines in the full form.I don't even know why it's only the full form that's affected and not quick reply.
TinyMCE, maybe?