tensorflow / tensorflow/tensorboard
Page/tab navigation breaks in MS Edge after first page change
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 1
Description
Hello, I've noticed a navigation issue in TensorBoard, when using Microsoft Edge.
Basically, the navigation system just stops working after the first navigation. You open TensorBoard and land in the "scalars", and navigating to another page (eg. "graphs") works fine.
After that, attempting to open another page, or to go back to the "scalars" page doesn't work anymore. You can see from the attached screenshot, that I've clicked on the "scalars" page and the label change animation played (notice the "scalars" tab is highlighted), but the navigation never starts. The URL is updated as well, even if the navigation isn't performed.
My workaround right now is to close/reopen the TensorBoard page if I need to go back to the first page, but that's not really convenient, of course.
Here are some info:
- TensorBoard/TensorFlow version 1.8.0
- Windows 10 (tested with both FCU and April Update)
- Python version 3.6.5
- Microsoft Edge (version 42.17134.1.0, EdgeHTML version 17.17134)
And here's the screen mentioned above:

Hope this helps!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reported sequence in Microsoft Edge: open TensorBoard, navigate from scalars to graphs, then select another page or return to scalars. Trace the TypeScript navigation implementation from that failing interaction and verify that repeated navigation updates both the URL and displayed page without reopening the tab.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100