{"push_id":549021208,"size":1,"distinct_size":1,"ref":"refs/heads/handle_multiple_zero_offset_scrollspy_elements","head":"22f9e30e990a3d09e3cc585c5ddd5a38729ef1a6","before":"ad933c6780a4cf9139fc9ea39d9aab0897895243","commits":[{"sha":"22f9e30e990a3d09e3cc585c5ddd5a38729ef1a6","author":{"email":"e7d4fedd39609342c9d775b51d0f7b99449312f5@herostrat.us","name":"Caden Lovelace"},"message":"Handle multiple zero-offset Scrollspy elements.\n\nWhen the first two elements in a scrollspy content block have a document\noffset of zero (i.e. they're hard against the top of the page),\nScrollspy would switch between them on every scroll event.\n\nThis could happen, for example, in a system of nested sections:\n\n```\n<section id=\"animals\">\n  <section id=\"dogs\">\n\tContent\n  </section>\n</section>\n```\n\nThis ocurred because Scrollspy's check to see if it's at the end of the\narray of sections uses `!arr[index]`. This misses the case where\n`arr[index]` does exist and is zero.\n\nThis commit explicitly checks the array bounds.","distinct":true,"url":"https://api.github.com/repos/neoeno/bootstrap/commits/22f9e30e990a3d09e3cc585c5ddd5a38729ef1a6"}]}