Find/replace Chrome extension disables most functions in Editoria
Eventually, a find/replace feature should be added to the editor. We'll also likely want a book-level search/replace. As a stopgap measure, we might be able to use a Chrome extension to do the find/replace. But, I can't find one that currently works with Editoria (at least on my machine).
Adam found Search and Replace, which gets the closest but still doesn't play nicely with Editoria. The search and replace function successfully find and replaces words in the editor, but it also disables most of the editor's features.
To replicate:
- Using Chrome 58.0.3029.110 (64-bit) on a MacBook Pro running OS X El Capitan 10.11.2
- Add the extension
- Open a chapter in the editor
- Run a search and replace for a word in the editor, with none of the checkbox options clicked (doesn't seem to matter whether you "Replace Next" or "Replace All"). You'll see your desired word substitutions.
There are two glaring problems. First, after the find/replacing, you can keep typing into the editor, but you can no longer:
- apply or change styles, which is either entirely disabled and greyed out, or is unchanged in appearance but doesn't function
- apply formatting (either with keyboard shortcuts or the top bar, which also is either entirely grey and inactive or just doesn't work
- save the fragment
Can you tell why this happens? I wonder if it's adding something invalid into the editor.
Secondly, the replacement won't work if you select the "Input fields only?" option. So, if the word you're replacing also appears outside the editor in Editoria, that text also gets updated, breaking the function of the button.
Perhaps we could live with the second issue for a while if there's an easy fix for the first. Or, we could look for another Chrome extension that works. I tried Easy Replace, RegEx Search & Replace, FindR, and Multiple-word Find and Replace, but none of them could even make replacements in the first place. If there's not an easy fix, though, or another extension, then maybe we should skip the extension and build find/replace in the editor.