Client Support identified Problem:

2.15 Support Alpha Site using Google Chrome Version 54.0.2840.50 beta-m (64-bit)

I am unable to add spaces to the body of the flex editor or any app that has the same editor toolbar (article library classic).

Quality Assurance Testing:

During QA testing it was determined that working with any CuteEditor on Chrome V.54 (BETA) exhibits the following behavior. 

·     Existing CuteEditor Apps – No issues editing content

·     New CuteEditor Apps – When creating content within app for the first time pressing the spacebar does nothing

Areas of the WCM that are affected:

·     Flex Editor Apps

·     Headlines and Features Classic

·     Article Library Classic

·     Broadcast E-Alerts (HTML editing)

·     Minibases (Custom View)

Quality Assurance Findings:

·     Issue is only occurring on Chrome BETA (v.54) browser

·     Issue was found to be isolated in the actual CuteEditor itself and not the WCM product

·     Issue is only going to affect clients in Site Manager (Editors of any app or broadcast E-alerts)

·     End User’s rendering will not be affected

Workarounds:

·     Don’t use the Chrome Browser v.54 (BETA)

o  Use alternate browser (Safari, Firefox, IE or Edge)

·     On new CuteEditor creation type a string of characters into the editor and backspace/delete all characters.  Once all content/characters is/are deleted the editor will accept spaces (function of hitting the spacebar)

o  Exception: If user does the above and then clicks html view and goes back to normal view without adding content the issue will reoccur

Concerns:

·     Google Chrome V.54 is set to release Tuesday October 18^th  October

o  ***This is our best guess on when the browser will release the update.  Google at this time does not have an official release date.  Right now we are making this assumption of release date based on the following information. https://www.chromium.org/developers/calendar (see section “Estimated *Stable dates” ***

·     Google Chrome automatically updates the browser without asking users.  It is possible to turn this feature off however most users do not know that.

Mitigation Strategies:

·