conditionally visible tab content available when using keystrokes

Hi, In our 2.5.3. project we make extensive use of conditionally visible tabs. This seems to work fine. However, we do encounter an issue now. In a tabbed region containing e.g. 3 tabs A, B and C, of which B is conditionally visible and in this case for this user INVISIBLE. The UI shows tabs A and B (which is OK). However when the cursor is on tab A and we use ARROW RIGHT key on the keyboard, the content (datagrid) of (the hidden) tab B is displayed. The Tab tag still shows A though. Pressing the ARROW RIGHT button once more will show Tab C and its contents. This is a security risk in our situation and we would like to resolve it. Bug? Workaround? Upgrading to the most recent version is not considered an option at this moment. Brian
3 answers

In the Release Notes for Mendix 2.5.5:

Ticket 8319: Fixed hidden tab being selectable with key navigation.

I guess you need to upgrade to a newer version.


You cannot avoid this, since the information is present anyway, just not visible. If you check the css code below (which is taken from Firebug), you can see how a tabpane is made invisible: by including a ' style="display: none;" '. Removing this information in Firebug immediately makes the tabpane visible. This is simply the way Mendix works.

CSS code:

div class="dijitTab" lang="" dojoattachevent="onclick:onClick" dojoattachpoint="titleNode" role="presentation" dir="" widgetid="mxuiwidgetMxTabContainer0tablistmxuiwidgetMxTabContent6" style="display: none;"

end CSS code

The only way to make sure a user can not see this information is to prevent it being sent to the client. You could configure entity access, or make a new form for this user role which does not include the tabpane you want to hide.


In 2.5.6 you can set the form with tabs on not editable, but if you then create a dataview in a tab and make a column editable you can inline edit the record.

If I recollect right this was a bug and resolved in later editions. So the only sollution would be to upgrade to a newer version. I hope that somebody from Mendix still can recollect this bug and answer this.