Hi all,
I have an issue with WebTab from version 8.3 with Hotfix 2039.
When I opened many tabs from the WebTab (about 10 tabs), the ScrollButton appeared - it is correct.
But when I closed the first or second opened tab, then clicked on Scroll Button Left, the closed tab was auto visible without any content on it.
I tried to debug from JavaScript and its properties was: getVisible() = false, getEnable() = false.
Please help me to resolve this issue. What options from WebTab that I can set to fix this?
Thank in advance,
Nguyen Huu Chu
VNetSoftware LLC
Hi Viktor,
Thanks you for the detailed update.
I checked the ig_webtab.js and below is the header of that file:
/** ig_webtab.js* Version 8.3.20083.2039* Copyright(c) 2001-2009 Infragistics, Inc. All Rights Reserved.*/
I just found the comment line //vs 1121808 from this file. It seems that the second change was not included in this version of js.
Regards,
Chu
Hi Nguyen,
I checked content of ig_webtab.js in 8.3.20083.2039 and found that is has a partial fix. There were 2 changes to codes which were releated to scrollbuttons when tabs are hidden on client. The hot-fix was released in 3 weeks after 2nd change, but it was built from source codes before that 2nd change.
That second change (which was not included in 2039) was done for issue when scrollbuttons were disabled after 1st tab was hidden. Your description about reappearing tabs match with first part of fix, so, I am not sure if 2nd change is related to your application.
Please ensure that correct version of ig_webtab.js is used. You may check it, if you debug application and look at files within list of Script Documents. At the top of ig_webtab.js file you should find name of that file and build version. There is also should be a comment line with date like
//vs 1121808 (12/18/2008 - first change)
//vs 123108 (12/31/2008 - second change)
//vs 111408 (11/14/2008 - previous version)
If your application at run time uses ig_webtab.js version 2039, then it would be great if you attach your aspx (within Options tab) which can be used to reproduce that issue.
Thank you for a bug report. Similar issue was already reported and fixed few months ago. Please try the latest hot fixes.