Since navigationPane is about to be documented(? TRINIDAD-626) is there any
interest in an alternative implementation (see below)?
Or is there an option to have the current implementation wrap the
navigationPane.tabs?
Chris....
Chris Hane wrote:
I ran into the problem I describe below which is caused by using a bunch
of nested tables and a ccs property overflow:none (or something like
that - I might have the exact name wrong).
Anyway, I created a second implementation of the tab look based on this
tutorial:
http://tutorials.mezane.org/tabbed-navigation-using-css/#Introduction
If there is any interest I can create a patch and apply it to a JIRA
issue for people to look at it.
Thoughts,
Chris....
Chris Hane wrote:
I am experimenting with replacing our custom navigation with
<tr:navigationPane> and ran into an interesting scenario that I hope I
am just overlooking something on.
If the window size is such that there are more tabs then fit on the
screen horizontally, the tabs to the right of the window break are not
accessible or visible even if the user scrolls the entire window to
the right.
I checked out the demo provided with Trinidad and it does the same
thing. See
http://localhost:8080/trinidad/faces/components/panelPage.jspx and
resize the window so that the tabs start to disappear.
Is this the expected behavior? Are there any workarounds.
I am using Trinidad 1.0.0. And the code fragement is:
<tr:navigationPane var="foo"
value="#{loggedInUser.menus}"
hint="tabs">
<f:facet name="nodeStamp">
<tr:commandNavigationItem text="#{foo.name}"
destination="#{foo.url}"
selected="#{foo.identifier==section}"/>
</f:facet>
</tr:navigationPane>
Thanks,
Chris....
