Using BOLD or UNDERLINE etc.. and Backspace / Delete Causes Cursor Jump

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Chris27
    Member
    • Oct 2010
    • 70
    • 5.0.X

    Using BOLD or UNDERLINE etc.. and Backspace / Delete Causes Cursor Jump

    Hi Guys - My users are reporting an issue. Here is how a user described it. I can duplicate 100% of the time, but can't figure out what's going on.


    When typing in an editing window (from Post Reply or Post New Topic, etc):
    1. Type some normal text
    2. Then, change the style via cmd-b/cmd-i (ctrl on Windows), and then type some more text
    3. Hit Delete (Mac)/Backspace (Win)
    4. The cursor will jump back to the beginning of the style change.


    Best explained via screenshots. Here's an example of some text right before hitting delete:

    Screenshot 1 below



    And immediately after hitting the delete button:

    Screenshot 2 below



    Chris Connaker

    Founder
    Computer Audiophile
  • Mark.B
    vBulletin Support
    • Feb 2004
    • 24288
    • 6.0.X

    #2
    Could be related to THIS. Is it Chrome by any chance?
    MARK.B
    vBulletin Support
    ------------
    My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
    My Unofficial vBulletin Cloud Demo: https://www.adminammo.com

    Comment

    • Chris27
      Member
      • Oct 2010
      • 70
      • 5.0.X

      #3
      Originally posted by Mark.B
      Could be related to THIS. Is it Chrome by any chance?
      Happens with Chrome and Safari but not Firefox.

      My readers report:

      Platforms where I've seen this problem:

      Win10-x64 Anniversary update:
      Chrome Version 54.0.2840.87 m
      Microsoft Edge 38.14393.0.0

      MacOS Sierra:
      Chrome Version 54.0.2840.87 (64-bit)
      Safari Version 10.0.1 (12602.2.14.0.7)
      Chris Connaker

      Founder
      Computer Audiophile

      Comment

      • Mark.B
        vBulletin Support
        • Feb 2004
        • 24288
        • 6.0.X

        #4
        Yes it's a related issue to the one I linked to. It occurs in Webkit / Blink based browsers.

        It will require a fix to be implemented by Chrome, whether they do so or not is another matter.

        Users for whom it's a big problem should switch to the standard editor rather than the WYSIWYG.
        MARK.B
        vBulletin Support
        ------------
        My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
        My Unofficial vBulletin Cloud Demo: https://www.adminammo.com

        Comment

        • Chris27
          Member
          • Oct 2010
          • 70
          • 5.0.X

          #5
          Originally posted by Mark.B
          Yes it's a related issue to the one I linked to. It occurs in Webkit / Blink based browsers.

          It will require a fix to be implemented by Chrome, whether they do so or not is another matter.

          Users for whom it's a big problem should switch to the standard editor rather than the WYSIWYG.
          Thanks Mark.
          Chris Connaker

          Founder
          Computer Audiophile

          Comment

          • Chris27
            Member
            • Oct 2010
            • 70
            • 5.0.X

            #6
            Originally posted by Mark.B
            Yes it's a related issue to the one I linked to. It occurs in Webkit / Blink based browsers.

            It will require a fix to be implemented by Chrome, whether they do so or not is another matter.

            Users for whom it's a big problem should switch to the standard editor rather than the WYSIWYG.
            How can this be a Chrome / Webkit / Blink thing if it happens in Microsoft Edge browser too?
            Chris Connaker

            Founder
            Computer Audiophile

            Comment

            • Mark.B
              vBulletin Support
              • Feb 2004
              • 24288
              • 6.0.X

              #7
              Originally posted by Chris27

              How can this be a Chrome / Webkit / Blink thing if it happens in Microsoft Edge browser too?
              The version of CKEditor used in vB4 is several years old now, so it could be an incompatibility with newer versions of browsers.

              vB4's editor isn't going to be updated, as this would be a major undertaking and development work is focused on vB5 now (which uses a newer version of CKEditor anyway), so the only workaround is to use the standard editor, if it's causing problems.
              MARK.B
              vBulletin Support
              ------------
              My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
              My Unofficial vBulletin Cloud Demo: https://www.adminammo.com

              Comment

              Related Topics

              Collapse

              Working...