Jump to content

CKE Firefox and Backspace


Klenkes
 Share

Recommended Posts

This morning a client contacted me with a strange problem. At first I couldn't reproduce it because I use Chrome but then I realized that it only affects Firefox and CKE fields.

If you type some text and then press SHIFT+ENTER to insert a <br> then wirte some text in the second line and then place the cursor at the start of the second line and hit backspace, the cursor jumps to the wrong position. The clients content editors are extremely frustrated by this because they have to search for the cursor :P

I can reproduce this behavior in almost all PW versions, even a clean install witout any CKE plugins.

This whole behavior seems somehow familiar, like I have heard it before, but I can't remenber...

cke-ff-problem.jpg.fa56080a8a29e1d29c4e80ad74a10455.jpg

Anyone knows a solution except using Chrome?

Link to comment
Share on other sites

Just tried it one more time and I see the same behavior as yours, that's strange. Tried to find something similar in the issues list, with no luck, so just open the new one.

Link to comment
Share on other sites

As you know...

There is always Ctrl + Z to undo Shift + Enter.

And placing the cursor at the end of the former line and pressing Delete. (Is the cursor also not where it should be?)

If there is no other solution...

NB: yesterday I tried to center an image with a style that centered the paragraph. It always made the image disappear.
Clicking on Source, I saw that something was not normal, and that helped me resolve the problem.
WYSIWYG editors can sometimes nest tags strangely, etc.
But yours seems to be another kind of issue.

Edited by Christophe
Link to comment
Share on other sites

12 hours ago, Zeka said:

Just tried it one more time and I see the same behavior as yours, that's strange. Tried to find something similar in the issues list, with no luck, so just open the new one.

Thanks. I didn't find anything either. I will file a new one.

5 hours ago, Christophe said:

There is always Ctrl + Z to undo Shift + Enter.

And placing the cursor at the end of the former line and pressing Delete. (Is the cursor also not where it should be?)

There are a few ways to avoid the error but for now I recommended to use Chrome instead of FF. These are professional texters and they are used to work in a certain way(we all know the feeling). But they will have to adapt for now.

Thanks for testing.

  • Like 1
Link to comment
Share on other sites

1 hour ago, Klenkes said:

I know. But the content editors are women in their end thirties and who am I to argue with them? I don't have a death wish :lol:

 

did LOL

I have tested this now with FF 58.0.2, Windows 8, and almost the latest PW version (CKEditor field inside a repeater matrix, multilang-setup).

I tried placing the cursor at the start of the 2nd line with the home button, with my mouse, and with going back using the arrow-left button. The cursor is exactly where it's supposed to be.

Perhaps you should also mention what kind of CKE setup / config you have, to narrow it down.

Link to comment
Share on other sites

13 hours ago, dragan said:

I have tested this now with FF 58.0.2, ...

FF 58? That's interesting! The "girls" said that the problem started about 10-14 days ago. Perhap the problem was introduced to FF with V 59?

13 hours ago, dragan said:

Perhaps you should also mention what kind of CKE setup / config you have, to narrow it down.

Doesn't matter. It also happens on CKE's own demo. https://ckeditor.com/ckeditor-4/

  • Like 1
Link to comment
Share on other sites

 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By abdus
      Wow
      I've started using it and I'm really impressed with how fast and responsive it is. Tab switching and startup is instant. On my PC, Chrome lags when scrolling on YouTube or on some sites occasionally, but on Quantum, everything feels buttery smooth. Design is quite nice and not in our face. RAM usage is way lower than Chrome, too.
      It'll be released on November 14, but a beta and dev edition is available if you want to test and see for yourself.
      https://www.mozilla.org/en-US/firefox/quantum/
    • By Yannick Albert
      Howdey!
      Over the last weeks, I had some critical thoughts about processwires ui/ux feeling (relative sizing, overflow-x, hover-states, word-wrap:break-word) but also its stability.
      Last night I had the time to setup some new things. Good point for me to fiddle a bit around, with issues I've seen over the last months...
      ...short break:
      A lot of bugs, I've noticed earlier, are gone...
      @allcontributors I ♥ you!
      However, someone left over some bugs, for me ;-)
      I just ended up with an ugly and unstructured markdown file. No issues or pull-requests via git. The biggest reason, most things are between "bug" and "enhancement" or are just too platform specific. I think, it's better to talk about those stumbling blocks first.
      Ok, enough for now.
      As I said, it's markdown, to see the compiled thing, take this: https://gist.github.com/yckart/62b7b2ed9d0e3845cc4b
      # Bugs - Mobile (iOS 8) ## Navigation closes immediately **Description** Menu opens (for less than ~100ms) and closes immediately again. **Reproduce** Click on the upper left menu icon, scroll a bit down (~10px), click menu icon again. Try to open the menu. ## "Add New"-menu unclosable **Description** Shortcut-menu to add new pages, can not closed again with "Add Menu"-button. **Reproduce** Click on "Add New" (is open), click again to close (is still open). **Solution** It's something about the hover-state in mobile safari. Adding `ontouchstart` to `<body>` could help. Better, listen for events and change states via javascript. ## ProcessLister not reachable **Description** Lister (filter/related) is not "reachable". **Reproduce** 1. Open backend on iOS. 2. Try to find/reach "lister" and "recent-pages" **Solution** Add a dropdown-menu with infinite levels of nesting. See also [#show-fullpage](#show-fullpage) ## <a name="input-auto-zoom-bug">#</a> Input auto zoom bug **Description** If an input gets the focus, the page will zoomed in a bit. Causes horizontal scrollbars. See also [#horizontal-overflow](#horizontal-overflow) **Reproduce** Focus a text input element in the backend. **Solution** `html { text-size-adjust: 100%; }` **References** - http://stevenosloan.com/articles/2013/prevent-zooming-on-forms/ - http://stackoverflow.com/questions/2989263/disable-auto-zoom-in-input-text-tag-safari-on-iphone ## <a name="horizontal-overflow">#</a> Horizontal overflow **Description** Causes horizontal overflow on some pages, mostly because of long words/text. See also [#input-auto-zoom-bug](#input-auto-zoom-bug) **Reproduce** View "ProcessPageEditImageSelect"-configuration page **Solution** `word-wrap: break-word` ## SystemNotifications ghost doesn't break words **Description** Ghosts do not break long text on iOS. **Solution 1** It's something with `position: fixed; width: 100%` and `position: fixed; left: 0; right: 0;`. **Solution 2** I've seen some problems with `word-wrap: break-word`, I think there are some bugs related to this topic. See also [#horizontal-overflow](#horizontal-overflow) ## ProcessPageSearchForm too small **Description** Input field is a bit too small, for my eyes. --- # UI/UX ## ProcessPageEditImageSelect image not scaled **Description** The currently edited image in modal is not scaled down. We are able to define dimensions (e.g. 800x600), it seems that the image will get exactly this pixel-values as dimension-properties, makes the thing feel not that responsive as it could/should. **Reproduce** 1. Open page with image field attached 2. Click an image (larger than the device viewport) to open modal. **Solution** Haven't looked deep in it, but something like this should help: `img { max-width: 100% ...` ## PageTable ### Drag breaks layout **Description** Dragged item is not longer in box-model (due `position:absolute`) and visually breaks the table. **Reproduce** Move cursor over table item > hold mousedown and drag ~1px. **Solution 1** Create clone and move this instead of original PageTableField. **Solution 2** Save offset, before the PageTableField gets `position: absolute`. ### PageTable optional sorting **Description** Sorting via drag-and-drop should be optional. Currently we can say that items added to PageTable are "pre-sorted" with `Inputfield_sortfields`, but they are furthermore sortable via drag-and-drop. **Solution** Add "Sortable via drag-and-drop"-option to PageTable ## NotificationBug alignment/position **Description** It's annoying to have the NotificationMenu-toggler move always up/down (and it looks a bit too "floaty" in my eyes). **Solution** Move the NotificationBug right to search form and "fix" (not `fixed`) it at the top. --- # Feature requests ## <a name="show-fullpage">#</a> Show fullpage **Description** It could be helpful to be able to switch (on mobiel devices) between mobile- and desktop version. **Solution** Add "Show fullpage"-link to footer ## Inline time picker on datetime field **Description** If the date picker is inlined (always visible) theres no time picker available. ## <a name="line-trough-draft-pages-asmselect">#</a> Line trough draft pages AsmSelect **Description** In PageLister a page with status "draft" is striked (~~line-through~~), should be the same in asmSelect (if "Allow unpublished pages" is enabled). See also [#asm-page-state](#asm-page-state) **Reproduce** 1. Enable draft pages on PageTable. 2. Change page status to draft. 3. Open the referenced page and view select-field item. ## <a name="asm-page-state">#</a> Indicate page-states in asmSelect **Description** Each state could visualized with different styles. See also [#line-trough-draft-pages-asmselect](#line-trough-draft-pages-asmselect) **Solution** - draft > ~~line-through~~ - hidden > opacity - locked > *italic* ## Image-reference selection **Description** Selecting already uploaded images, from any page, is a must have! **Solution** Indri is one great tool for this, https://github.com/ikayzo/indri ## Create page once **Description** It should be a possibility to create pages (one the same tree-level) just once, instead of renaming to "duplicate-page-name-1". **Reproduce** 1. Create new page with name "foo". 2. Create another page with name "foo". 3. Now you have "foo" and "foo-1". **Solution** Add "Singular"-option to templates to let us decide what we want. If this option-field is ticked later, on page edition show notification if page with name "foo" already exists and don't save, or ask what todo. ## Pre-select site-profile **Description** If there's just one site-profile to install, use it. ## Show full version number on installation **Description** During installation the version in footer-section is trimmed e.g. 2.5.29 => 2.5 ## Dynamically enable field deletion **Description** Ajax-check to enable "Delete field" after valid change on "Action"-tab.
×
×
  • Create New...