Open Bug 358083 Opened 13 years ago Updated 4 years ago

Scrolling with scroll wheel set to "page at a time" does not take header into account

Categories

(Other Applications :: ChatZilla, defect)

defect
Not set

Tracking

(Not tracked)

People

(Reporter: bogofilter+mozilla, Assigned: rginda)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7

Scrolling with the scroll wheel set to "page at a time" does not take the space taken up by the channel header into account, causing some number of lines (depending on the header height) to be skipped on each scroll.  Works correctly when you use PgDn/PgUp on the keyboard.

Reproducible: Always
Not a lot we can do about this, as the mousewheel scrolling never goes near our code. I don't suppose we can capture something and do the scroll ourselves? (Does that mean we would need to check all those damn mousewheel prefs, too?)
Suggestion from someone who has no idea how ChatZilla is put together:  What about moving the top of the channel window down to make room for the header instead of overlapping the header over the channel?
OS: Windows XP → All
Hardware: PC → All
Version: unspecified → Trunk
The fact that the header overlaps has some benefits if it's see-through (more screen real-estate for chat, in a way - but I don't know of any better benefits. 

There are other downsides to it apart from the one mentioned in this bug, though (see bug 384694 for example). I think taking it out of the scrollable area will save us some headaches. Not sure exactly how we should do that, but I'm guessing it should be possible... just not sure how easy it is. I think we'd need an iframe, which gets us into "you're in another document" hell. A div wouldn't work (I think) because you can't force it to scroll somewhere, which we will need to do. Not sure if there's other solutions. Sigh.

James, what do you think about this?
Somewhere back before the vicinity of 0.9.34 the header info was all chrome, like in mailnews. Why was it changed? Why not change it back?
(In reply to comment #4)
> Somewhere back before the vicinity of 0.9.34 the header info was all chrome,
> like in mailnews. Why was it changed? Why not change it back?
> 

Probably to make it stylable. Confirming this, but leaning to "wontfix" here too, as fixing it is probably a lot of effort for a solution that breaks easily, etc.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Interestingly, it turns out Page Up/Down don't take the size of the header into account either - they just use 75% of the visible height to scroll by. We should share code between the these two things (if/when we fix this bug).
QA Contact: samuel → chatzilla
You need to log in before you can comment on or make changes to this bug.