Bug 14164 - Gmail has arrow ghosts stick around until repaint is forced
Summary: Gmail has arrow ghosts stick around until repaint is forced
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 523.x (Safari 3)
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Nobody
URL: https://mail.google.com/
Keywords: GoogleBug
Depends on:
Blocks:
 
Reported: 2007-06-15 07:17 PDT by Jeremy Baron
Modified: 2022-07-26 10:09 PDT (History)
6 users (show)

See Also:


Attachments
screenshot (9.54 KB, image/png)
2007-08-24 22:17 PDT, Jeremy Baron
no flags Details
Screenshot with full height of window (35.23 KB, image/png)
2007-08-26 07:03 PDT, David Kilzer (:ddkilzer)
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jeremy Baron 2007-06-15 07:17:11 PDT
Gmail has an arrow that points to the currently selected message that only shows up if you scroll through the message list with the keyboard using j and k (aiui that's how it's supposed to work)
If you scroll past the end of the content pane there is a ghost left behind when the content scrolls pointing to the message that was selected before the scroll.  (a lot better than the behavior I'm used to in earlier nightlies and shipping where any keyboard scrolling I did at all resulted in the page position reverting to the top.)
If I scroll so that the ghost is not visible and back again it is gone (with arrow keys on keyboard or mouse) so I assume that it's forcing a repaint.

ENV: intel Mac OS X 10.4.9 (8P2137) webkit svn r23527 (official nightly)
Comment 1 Jeremy Baron 2007-08-24 21:54:07 PDT
To clarify, this is at the list of conversations displayed when viewing search results, the content of a folder, all messages, starred messages, etc.  For example the screen you are redirected to when you visit gmail.com
Comment 2 David Kilzer (:ddkilzer) 2007-08-24 22:00:52 PDT
(In reply to comment #1)
> To clarify, this is at the list of conversations displayed when viewing search
> results, the content of a folder, all messages, starred messages, etc.  For
> example the screen you are redirected to when you visit gmail.com

Thanks for the bug report, Jeremy.  Could you post a screen shot of correct/incorrect behavior?  It might make it clearer.  Use Cmd-Shift-4 (use Space bar to toggle between outline and whole-window mode) or Cmd-Shift-3 for the whole screen.

Comment 3 Jeremy Baron 2007-08-24 22:17:30 PDT
Created attachment 16115 [details]
screenshot

This is the current behavior. (r25168)
There should never be more than one item in the list with an arrow pointing at it under any circumstances.
Comment 4 mitz 2007-08-25 01:46:43 PDT
I could not reproduce the bug. Maybe it has to do with the scroll amount, which in its turn has to do with the window height. Jeremy, can you post a screenshot that shows the entire window height (you can capture only the right or left edge of the window, which should not contain any personal info).
Comment 5 Jeremy Baron 2007-08-25 16:13:53 PDT
Now that I've created a second gmail account to repro this I see a gaping hole in my STR.
Your settings need to have keyboard shortcuts enabled (apparently default is disabled)

btw, mitzpettel just repro'd on tiger but cannot on leopard.
Comment 6 David Kilzer (:ddkilzer) 2007-08-26 07:03:04 PDT
Created attachment 16123 [details]
Screenshot with full height of window

At Mitz's request, here is a screenshot with the full height of the window.

After turning on keyboard shortcuts, hold down the "j" key to make the arrow go down the page.  As soon as gmail jumps to the next page, a "stuck" arrow will be drawn.
Comment 7 David Kilzer (:ddkilzer) 2007-08-26 22:37:53 PDT
Searching WebKit nightlies, r13675 was the first revision that would scroll the page correctly when the marker reached the last item on the page.  This revision also leaves a marker behind after scrolling, so I don't think this issue is a regression.
Comment 8 Ahmad Saleem 2022-07-26 05:00:58 PDT
Google website has changed drastically and there is no test case to reproduce this reliably today, do we need to have it open or we can close it as "RESOLVED INVALID" or "RESOLVED WORKSFORME"? Thanks!