cancel
Showing results for 
Search instead for 
Did you mean: 

Internet Explorer limitation for Web Dynpro Table Data

Former Member
0 Kudos

Hello everybody,

I am having a trouble while trying to display a Web Dynpro table in Internet Explorer. This table is bound to a Context Node that is filled up manually with code, and for example if I passed more than 116 elements to the node the table only shows 116. Since this issue only happens with IE, I consider that it is related to the client part, something related with JavaScript. Any idea/suggestion?

Many thanks in advance,

Jesus

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member197348
Active Contributor
0 Kudos

Hi Jesus,

Welcome to SDN!

Are you getting any error message? You said "this issue only happens with IE" that means, is it working properly in any other browsers ? Web Dynpro is client independent. It should not behave like that. There may be little differences in layout rendering in different browsers but missing part of the data is impossible as for as I know. Can you give more details like how it is working in different browsers when the table has below 116 elements and above 116 elements? Are you using any scroll container for the table? Which version of IE, NWDS and EP are you using?

Regards,

Siva

Former Member
0 Kudos

Hello Siva,

Thank you very much for your response. There is no message error, it is just not showing the entire node content, the weirdest thing is that even though WD is client independent this only happens with Internet Explorer. It works properly with any other browser such as Mozilla FF, Chrome and Safari browsers when the table has above 116 elements. When the table has below 116 elements it works properly with any browser. I have tried with IE6.0 and 7.0 using NWDS 7.0 and EP 7.0 SP 18.

The table is child of a Group element which in turn is child of the Root Element.

Best Regards,

Baez

Former Member
0 Kudos

Such strange effects may occur if the HTML table nesting exceeds a certain limit. Can you try to reduce the nesting of containers in your screen and check if this solves the issue?

Armin