User317523852 posted
uh...that is a bit impossible at the moment. But I found what went wrong....in the web.config file we added a few lines of code in the browse caps tag.
so what is happening is that the mobile browser is getting identified as some god damn browser and .NET doesn't know where to find the mobile controls for the detected browser. Hence the error i mentioned showed up.
The browsecaps stuff was added to prevent panel controls getting rendered as table in safari and some other browsers.
Can someone suggest a fix for the browsecaps stuff...is there anyother fix for the panels getting rendered as tables in safari.