dartdoc html causes user to lose context when navigating

[tvolkert]

Steps to reproduce

• Visit https://docs.flutter.io/flutter/material/material-library.html
• Scroll down to the ThemeData class in the right-hand-side class navigation
• Click on the class
• Go to click on one of other classes you were just browsing, like TextSpan

Expected behavior

You expect to keep your navigation context as a visual anchor of where you are in the site.

Actual behavior

Since the page doesn't use frames, the whole page is reloaded. Further, the constants, typedefs, and classes now like on the left side of the page, where they were on the right before. I'm no usability expert, but I find this totally jarring as a user (still to this day, even after having used Dartdoc for over a year).

Suggestion

We should take a page from Javadoc, which I think got this one right. The listing of your packages should stay in a constant location, as should the listing of your constants-typedefs-classes-etc. I think html iframes is probably the way to go with this, but there may be others.

[sethladd]

Thanks. Can you reword the title to be more about the problem, less about the solution?

…

On Wed, Dec 14, 2016, 6:03 AM Todd Volkert ***@***.***> wrote: Steps to reproduce - Visit https://docs.flutter.io/flutter/material/material-library.html - Scroll down to the ThemeData class - Click on the class - Go to click on one of other classes you were just browsing, like TextSpan Expected behavior You expect to keep your navigation context as a visual anchor of where you are in the site. Actual behavior Since the page doesn't use frames, the whole page is reloaded. Further, the constants, typedefs, and classes now like on the left side of the page, where they were on the right before. I'm no usability expert, but I find this totally jarring as a user (still to this day, even after having used Dartdoc for over a year). Suggestion We should have a page from Javadoc, which I think got this one right. The listing of your packages should stay in a constant location, as should the listing of your constants-typedefs-classes-etc. I think html frames is probably the way to go with this, but there may be others. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1288>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAVZ0t1D05km3vKJHDAA4QdlVSnChAoks5rH_cggaJpZM4LM9Gs> .