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
  • #10851
Closed
Open
Issue created Sep 28, 2013 by Administrator@rootContributor

Data-api initialization doesn't work properly with async loading approach

Created by: sergeyzwezdin

If you are using data-api intialization with async loading (Require JS, for example), there is may be an issue with affix, carousel and scrollspy plugins. From time to time this plugins won't be initialized.

This is because window load event used, instead of document ready. Once the plugin loaded into browser, document might be loaded already in async scenario and initialization handler never fires. The suggestion is to replace"$(window).on(load)' with "$(document).ready()" if there is no other objections.

Assignee
Assign to
Time tracking