Width of Container object tabs is fixed(narrowed)| Limitation of container object

[Qlik1_User1]

Hi All,

I am using Qliksense Sep 2019, and seems there are  limitation in Container objects.

1. Width of Container object tabs is fixed, means we can't adjust tab width.
2. If tab name is long (50 characters) than full name of tab is not shown, name of a tab is getting cut and only partial name is displayed followed by dots.
3.An extra white space is automatically getting  added in  last tab.
4. There is no proper lines highlighted between tabs , to show as a segregator.

Please suggest some alternative for these , also if is there any Qlik support article on these points please share.
Please share any other limitations that container object has.

[ArnadoSandoval · Accepted solution]

Hi @Qlik1_User1 

I will do my best to explain the container and QlikSense User Interface, I am using QlikSense April 2020.

1. Width of Container object tabs is fixed, means we can't adjust tab width.

Qlik implements a Responsive UI, with the Responsive design defining size attributes is not a priority, and it is not required, you may find this article: Static VS Responsive Design: What You Need to Know; besides, if we are talking about a container, each one of its tabs, hints the user about the information contained in any particular tab, it is not that we are going to provide a label long enough to write a 100 characters text (It sounds like a novel). I managed to write a 28 character long tab in my environment.  

2. If tab name is long (50 characters) than full name of tab is not shown, name of a tab is getting cut and only partial name is displayed followed by dots.

This is related to the first question, still the answer is similar, Qlik implements a Responsive design where we do not specify size attributes.

3.An extra white space is automatically getting  added in  last tab.

Actually, it could be more that an extra white space, internally Qlik realize the size of the screen, it could be a mobile, 8" tablet, or large monitor, Qlik workout how many tabs could be displayed on the space available, padding the right side of the screen; This is also part of the responsive design.

 4. There is no proper lines highlighted between tabs , to show as a segregation.

Indeed, containers' tabs had been featured with so many styling stiles by so many development environments, when at the end of the day, the end users wants to know is a quick reference (a hint) of what information is contained in the tab. QlikSense took a simple approach with its tabs, the application is not using too much time formatting and colouring them, they are functional.

I hope my observations-responses to your questions guide you into understanding the way Qlik works.