[bubba]

test test test

[Tattersail_]

It is ok from mobile. Just pc

[Silencer]

Tattersail_, on 29 October 2016 - 06:33 AM, said:

It is ok from mobile. Just pc

Definitely an odd issue. I don't think I've had any trouble on Chrome. Do you know your version number? (settings/about or similar should have it)

[Tattersail_]

Silencer, on 29 October 2016 - 07:31 AM, said:

Tattersail_, on 29 October 2016 - 06:33 AM, said:

It is ok from mobile. Just pc

Definitely an odd issue. I don't think I've had any trouble on Chrome. Do you know your version number? (settings/about or similar should have it)

Not until Monday

[Whisperzzzzzzz]

This Chrome bug report says they're deprecating space bar, as it's "too confusing for newer users." Chrome seems to be targeting infants these days.

First they came for backspace, now they're coming for space ;(

This post has been edited by Whisperzzzzzzz: 29 October 2016 - 12:52 PM

[Tattersail_]

Andorion, on 27 October 2016 - 04:30 PM, said:

Xae, on 27 October 2016 - 04:08 PM, said:

If a hard refresh (Ctrl + R or clearing your cache) doesn't solve it, check the console; Ctrl + Alt + i in Chrome, Ctrl + Alt + j in Firefox. In case a recent browser update caused an incompatibility, there may be an error there.

Testing,nohardrfreshdoesnotwork.

testingnope.

[Tattersail_]

Silencer, on 29 October 2016 - 07:31 AM, said:

Tattersail_, on 29 October 2016 - 06:33 AM, said:

It is ok from mobile. Just pc

Definitely an odd issue. I don't think I've had any trouble on Chrome. Do you know your version number? (settings/about or similar should have it)

Version 54.0.2840.71 m

[Andorion]

Tattersail_, on 31 October 2016 - 08:47 AM, said:

Silencer, on 29 October 2016 - 07:31 AM, said:

Tattersail_, on 29 October 2016 - 06:33 AM, said:

It is ok from mobile. Just pc

Definitely an odd issue. I don't think I've had any trouble on Chrome. Do you know your version number? (settings/about or similar should have it)

Version 54.0.2840.71 m

Version 54.0.2840.71 m (64-bit) for me too

[Imperial Historian]

I have replicated the issue on my chrome, same version! Only affects the quote reply. Fast reply and add reply work fine.

I'm still at a loss as to how to fix it though.

[Andorion]

I hope the next Chrome update fixes this

[D'rek]

From a quick google search, it seems like there are other websites that have experienced similar issues over the last many years - spacebar not working, specifically only in Chrome. No ideas on the cause or fix, though.

[ansible]

D, on 31 October 2016 - 02:37 PM, said:

From a quick google search, it seems like there are other websites that have experienced similar issues over the last many years - spacebar not working, specifically only in Chrome. No ideas on the cause or fix, though.

testthisisatest

[ansible]

ansible, on 31 October 2016 - 09:50 PM, said:

D, on 31 October 2016 - 02:37 PM, said:

From a quick google search, it seems like there are other websites that have experienced similar issues over the last many years - spacebar not working, specifically only in Chrome. No ideas on the cause or fix, though.

testthisisatest

test this is a test

[ansible]

Ok, I noticed this recently as well. I can reproduce the error and I've found a few ways around it.

The simplest way is to tap the up arrow in your reply when quoting someone before you start typing. This brings the cursor to directly below the quote tag and spaces work fine. Interestingly, if you look at the actual HTML in Chrome vs. Firefox, you can see an additional two line breaks added to the reply editor in Chrome - "<br> [/quote] <br> <br> <br>" (Chrome) vs. "<br> [/quote] <br>" (Firefox).

The other way to permanently fix the issue (from the user side) is to change the editor settings. It appears from the editor attributes that the editor is set to WYSIWYG by default - meaning, whatever you do with formatting looks in your reply like it will when you post it (e.g., when you highlight text and click the "Bold" button, the text actually turns bold instead of getting wrapped in [b ][ /b] tags). The only control the user appears to have over the editor is the RTE setting.

My Settings -> General Settings -> Posting Settings -> Uncheck "Enable visual (RTE) editor?" box -> Save Changes

This will make your replies look less fun while writing them (fixed-width fonts, [tags] instead of visual text changes, etc.), but it does prevent the spacebar problem.

From what I can tell this is a bug with the current version of Google Chrome and the WYSIWYG editor. Using a "Standard" editor option (or something like no RTE) doesn't cause the bug to occur when using Chrome.

I'm using Google Chrome Version 54.0.2840.71 m (64-bit).

[worry]

That sounds complicated. Any way to clarify? For reference: I'm pushing the thingy on the page and the line isn't showing, but when I push the other thingy it's actually still there. So is it there when it's not showing and I just can't see it or is it really not there?

[ansible]

Press F10 for money?

[worry]

Does it have to be capital F or can I type f10?

[Silencer]

ansible, on 31 October 2016 - 10:13 PM, said:

Ok, I noticed this recently as well. I can reproduce the error and I've found a few ways around it.

The simplest way is to tap the up arrow in your reply when quoting someone before you start typing. This brings the cursor to directly below the quote tag and spaces work fine. Interestingly, if you look at the actual HTML in Chrome vs. Firefox, you can see an additional two line breaks added to the reply editor in Chrome - "<br> [ /quote] <br> <br> <br>" (Chrome) vs. "<br> [/ quote] <br>" (Firefox).

The other way to permanently fix the issue (from the user side) is to change the editor settings. It appears from the editor attributes that the editor is set to WYSIWYG by default - meaning, whatever you do with formatting looks in your reply like it will when you post it (e.g., when you highlight text and click the "Bold" button, the text actually turns bold instead of getting wrapped in [b ][ /b] tags). The only control the user appears to have over the editor is the RTE setting.

My Settings -> General Settings -> Posting Settings -> Uncheck "Enable visual (RTE) editor?" box -> Save Changes

This will make your replies look less fun while writing them (fixed-width fonts, tags instead of visual text changes, etc.), but it does prevent the spacebar problem.

From what I can tell this is a bug with the current version of Google Chrome and the WYSIWYG editor. Using a "Standard" editor option (or something like no RTE) doesn't cause the bug to occur when using Chrome.

I'm using Google Chrome Version 54.0.2840.71 m (64-bit).

Ooooh, that might explain why I haven't noticed. Pretty sure I switched my text settings over aaaaages ago.