| Issue Number | 11 |
|---|---|
| Summary | [Calendar] WYSIWYG editor options |
| Created | 2013-09-17 09:24:53 |
| Issue Type | Improvement |
| Submitted By | Juthe, Robin (NIH/NCI) [E] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2013-10-08 18:10:18 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/oceebms/issue.113295 |
TIR #2416 entered 2013-02-28 by Robin Juthe
Would it be possible to add center/right-justify/left-justify options to the WYSIWYG editor options for creating our agendas? Also, is there an option available to allow us to indent content? Pressing "tab" brings us to the next field on the page.
Victoria has also noticed that hitting "return" in the WYSIWYG editor on the travel pages doesn't do anything. We should look into what other options are available for helping us format text within these editors.
I have added buttons for aligning text right, left, and center, and for indent and outdent. I am unable to reproduce the behavior reported by Victoria (pressing the Enter key starts a new paragraph when I try it on the travel pages). Ready for user review on DEV.
It looks like the problem Victoria ran into is unique to IE version 10. Earlier versions of IE don't have that problem, nor do other browsers. Workaround for now is to use Firefox or Chrome.
The new buttons, and the return key, all work in Firefox, but they do not work in IE. Should they be working in IE? I thought your last comment about using Firefox or Chrome only applied to the return key, but perhaps I am reading it wrong?
You were reading it right, but it seems that what I learned from Sridhar about what was broken by IE10 wasn't a complete picture. There is a more recent version of the WYSIWYG library we're using, which has workaround for the IE10 bugs, but that library is shared by all of the Drupal sites, which means we need to coordinate the upgrade and its testing with those other sites. We're slated to discuss what the timetable might look like some time next week. I have floated the idea of modifying the EBMS to force IE10 to behave like IE9, but that too would require (possibly extensive) testing, and I might not get the green light to take such a drastic measure. In the meantime, you'll need to use another browser, or force IE to use "compatibility mode" for the EBMS (and I'm not sure what side effects that might introduce).
We will plan to use Firefox when we are using the WYSIWYG editor pages. It doesn't seem like it's worth it to change the behavior of the EBMS with IE10 given the extensive testing required and potential side effects.
Verified on prod.
Elapsed: 0:00:00.000675