That would be possible, but it's not clear that it would be an improvement to the user experience. Suppose the user is trying to scroll to some specific content, so they are looking at the scrollable content as they are dragging the scrollbar, and will stop dragging once they see what they're looking for. Suppose the content they're looking for is 40% of the way down the page. With the described change, it might be that we are showing the content at that position (40%) while the scroll position based on the scroll thumb is further down, say at 50%. If the user stops dragging at this time, the page will soon repaint to show the contenet at 50%, and the user will be confused because they were expecting to see the 40% content. With the current behaviour, a user in this situation would naturally just slow down their drag to a speed where painting can keep up, and can stop at the desired location.
Bug 1251617 Comment 20 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
That would be possible, but it's not clear that it would be an improvement to the user experience. Suppose the user is trying to scroll to some specific content, so they are looking at the scrollable content as they are dragging the scrollbar, and will stop dragging once they see what they're looking for. Suppose the content they're looking for is 40% of the way down the page. With the described change, it might be that we are showing the content at that position (40%) while the scroll position based on the scroll thumb is further down, say at 50%. If the user stops dragging at this time, the page will soon repaint to show the content at 50%, and the user will be confused because they were expecting to see the 40% content. With the current behaviour, a user in this situation would naturally just slow down their drag to a speed where painting can keep up, and can stop at the desired location.