Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[$Your price?] Android back button doesn't work in Web #548

Closed
SleepySquash opened this issue Sep 6, 2023 · 0 comments · Fixed by #657
Closed

[$Your price?] Android back button doesn't work in Web #548

SleepySquash opened this issue Sep 6, 2023 · 0 comments · Fixed by #657
Assignees
Labels
bug Bugs and incorrectness problems k::UI/UX UI (user interface) and UX (user experience) changes platform::android Specific to Android platform platform::web Specific to Web platform

Comments

@SleepySquash
Copy link
Contributor

SleepySquash commented Sep 6, 2023

Background

Мессенджер Gapopa.

Problem to solve

Проблема: СИСТЕМНАЯ кнопка "Назад" (или жест назад, в зависимости от лаунчера) на Android'е в веб приложении не возвращает на предыдущую страницу.

Чтобы повторить проблему, необходимо:

  1. Открыть приложение в браузере на Android'е.
  2. Открыть, например, чат "Заметки".
  3. Нажать на системную кнопку "Назад" (или произвести жест назад, в зависимости от лаунчера).
  4. Наблюдать, что приложение осталось на той же странице (предыдущая, список чатов, не открылась).

Сделать: исправить системную кнопку "Назад" (или жест назад, в зависимости от лаунчера) на Android'е в веб приложении.

Possible solutions

Для определения того факта, что кнопка "назад" (или жест назад, в зависимости от лаунчера) была нажата, иногда используется BackButtonInterceptor из пакета. Есть вероятность, что его наличие создаёт какие-то проблемы.

Кнопка "назад" (или жест назад, в зависимости от лаунчера) должна работать везде, не только в описанном сценарии. Нужно проверить работоспособность:

  • при активном звонке;
  • при открытии прикреплений в чате;
  • при нескольких страницах.
@SleepySquash SleepySquash added bug Bugs and incorrectness problems k::UI/UX UI (user interface) and UX (user experience) changes platform::android Specific to Android platform platform::web Specific to Web platform labels Sep 6, 2023
@SleepySquash SleepySquash added this to the 0.1.0-alpha.10 milestone Sep 6, 2023
@SleepySquash SleepySquash self-assigned this Sep 6, 2023
@SleepySquash SleepySquash moved this to Bugs in Roadmap Sep 6, 2023
@SleepySquash SleepySquash changed the title Android back button doesn't work in Web [$Your price?] Android back button doesn't work in Web Sep 29, 2023
@SleepySquash SleepySquash removed this from Roadmap Sep 29, 2023
@SleepySquash SleepySquash moved this to Todo in Freelance Sep 29, 2023
@SleepySquash SleepySquash removed their assignment Sep 29, 2023
@SleepySquash SleepySquash added help wanted This issue is looking for freelancer to work on it 💰 paid labels Sep 29, 2023
@SleepySquash SleepySquash removed help wanted This issue is looking for freelancer to work on it 💰 paid labels Oct 17, 2023
@SleepySquash SleepySquash removed this from Freelance Oct 17, 2023
@SleepySquash SleepySquash moved this to In Progress in Roadmap Oct 17, 2023
SleepySquash added a commit that referenced this issue Oct 17, 2023
#641, #548)

Additionally:
- fix Android back button not working in Web

Co-authored-by: SleepySquash <nordnikita@icloud.com>
@github-project-automation github-project-automation bot moved this from In Progress to Done in Roadmap Oct 17, 2023
github-actions bot added a commit that referenced this issue Oct 17, 2023
#641, #548)

Additionally:
- fix Android back button not working in Web

Co-authored-by: SleepySquash <nordnikita@icloud.com> 6f53210
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bugs and incorrectness problems k::UI/UX UI (user interface) and UX (user experience) changes platform::android Specific to Android platform platform::web Specific to Web platform
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants