It think this bug might have been fixed before (I remember it working a few times), but it's back. You can't add newlines anywhere when making a new thread while in BBCode editing view.
"Roughly 95% of Minecraft players hate Villagers and would be very happy if they were removed. If you are one of the 5% who actually like villagers, copy this into your signature." -RainbowGirl
"Roughly 95% of Minecraft players hate Villagers and would be very happy if they were removed. If you are one of the 5% who actually like villagers, copy this into your signature." -RainbowGirl
I was also experiencing this while making a thread.
I presume this is possibly a chrome-only bug, but I did look into the console and noticed some helpful output
The first line (in blue) is just a minor css thing that is completely unrelated, ignore it.
The second line ("'KeyboardEvent.keyLocation'") was the output we should be focusing on and could be the source to this problem, though it also may not. I didn't check anything so don't quote me on that.
The other 4 lines are the outcome of pasting in a new line. I only pasted two new lines, each produced two "null" outputs.Edit: I just went back to editing the thread I was making when this bug occurred, and now pasting a new line only creates one null output. Could be the fact I did copy an already pasted in new line which could have a different effect?
Links to Mods: EndPlus | Deeper Caves | FarLands
"Roughly 95% of Minecraft players hate Villagers and would be very happy if they were removed. If you are one of the 5% who actually like villagers, copy this into your signature." -RainbowGirl
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumHi
Hello
This is a new line.
Pleased to say, this works.
Have you any cake?
Sorry, I'm out.
That worked...
Links to Mods: EndPlus | Deeper Caves | FarLands
"Roughly 95% of Minecraft players hate Villagers and would be very happy if they were removed. If you are one of the 5% who actually like villagers, copy this into your signature." -RainbowGirl
I presume this is possibly a chrome-only bug, but I did look into the console and noticed some helpful output
The first line (in blue) is just a minor css thing that is completely unrelated, ignore it.
The second line ("'KeyboardEvent.keyLocation'") was the output we should be focusing on and could be the source to this problem, though it also may not. I didn't check anything so don't quote me on that.
The other 4 lines are the outcome of pasting in a new line. I only pasted two new lines, each produced two "null" outputs.Edit: I just went back to editing the thread I was making when this bug occurred, and now pasting a new line only creates one null output. Could be the fact I did copy an already pasted in new line which could have a different effect?
-
View User Profile
-
View Posts
-
Send Message
Admin