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

BUG: indexmenu redirecting namespaces #241

Open
Garrettlynch opened this issue Apr 19, 2021 · 3 comments
Open

BUG: indexmenu redirecting namespaces #241

Garrettlynch opened this issue Apr 19, 2021 · 3 comments
Labels

Comments

@Garrettlynch
Copy link

I'm experiencing what seem to be several bugs or different behaviour from other platforms on IOS (9.3.5) in every browser I've tested (Chrome and Safari so far).

  1. Clicking on any namespace that does not contain a start.txt page does not open the namespace but instead redirects to the sitemap with the namespace open.
  2. When using a start.txt to rename namespaces and enabling 'Hide headpages' clicking on the namespace does not open the namespace but instead takes you to the start.txt page. In this second issue it's impossible to navigate to other pages in the namespace.

Appreciate the IOS I'm using is old but opening namespaces works perfectly in the sitemap so unclear as to why it is failing in indexmenu.

@Klap-in
Copy link
Collaborator

Klap-in commented Jul 10, 2021

I recognize this UX issue. Partly this is a feature, it add a link to startpage of the namespace. But, of course, it is problematic that it makes folding/unfolding not possible. Or jumps to the index instead.

Could you give an example of the syntax you are using? I'm right you are using the nojs version?

@Garrettlynch
Copy link
Author

Hi, no I wasn't using the nojs version. I can't give you any example of my setup anymore as I've now abandoned using indexmenu as it made my wiki unusable on IOS.

@Klap-in Klap-in reopened this Jul 10, 2021
@Klap-in
Copy link
Collaborator

Klap-in commented Jul 10, 2021

Ok, thanks for the feedback. I have seen this behaviour sometimes as well, so I think it is a real bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants