User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0) Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.4b) Gecko/20030507 The logout page of GMX contains a small area at the bottom where a newsticker scrolls up. When displaying this page and scrolling the whole page down the bug appears. The page can be scrolled further down than in IE. Instead of displaying the newsticker scrolling up the rest of the page is scrolled down until the bottom of the displayed page hits the window bottom then the page stops and the newsticker starts scrolling up. Reproducible: Always Steps to Reproduce: 1. Get a free GMX account at http://www.gmx.de 2. Log in then log out 3. scroll down the logout page as far as possible Actual Results: Instead of the newsticker area scrolling up the page around it is scrolled down until it hits the bottom of the window Expected Results: always scroll up the newsticker area The page can be scrolled further down intitially than in IE. Seems to be a bug with that. After the scrolling down has hit the bottom of the window it cannot be scrolled beyond the end of the page again.
Assignee: rogerl → asa
QA Contact: pschwartau → desale
Robert reports that the bug does not show up in this build: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 I have been able to log in to the site, and will attach a copy of the logout page below. It is generic and has no personal info. It uses the following JS file: http://stern.de/shortnews/ticker/gmx.js It document.writes() one of these scripts, depending on the browser: IE6 --> http://newsticker.shortnews.de/de/js/pro/2/engine_pro.js Moz --> http://newsticker.shortnews.de/de/js/pro/2/engine_dom.js The content for the scrolling ticker is at: http://www.stern.de/shortnews/content/gmx_def.js
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee: asa → other
Component: Browser-General → Layout
QA Contact: desale → ian
Here, gmx.de or gmx.net - after logging out - seem to reload the page infinitely, until firefox finally crashes.
You need to log in before you can comment on or make changes to this bug.