miguel-perez/smoothState.js

Relative links stop working after 1 cycle

Open

#200 opened on Jul 31, 2015

View on GitHub
 (6 comments) (0 reactions) (0 assignees)CSS (4,433 stars) (515 forks)batch import
bughelp wanted

Description

Demo: http://dirkvanveghel.nl/smoothbug/portfolio/

Steps to reproduce:

  • Click on About in the menu.
  • Click on Portfolio in the menu. (or the other way around, doesn't matter which page you start)

Expected result: You navigate to the Portfolio page.

Actual result: You navigate 'back' one directory too many, or just back to the root.

Tested in Chrome and FF.

Description: When you switch from Portfolio > About the first time it works, but when you want to navigate back to portfolio again via the same menu it fetches the URL wrong and goes back one directory too many it seems. When you refresh the bug is also gone, so I assume I didn't just code anything wrong. Sorry for my non-native English, or if I'm just doing something wrong.

Contributor guide

Tech stack
javascriptcss
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaScriptjQuerybasic understanding of smoothState.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate the smoothState.js library's handling of relative links during navigation. Focus on the `load` and `fetch` methods in the source code (likely in `jquery.smoothState.js`). Check if there is a state variable tracking the current URL that gets incorrectly updated after the first navigation cycle. Also review any history manipulation logic that might affect relative path resolution.