Hi Folks
I'm not even sure how to describe these problems to this group:
(my page has the tab control with 6 active tabs)
1. any click on the 2nd TabItem, renders only the 1st & 2nd tab enabled after it's been clicked (and there is no code behind setting this).
2. a post-back on the 2nd TabItem completes the required actions expected in code, but the tabitem is refreshed with a control(s) from the masterpage (and the one on the masterpage content disappears). in this case, it is an asp:menu which is dynamically built for each user/site login.
we are scratching our heads here...
thanks
Hello Scott,
Thank you for submitting your inquiry to the Infragistics ASP.Net Forums. Which version and build of NetAdvantage are you working with? Also, which tab control are you using, the classic WebTab or the Aikido WebTab?If possible, please attach your Markup code for the Master and Content Pages so we may take a closer look. If you would not prefer to attach your Markup on this thread, let me know and I can open a support request for this inquiry.Thank you.Sincerely,Mike D.Developer Support EngineerInfragisticswww.infragistics.com/support
hi mike
we are working with v10.3, WebTab
we'd love to give you the code, but may we ask you to open up a request so we can ship you the code privately?
we are also looking into 2 other issues:
1. changing tab settings in the VS designer creates additional (more than one) tags like these:
<postbackoptions enableajax="True" enableloadondemand="True" />
we are worried that we may be introducing additional/unwanted postbacks as a result of this
2. adding a webhtmleditor on a tab "pins" the build process to a tab... let me explain
a. you have 6 tabs on a webtab control
b. your place the webhtmleditor is on the first tab
c. you build the web solution while viewing a tab OTHER than the first tab in the VS Designer
d. web solution always crashes on this page load event here:
Me.WebHtmlEditor_SiteGeneralInformationEdit.SpellCheckerID = Me.WebSpellChecker1.ClientID
e. go back to tab#1 in VS Designer, ALL builds/runs fine
* OUR REALLY BIG CONCERN HERE, IS THAT IN AN ENVIRONMENT WITH MULTIPLE DEVELOPERS, NONE OF US KNOWS HOW (OR WHAT TAB IN THE VS DESIGNER) THE LAST DEVELOPER LEFT THE PAGE ON.
* OUR BUILD & DEPLOY PROCESS COULD RUN w/o ISSUE, BUT THE PAGES WITH THE CONDITIONS MENTIONED ABOVE COULD BE CRASHING ALL OVER THE PLACE IN PRODUCTION (without there actually being a software bug, just a build bug).