You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Within each step, we move to the next step using a button that performs a router.push with the path of the next step.
The problem I'm having is maintaining correct "back" behavior on the browser. The default / step router-views render the previous step correctly, but the o-steps component, which has a marker of the current step, doesn't. It still shows the pre-back step highlighted. I guess this makes sense as the steps component isn't aware of the router or use it in any way.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a page with several steps that the user progress through, each step is mapped to a different path using a router.
Within each step, we move to the next step using a button that performs a
router.push
with the path of the next step.The problem I'm having is maintaining correct "back" behavior on the browser. The
default
/step
router-views render the previous step correctly, but theo-steps
component, which has a marker of the current step, doesn't. It still shows the pre-back step highlighted. I guess this makes sense as the steps component isn't aware of the router or use it in any way.What would be the correct way to handle this?
<Editor> template
:Beta Was this translation helpful? Give feedback.
All reactions