fix: adding a tab or maximizing a portlet now stick to the tabgroup #2307
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bjagg
requested review from
jonathanmtran,
cousquer,
jgribonvald,
ChristianMurphy,
loulou2u and
cbeach47
uPortal-webapp/src/main/resources/layout/theme/respondr/navigation.xsl
Outdated
Show resolved
Hide resolved
…tion.xsl Co-authored-by: Christian Murphy <christian.murphy.42@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
Description of change
When tabgroups were active, adding a new tab or maximizing a portlet would create a new "More" tabgroup rather than remain in the current tabgroup. The
tabManager.jscode supports tabgroups. It was looking for an ID that was not migrated to Respondr. This PR adds the needed ID.