Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • B bootstrap
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 263
    • Issues 263
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 114
    • Merge requests 114
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Bootstrap
  • bootstrap
  • Issues
  • #26525
Closed
Open
Issue created May 16, 2018 by Administrator@rootContributor

Unnecessary delay before fading-in new tab pane - tab.js

Created by: Djules

Using version 4.1.0, I found out a delay before new tab pane is shown with JS behavior and fade effect. This delay is the transition-duration value of the fade utility class.

Issue comes from the _activate method, line 144 in tab.js file.

There is a listener added to the previously activated tab pane for the transitionend event, but no classes are added to this element after that, so only the emulator can triggers the callback which activates the new one.

Have a look at the demo in the official doc.

Assignee
Assign to
Time tracking