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
The issue is intermittent and seems to only be reproducible by some users. I can reproduce it fairly consistently in Edge, but not at all in IE 11 or Firefox (and it also doesn't reproduce in Edge if I refresh using ctrl-F5). Some others on the dev team can't reproduce it all, but several users of the application are reporting issues (some also see it in IE 11).
This page also exists on an internal "preview" server that the client uses to preview changes before releasing them publicly, but as far as I am aware the issue only exists on the above public server.
About 1/3 of the way down the page, there is a section called "Step by Step". There should be two tabs ("Level 1", and "Level 2") just below that heading. The issue is that sometimes, the "Level 1" tab is displayed, but the "Level 2" tab is not displayed.
This app has been in production for several years without issue and this problem has only been noticed within the last couple of weeks. Our best guess is that there is some sort of network delay causing the component not render correctly for some users. Note that we have recently migrated the application to a new web server, but from what we can tell this started happening for the client before that migration took place.
I have tried to force the tabs to render using $( ".wb-tabs" ).trigger( "wb-init.wb-tabs" ); as described in the documentation but that did not resolve the problem.
We are currently developing a new version of ORT which will include an upgrade to the latest CDTS version, but it has not been deployed yet (it doesn't appear when testing locally, or on our test server - but neither does the above issue) so I can't confirm whether the issue still exists using the latest version.
Any insight on what may be the issue would be greatly appreciated.
Thanks!
The text was updated successfully, but these errors were encountered:
We have client reports of tabs (https://wet-boew.github.io/v4.0-ci/docs/ref/tabs/tabs-en.html) not displaying correctly on the pages of the ORT application.
The app is currently using CDTS v4_0_29.
The issue is intermittent and seems to only be reproducible by some users. I can reproduce it fairly consistently in Edge, but not at all in IE 11 or Firefox (and it also doesn't reproduce in Edge if I refresh using ctrl-F5). Some others on the dev team can't reproduce it all, but several users of the application are reporting issues (some also see it in IE 11).
One example page in question is the following: http://ort.prv/en/procedure/task/out_canada_regular_ben.html
This page also exists on an internal "preview" server that the client uses to preview changes before releasing them publicly, but as far as I am aware the issue only exists on the above public server.
About 1/3 of the way down the page, there is a section called "Step by Step". There should be two tabs ("Level 1", and "Level 2") just below that heading. The issue is that sometimes, the "Level 1" tab is displayed, but the "Level 2" tab is not displayed.
This app has been in production for several years without issue and this problem has only been noticed within the last couple of weeks. Our best guess is that there is some sort of network delay causing the component not render correctly for some users. Note that we have recently migrated the application to a new web server, but from what we can tell this started happening for the client before that migration took place.
I have tried to force the tabs to render using $( ".wb-tabs" ).trigger( "wb-init.wb-tabs" ); as described in the documentation but that did not resolve the problem.
We are currently developing a new version of ORT which will include an upgrade to the latest CDTS version, but it has not been deployed yet (it doesn't appear when testing locally, or on our test server - but neither does the above issue) so I can't confirm whether the issue still exists using the latest version.
Any insight on what may be the issue would be greatly appreciated.
Thanks!
The text was updated successfully, but these errors were encountered: