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
Describe the bug
We are facing the issue in progress bar percentage calculation while having hidden steps in the wizards.
var widthPercentage = width / this.steps.length * (idx+ 1) / width * 100;
this.steps.length - This will always give length of all steps including the hidden steps.This needs to be update only length of the visible steps. and idx always giving the stepid instead of the index of the current step.
To Reproduce
Steps to reproduce the behavior:
Total Steps = [1,2,3,4,5,6,7,8,9]
hide some steps [3,8]
Check clicking next after the hidden step;
now in progress bar you feel issue.
Expected behavior
var widthPercentage = width / visibleSteps.length * (currentactiveinvisiblestepIdx + 1) / width * 100; Screenshots
If applicable, add screenshots to help explain your problem.
Current Active Step is 4. But progress bar completed. Desktop (please complete the following information):
OS: Windows
Browser chrome
Version:134.0.6998.89
The text was updated successfully, but these errors were encountered:
Describe the bug
We are facing the issue in progress bar percentage calculation while having hidden steps in the wizards.
var widthPercentage = width / this.steps.length * (idx+ 1) / width * 100;
this.steps.length - This will always give length of all steps including the hidden steps.This needs to be update only length of the visible steps. and idx always giving the stepid instead of the index of the current step.
To Reproduce
Steps to reproduce the behavior:
Total Steps = [1,2,3,4,5,6,7,8,9]
Expected behavior
var widthPercentage = width / visibleSteps.length * (currentactiveinvisiblestepIdx + 1) / width * 100;
Screenshots
If applicable, add screenshots to help explain your problem.
Current Active Step is 4. But progress bar completed.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: