Bug 17462

Summary: Misplaced search button on Newsgator online
Product: WebKit Reporter: Matt Lilek <dev+webkit>
Component: Layout and RenderingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: ahmad.saleem792, frances_c, webkit-bug-importer
Priority: P2 Keywords: InRadar, NeedsReduction
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Attachments:
Description Flags
Screenshot none

Matt Lilek
Reported 2008-02-20 16:58:38 PST
The search button on Newsgator's online RSS reader is improperly positioned in ToT (see attached screenshot). When the reader is loading, the page contents starts out and for a brief moment, the grey area at the bottom is higher up in the page. When the feed list is populated, it is pushed down, but the search button does not follow suit. Use the login information from bug 14808 comment 0 to login. You may need to reload the reader a few times in order for it to reproduce.
Attachments
Screenshot (81.50 KB, image/png)
2008-02-20 17:00 PST, Matt Lilek 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Matt Lilek
Comment 1 2008-02-20 17:00:27 PST
Created attachment 19243 [details] Screenshot Firefox 3 Beta (for reference) vs ToT
Matt Lilek
Comment 2 2008-02-20 17:01:18 PST
I also think this is a regression, but do not have an old enough version of Safari around at the moment to test that out (hence the P2 treatment).
Frances Cornwall
Comment 3 2024-04-17 21:22:05 PDT
The website in the test case: newsgator.com does not exist anymore, we can probably close the bug.
Radar WebKit Bug Importer
Comment 4 2024-04-18 17:13:09 PDT
<rdar://problem/126721415>
Ahmad Saleem
Comment 5 2024-04-19 04:49:52 PDT
I think we can find the website copy from Wayback Archive but from the reference picture, it seems that the user is logged in and have 'feed' configured. Wayback Link showing 'login' - https://web.archive.org/web/20081118102732/https://www.newsgator.com/ngs/si.aspx To try 'Newsgator Online' RSS Reader. Since it is difficult to reproduce and also if we might have similar bug, we might have already fixed it or might have reproducible test case. So it is not worth tracking this old bug.
Note You need to log in before you can comment on or make changes to this bug.