12
  • Text selection and cursor position rendered wrong if input contains "bad" text [Mojave]

  • BugsDesktopPlanned

Steps to reproduce:
I first noticed this issue with GitHub, but actually it now happens in this very feedback form! Specifically, in some circumstances, if I select a word by double-clicking it, the selection appears in the wrong place. Indeed this seems to happen if certain strings occur in the text; for example the semicolon in this sentence triggers it.

To illustrate what I mean, I double clicked the first occurrence of the word "semicolon" in the preceding paragraph. Note how the selection is not placed quite correctly. This gets worse the more "problematic" characters are in the input. Worse (to me) is that also cursor positions are not right anymore. This turns editing into a nightmare: you click somewhere to insert something or maybe fix a typo, and the edit happens in a different place.

Other "bad" character sequences seems to include $( or also :// as it appears in URLs, and more stuff that is regularly part of source code.

This is not affected by compatibility mode, and it works fine in Safari/Firefox/Chrome/...

Expected behavior:
The text selection and cursor position should be correct.

Orion and macOS:
Orion 0.99.109.1-beta (WebKit 613.1.12)
macOS Version 10.14.6 (Build 18G9323)
MacBookPro15,3

Image/Video:

    Hmm, I can't reproduce this as you've described, adding any of those characters or strings doesn't cause any issues. Do you have any extensions installed?

      I've observed a similar issue on Mojave for some time during a number of Orion releases. It seems the issue is specific to only the problematic text which causes it once entered. I've attached an example video snippet of a message I was editing in Fastmail's web interface, where I could move the text shown around the message body (just using the Delete key, as I recall) yet the cursor hid behind the center of some character glyphs regardless of where this string was in the text box. Highlighting the text in order to trigger the bug isn't necessary, but I suspect the two problems are related.

      If it helps, the only extension I'm currently running is Bitwarden.

        No active extensions:

        Orion 0.99.109.1-beta (WebKit 613.1.12)
        macOS Version 10.14.6 (Build 18G9323)
        MacBookPro15,3

        Session Info:

        Enabled Extensions:

        Disabled Extensions:

        • 1Password – Password Manager (firefox)
        • uBlock Origin (firefox)

        Non Default Settings:

        • ContentBlockerLastUpdated => 2021-12-21 00:00:00 +0000
        • CustomAppIconData => <>
        • FirstLaunch => 0
        • HyperlinkAuditingEnabled => 0
        • LastUsedBuildVersion => 109.1
        • PreCompiledContentRuleListVersion => 109.1
        • LastCrashCheckDate => 2021-12-28 12:14:06 +0000
        • NetworkPredictionEnabled => 0
        • NextBookmarkID => 5
        • NextDownloadID => 3
        • SavedWindowSize => 1680.0,1027.0
        • SavedWindowPosition => 0.0,0.0
        • QuitWithConfirmation => 1
        • ActiveLibraryTab => extensions
        • ActivePreferenceTab => appearance
          11 days later

          An easy way to trigger the cursor rendering problem here - type a colon into the Google search box before a query.

          In the example above, the cursor is correctly deleting items next to itself, but the problem with deleting text (incorrect cursor positioning) can also be replicated by entering multiple colons into the middle of a search query.

          In the second example, the cursor also jumps forward past the end of my entry when I use the right arrow key to move through the text.


            13 days later

            Steps to reproduce:
            Cursor is offset in entered text after any period as if a space was inserted after each period.

            Open the comment box on any orionfeedback post (also works on translate.google.com). Type something with periods and no spaces (i.e. version 0.99.111 beta). Then select text with cursor. Spaces will appear after the periods only when selected. Additionally, trying to edit beta (or anything after the periods) will result in the cursor being visually offset from where the typing is inserted.

            Seems that spaces are inserted similarly before semicolons;

            No problem in safari. Bug persists in compatibility mode.

            Expected behavior:
            <What you expected to happen?>
            Cursor should not be offset, typing should be entered where it is placed. No spaces should be visible after periods on selection unless typed there.

            Orion, OS version; hardware type:
            Orion version 0.99.111 beta
            MacOS Mojave version 10.14.6, MacBook Pro (Retina, 13-inch, Late 2013), 2.4 GHz Intel Core i5
            `
            Image/Video:
            <Copy/paste or drag and drop to upload images or videos (up to 20MB)>

              I can replicate this on Mojave (just submitted this bug before seeing this post https://orionfeedback.org/d/1482-cursor-offset-in-entered-text-boxes-when-punctuation-is-used) but it's worth noting this only started happening to me after I updated orion. Was not happening on version 0.99.110-beta for me but is happening on 0.99.111-beta. Unless this was fixed and then reappeared, it could be the act of updating itself that triggers the bug.

                Merged 5 posts from Cursor offset in entered text boxes when punctuation is used.
                  a year later
                  5 days later

                  +1 . I have been having the same issue since forever, but thought it was part of the beta nature. Currently happening on MacOS 10.14

                  • Vlad replied to this.
                    Vlad changed the title to Text selection and cursor position rendered wrong if input contains "bad" text [Mojave] .

                      Vlad

                      1. Go to any Github's project
                      2. Navigate to "Issues"
                      3. Write a filter, enter
                      4. Try to edit the filter
                      5. The typing cursor doesn't match the content

                        4 months later

                        Steps to reproduce:

                        1. Create a new issue here
                        2. Type something that looks like a domain name inside parenthesis, close the parenthesis, and then type some more text. Make sure all of the text fits on a single line. Something like this:

                        Test is some text. (This contains something.lookslikea.domain) Here is some more text.

                        1. Click the text after the parenthesis to move the insertion point
                        2. Try typing more text
                        3. Note that the text appears in the wrong place

                        Orion, OS version; hardware type:
                        Version 0.99.124.1-beta (WebKit 616.1.10)
                        macOS 10.14.6

                        edit: I just observed this same bug in a text field on another website. So this should probably be recatorgized as a general Orion bug.

                        • Vlad replied to this.

                          Video attached. Note where I'm clicking vs. where text appears.

                          • Vlad replied to this.