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
  • #12487
Closed
Open
Issue created Jan 31, 2014 by Administrator@rootContributor

ScrollSpy not acurate unless element has position: relative

Created by: kennethjevans

I just noticed that Scroll Spy miscalculates the offsets for its targets unless the element the scrollspy is on has its position set to relative.

This isn't a huge deal, but it isn't documented at all. Could we please get the documentation updated?

Thank you.

In case I'm crazy, I've setup a jsFiddle to demonstrate. I'm seeing this behavior in Windows 8 on FF 26, Chrome 32, and IE 10.

http://jsfiddle.net/ZAEXu/

Assignee
Assign to
Time tracking