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
  • #24195
Closed
Open
Issue created Oct 01, 2017 by Administrator@rootContributor

Clarify ScrollSpy 'activate' event element [docs][v4][has-pr]

Created by: mikejacobson

In the docs for v4 ScrollSpy, it's not clear that the activate.bs.scrollspy event is now triggered on the scroll element rather than on the nav/tab element like it was in v3.

The event Description doesn't mention which element triggers the event, and the sample code for attaching a listener attaches it to element #myScrollSpy, which is not in any of the example markup so it's difficult to tell which element that is.

I think the event Description should specify which element triggers the event (especially since it's changed from v3) and the sample code for attaching a listener should use a relevant selector.

I'll submit a PR with these changes.

Assignee
Assign to
Time tracking