7

When I try to edit text towards the end of a long post (or sometimes middle, for very long posts), my cursor disappears. Where exactly this happens seems to depend on where the scroll bar is.

I can't see where I'm typing except that text appears (or disappears, when backspacing), and trying to move around my cursor is hopeless because tapping doesn't make it appear and neither does holding the spacebar. I can't see if I have any text selected either (as I sometimes end up deleting the entire body of the post). Examples of a few answers where this happened:

Cursor is between community and the period when I was backspacing:

cursor missing from CW FAQ answer

I tested it on two different browsers (iOS Chrome and iOS Safari) on different devices and it happens on both. It also happens on the preview editor. (I have not encountered this on desktop, which is the device I have to switch to in order to make edits.) It doesn't happen on every answer, only when the answer is long or maybe has some complicated formatting. It also seems to happen in both editor modes.

Significantly, this is preventing me from editing something on a private Team (where this is the only editor, and I also see this happening on questions), so it should be fixed.

7
  • 5
    Can you add a gif showing what this looks like?
    – Justin
    Commented May 15, 2022 at 14:45
  • 1
    Have you only experienced this in iOS? Or on other operating systems/platforms as well?
    – V2Blast StaffMod
    Commented Jun 7, 2022 at 4:57
  • @V2Blast It's only been on iOS but it's severe enough that it prevents me from editing a bunch of my answers.
    – Laurel
    Commented Jul 13, 2022 at 18:21
  • 2
    This might be worth adding as a bug report on the Beta release post.
    – Justin
    Commented Jul 19, 2022 at 17:52
  • 2
    Ticketed in the repo: github.com/StackExchange/Stacks-Editor/issues/206
    – Jeremy
    Commented Aug 27 at 0:49
  • 1
    @Jeremy but this bug doesn't even have the status-review tag here, which means it's not on SE developers radar or backlog. With hundreds of other bugs already there, I'm afraid it's long years until a developer will actually even take a look on this one. As you said, they released a product broken beyond usability for a significant number of users. And I'm not surprised a bit: that's how SE "works" for way too long. Commented Sep 2 at 10:30
  • @ShadowWizard the report here was marked status-review two years ago, but since that developer is no longer with the company I’m sure you’re right that this isn’t being tracked. I wanted to bump it because I’ve been running into it as I’ve tried to use Staging Ground and it’s been incredibly frustrating, but I don’t have much hope.
    – Jeremy
    Commented Sep 2 at 15:49

0

You must log in to answer this question.

Browse other questions tagged .