You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Nicolas Castel had asked this question, but I couldn't comment with my answer so I'm starting a new post.
I've had this problem with the Keysight HTML Elements. I think I finally found the answer so I'll share.
The AUI Tabs relies on some simple html - an unordered list of anchors for the menu items and a matching set of div tags. See https://docs.atlassian.com/aui/8.5.1/docs/tabs.html for details. When the tab is clicked, two things happen. First, some javascript changes the visibility of the tabs so that only the one selected is shown. This is desired behavior. Next, the browser scrolls down to the anchor. It's this second behavior which is annoying and needs to be stopped.
My solution is to add a custom class, keysight-tab-menu-item-anchor, to the anchor tags so they are easy to extract with jQuery, then insert the following javascript:
AJS.toInit(function(){
AJS.tabs.setup();
// Without this hook, Confluence will scroll the page
// so that the top of the tab is at the top of the screen.
// This code triggers the tab change, than stops propagation
// or the event so the page is not scrolled.
$(".keysight-tab-menu-item-anchor").click(function(e){
AJS.tabs.change(jQuery(this), e)
e.preventDefault()
e.stopImmediatePropagation();
});
});
This code seems to work just fine. :)