New Posting Features - Chrome Browser Notice (For Quick Reply Editor) - How to fix non-working space bar

If you are not already aware the latest version of Chrome browser (Version 54.0.2840.71, possibly others) has introduced a bug or incompatibility with the version of CKEditor used in VB 4.x.

If a user attempts to use the "Reply With Quote" feature on an existing post and begins to type their reply under the existing quote without hitting the Enter key first, the space bar will not work.

The issue is talked about on vBulletin.com here: http://www.vbulletin.com/forum/forum...rking-on-reply

While this is not a true fix, it does display a notice above the quick reply editor advising Chrome users that they can fix the problem simply by hitting the Enter key. (See Screenshot.)



The actual text displayed is held in a Global phrase called chrome_editor_message_bop5 so it is easily edited or translated as needed using Phrase Manager in the Admin CP.

There are no options, just install it and it will become active. Disable or remove the product to stop using it.

Notice will only be displayed in Chrome browser and when the enhanced WYSIWYG editor is enabled in the user's options. The Standard Editor and Basic Editor do not have this bug.

The function that attempts to determine the browser version was publicly available, location it can be found is a comment in the Functions plugin.

This mod will only install on VB 4.x versions and is only useful with VB 4.x versions 4.1.12 and above. May not work on heavily customized styles.

------------------------------------------------------

Please "Mark as Installed" if you use this.
Donations always appreciated. :up:
Nominate MOTM if you LOVE it!

[tpearl5]

Originally Posted by Kane@airrifle

I take no credit, this kludge was posted elsewhere by man1c.

To get it to work in PMs and Quick reply add this to the bottom of editor_contents.css.

/*-- Temporary Chrome Spacebar Fix --*/
@supports (-webkit-appearance:none) {
body.forum {white-space: pre-wrap;}
body.content {white-space: pre-wrap;}
}

Thanks for this! Is it just putting the cursor before the quote tag, or am I missing something?

[sticky]

Anyone know if the latest chrome update resolves this?

[Kane@airrifle]

Originally Posted by tpearl5

Thanks for this! Is it just putting the cursor before the quote tag, or am I missing something?

Other than occasionally testing I never use the WYSIWYG editor myself so I do not really know what the usual cursor position is for it.

After complaints about the massive amount of whitespace the above css kludge adds to quoted contents while editing, particularly irksome when the post is long, I went another route in the end.

I removed the css from editor_contents.css and kept Quick Edit turned off. In New Posting Templates/newpost_quote I simply added 3 blank lines below:

{QUOTE={vb:raw originalposter}]{vb:raw pagetext}[/QUOTE}

It has the same effect as the css kludge without the aggravation of the white space in the quoted content. Users imply move the cursor to the 1st, 2nd or 3rd line below the quote and reply. If you can live an under quote you can put the blank lines above the code.

Originally Posted by sticky

Anyone know if the latest chrome update resolves this?

BirdOPrey5's mod is still relevant with the latest version of Chrome ( 56.0.2924.76 ). I don't think Google will fix it. I don't think the baked in CKEditor needs a complete overhaul either, as far as I know only two files need updating, ckeditor.js and the enhancedsourcearea plugin.

[tpearl5]

Originally Posted by Kane@airrifle

Other than occasionally testing I never use the WYSIWYG editor myself so I do not really know what the usual cursor position is for it.

After complaints about the massive amount of whitespace the above css kludge adds to quoted contents while editing, particularly irksome when the post is long, I went another route in the end.

I removed the css from editor_contents.css and kept Quick Edit turned off. In New Posting Templates/newpost_quote I simply added 3 blank lines below:

{QUOTE={vb:raw originalposter}]{vb:raw pagetext}[/QUOTE}

It has the same effect as the css kludge without the aggravation of the white space in the quoted content. Users imply move the cursor to the 1st, 2nd or 3rd line below the quote and reply. If you can live an under quote you can put the blank lines above the code.



BirdOPrey5's mod is still relevant with the latest version of Chrome ( 56.0.2924.76 ). I don't think Google will fix it. I don't think the baked in CKEditor needs a complete overhaul either, as far as I know only two files need updating, ckeditor.js and the enhancedsourcearea plugin.

Yes, I noticed the extra line breaks too.

I'm going to do some testing with the updated ckeditor rar (v3.6.6) file posted here: http://www.vbulletin-ressources.com/...10-et-ckeditor

and see if it makes a difference.

[tpearl5]

Okay, yeah, that rar isn't going to work without modifying things further. It looks like they just merged the vbulletin plugin with the latest ckeditor code, but by default vbulletin doesn't use the core directory.

Originally Posted by Kane@airrifle

I don't think the baked in CKEditor needs a complete overhaul either, as far as I know only two files need updating, ckeditor.js and the enhancedsourcearea plugin.

In ckeditor.js there's actually a function to insert the enter key

(function () {n.add('enterkey', {

If that were to be used after clicking reply with quote that would probably solve the issue. Unfortunately I don't know enough JavaScript to modify things myself.

[Flipfloptrader]

Installed and working, exactly what I was after, thank you.

[War Machine]

I can't translate the whole phrase. Everytime i try it my site crash in white page. Any solutions?

[sticky]

Originally Posted by tpearl5

Okay, yeah, that rar isn't going to work without modifying things further. It looks like they just merged the vbulletin plugin with the latest ckeditor code, but by default vbulletin doesn't use the core directory.



In ckeditor.js there's actually a function to insert the enter key

(function () {n.add('enterkey', {

If that were to be used after clicking reply with quote that would probably solve the issue. Unfortunately I don't know enough JavaScript to modify things myself.

Any update or solution?

[BirdOPrey5]

Originally Posted by War Machine

I can't translate the whole phrase. Everytime i try it my site crash in white page. Any solutions?

Check your PHP error log right after you get a white screen. It will be one of the most recent errors listed in the log. That will help figure out the issue. My guess, perhaps, out of memory, but wild guess without actual error.

[creative-friend]

Now space bar working fine on WYSIWYG mode