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!

[BirdOPrey5]

Reserved.

[BirdOPrey5]

<span style="text-decoration: line-through">Well, I guess this was a waste of my time.

Google has already pushed out an update with Chrome that fixes the issue. The new version on Win 10 64 bit is 54.0.2840.87.

If you have already installed it maybe give it a week or so for everyone to update and then remove it. No need for it.</span>

Edit - Not true.

[andryus]

I am getting the same issue with the latest chrome update ( 54.0.2840.87 m )

[Kane@airrifle]

Originally Posted by andryus

I am getting the same issue with the latest chrome update ( 54.0.2840.87 m )

As am I and my users.

[BadgerDog]

Originally Posted by BirdOPrey5

Well, I guess this was a waste of my time.

Google has already pushed out an update with Chrome that fixes the issue. The new version on Win 10 64 bit is 54.0.2840.87.

If you have already installed it maybe give it a week or so for everyone to update and then remove it. No need for it.

I've found your code and contributions are never a waste of time .. :up:

Thanks for doing this ..

Regards,
Doug

[BirdOPrey5]

Originally Posted by andryus

I am getting the same issue with the latest chrome update ( 54.0.2840.87 m )

Originally Posted by Kane@airrifle

As am I and my users.

Have you restarted your browsers and perhaps cleared your cache? I know I cleared my cache for a different reason but it definitely works for be after restarting the browser.

[andryus]

Originally Posted by BirdOPrey5

Have you restarted your browsers and perhaps cleared your cache? I know I cleared my cache for a different reason but it definitely works for be after restarting the browser.

Sure, already tested, still with the same issue with the latest chrome update, tested on different computers with clean chrome.

[BirdOPrey5]

So weird... seems like it is still broke for me. I thought changing styles would have reloaded the CSS but I had to clear my cache and once I did the problem was back.

There is no working fix yet from Chrome, sorry for the confusion.

[DeMonViTo]

Hello thanks for the mod!
I have the same problem even when I reply to private messages, you could place the warning them also?