Page MenuHomePhabricator

Mobile: After saving a redlink page, the user is redirected to the previous page (typically the page the redlink was on) rather then the newly created page
Closed, ResolvedPublic

Description

Steps to reproduce:

1.Open a page with Mobile VE with desktop safari or iOS safari
2.Create a link to a new page and save the page
3.Go to that new page that you just created link to
4.Edit that page and save it

Observed Result:

It will redirect you to the page that you started with at step1

Environment:Betalabs and test2


Version: unspecified
Severity: normal
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=60848
https://bugzilla.wikimedia.org/show_bug.cgi?id=65041
https://bugzilla.wikimedia.org/show_bug.cgi?id=69559

Details

Reference
bz67639

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 3:42 AM
bzimport set Reference to bz67639.
bzimport added a subscriber: Unknown Object (MLST).

bingle-admin wrote:

Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/wdlVRRim

Sounds like another lazy-loading bug.

OT: I notice you are testing VisualEditor in alpha since the bug is assigned to alpha. Please don't.... Please use beta which is more stable and will help us filter out bugs in VE vs bugs in mobile.

Can you confirm the above problem happens in the alpha mode or is it beta mode (it does indeed sound like alpha)?

Just checked with Rumana and it's actually an issue in beta mode too.
So not necessarily related to ajax page loading/link hijacking :)

Reproducing this bug is currently blocked by bug 68249.

The issue here is that we're adding a hash to the URL when we launch the editor, and then doing history.back() after it's saved to restore the original URL. The only problem is that redlinks link directly to the editor, so once you're done, going back takes you to the previous article. Linking directly to the editor is the correct behavior (it's the same as is done on desktop). The problem is the history.back() hack (IMO).

I think this bug is actually the same as bug 60848 and bug 65041. Bug 60848 was closed by Jon as WONTFIX. Should we reopen it? Bug 65041 is just another specific case of the underlying issue.