[bug/error] Unable to type space in replies

[localzuk]

For the last week, if I try and reply to a post I am unable to type a space between words without copying and pasting it in. Kinda annoying, to say the least...

 

Running Chrome 54.0.2840.71 m 64bit on Win 10 build 1607.

[ZeroHour]

For the last week, if I try and reply to a post I am unable to type a space between words without copying and pasting it in. Kinda annoying, to say the least...

 

Running Chrome 54.0.2840.71 m 64bit on Win 10 build 1607.

 

Hmm it seems to break and work occasionally for me, when I typed in the reply box to you initially it worked, I then "reply with quote" and it didnt then now when I tried again it did work, I had no noticed it until testing now, I think chrome 54 came out in the last week so I wonder if its to do with that.

 

Thanks, will investigate.

 

EDIT: This is being reported across quite a large amount of vBulletin forums right now and all seem to point to something breaking in Chrome 54. It seems to occur if you try to type under a quoted post most regularly. I am looking for a fix.

Edited October 28, 2016 by ZeroHour

[6Foot2]

For the last week, if I try and reply to a post I am unable to type a space between words without copying and pasting it in. Kinda annoying, to say the least...

 

Running Chrome 54.0.2840.71 m 64bit on Win 10 build 1607.

 

Working here with the same setup you describe. Is this still an issue for you?

[ZeroHour]

It is happening for me nearly 100% of the time when using "Reply with Quote"

[6Foot2]

It is happening for me nearly 100% of the time when using "Reply with Quote"

 

That does not happen for me. Replying to, hopefully, provide more information.

 

[sparkeh]

Got it intermittently with chrome 54 here

[ZeroHour]

For the last week, if I try and reply to a post I am unable to type a space between words without copying and pasting it in. Kinda annoying, to say the least...

 

Running Chrome 54.0.2840.71 m 64bit on Win 10 build 1607.

A possible fix is rolling out now but you may need to clear you cache to test it.

[sparkeh]

A possible fix is rolling out now but you may need to clear you cache to test it.

Ok this appears to be working now

 

Thanks!