Lost drafts in iOS apps due to swipe-up gesture

제품 지원
1

I’ve lost a few drafts using the iOS app since the interface update. This happens sometimes when I’m scrolling up and down among previous posts as I type, and accidentally trigger a gesture to swipe the whole forum down, returning me to the forum selection screen. When I open the forum again, no draft.

I’m guessing this is low-probability, high pain. It’s not happening constantly, but when it does, it’s not fun losing a draft. Especially a long one. Especially a long one that I typed out with my thumbs.

2

can you repro consistently? If you re enter the topic draft should reopen (also see drafts section in your user profile )

3

Yeah did you try re-entering the topic? Unlikely it was actually lost. Try testing the scenario.

4

Yeah, I’ve been able to repel a few times. But it might be that I’m losing drafts that don’t reach the save timeout.

5

Drafts have to be over the minimum post character length to save (20 chars) and the automatic draft saves happen about every 60-90 seconds as I recall, I would need to check the code.

6

Roger that, but even if draft saving is fine, it’s annoying to be closing forums and losing my place all the time.

I do a lot of referring to prior posts when I write for Discourse. It happened again responding here.

7

We need specific repro steps. Or maybe don’t use the app, try without the app for a bit and see if things improve? I find the app just adds complexity, personally?

8

iOS 12.4.1 iPhone 6s

  1. Visit topic.

  2. Tap reply.

  3. Get both reply box and prior posts in view.

  4. Scroll posts up vigorously.

I don’t think your finger has to hit the title bar. Pressure sure I’ve repro’d just attempting to scroll posts.

9

So this is app specific, it’s interpreting your scrolling as an app gesture? Can you repro this in the Safari browser (no app)?

10

The app does have a “swipe down to dismiss current screen” gesture. And I confirm, scrolling vigorously up and down does trigger the issue. Especially if scrolling from the top third of the screen downwards.

I will look into possible ways to address this. The gesture can be disabled, but it is useful, especially in cases where the current is unresponsive and the footer nav is not visible.

11

Not following though, does it nuke a saved draft or simply dismiss the page?

12

I don’t think it’s possible it nukes a saved draft.

But I did notice today that the slide-down-to-dismiss gesture is a lot easier to invoke on an iPhone without a notch (6s, 7, 8) vs. one with a notch.

I think the easiest solution here is to remove the gesture for notchless iPhones.

14

That sounds good to me!

15

@kemitchell 이 문제에 대해 약간 다른 방식으로 수정을 구현했습니다. 노치가 없는 iPhone에서는 위에서 아래로 스와이프하여 닫는 제스처가 여전히 활성화되어 있지만, 트리거를 더 어렵게 만들기 위해 파라미터를 수정했습니다. 이제 사용자는 제스처를 실행하려면 화면 상단 10% 부근(Discourse 페이지 헤더 근처)에서 더 높은 위치에서 스와이프를 시작해야 합니다.

해당 수정 사항은 앱의 베타 버전에서 사용할 수 있습니다(이 링크를 통해 TestFlight에서 베타 버스를 설치하세요).