3
Vote

TabContainer bugs introduced in the November 2011 release

description

The bug is very simple.

Since the Novembre 2011 release, if the TabContainer control is outside of the view of the browser when the browser loads, the browser will go down to be able to see the header of the TabPanel.

For example, if you put a lot of <br/> so you can't see the TabContainer when opening a page, the browser will "go down" to view at least the header of the TabPanel. It's like it now needs to be visible to be activated.

When we go back to the September 2011 release, everything is fine.

comments

Superexpert wrote Oct 23, 2012 at 4:18 AM

Can someone please send sample code to reproduce the current behavior and expected behavior?

DarkJaff wrote Oct 23, 2012 at 11:38 AM

You really don't need a sample code to reproduce this behavior:

1) Create one project with November 2011 release and one project with previous version (September 2011 will do)
2) Put a TabContainer in an aspx with 3 tabs for example (Do that in both project). You don't need any content in the Tabs I think.
3) Before the TabContainer, put approximatly 30 "<br/>". Depending on your screen size and/or resolution, maybe you will need more. The goal is that when you load the page, it's not visible, you need to scroll down to see it.
4) In the Project with November 2011 release, the page will automatically scroll down to the first tab of the TabContainer (BAD) but in the September 2011 release, the page will stay at the top and you will need to scroll down manually (GOOD)