Closed Bug 113974 Opened 23 years ago Closed 22 years ago

Nominum.com: web page scrolls as News text scrolls

Categories

(Tech Evangelism Graveyard :: English US, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: masri, Assigned: doronr)

References

()

Details

(Whiteboard: aok)

Platform: PowerBook G3/300/192Mb/48Gb, MacOS X 10.1.1
Fizzilla Build ID: 2001112005

Try the following.

1) Set your display to 1024x768, make the main browser window approx. 3/4 the
size of the screen. Perhaps a inch away from the bottom, and 2 inches away from
the right side.

2) Go here.

http://www.nominum.com/

3) Click the down arrow.

What happens: the page begins to scroll up as the "news" text scrolls up, until
it can't scroll any more at which point the vertical scrollbar disappears.

What should happen: the page should not scroll as the News text scrolls.

- Adam
OK, here's what I think is happening :

The page has a vertically-scrolling news ticker.  It works by scrolling a div
(which contains the text) slowly upwards.  Though it is mostly hidden, this div
is several hundred pixels high.  When at its lowest extreme (i.e. when you're
reading the top headline), the bottom of this div is well below the bottom of
the window, so you see a scrollbar.  As the div moves upwards, the "page" gets
shorter and shorter, so the scrollbar moves accordingly.

IMO, this is just a quirk of the way they've coded their ticker.  There's
probaby some cunning changes that can be made to their code which will make the
problem go away.
Hmm, so then you're thinking this might just be an evangelism problem?

- Adam
->tech evangelism
Assignee: asa → doronr
Component: Browser-General → US General
Product: Browser → Tech Evangelism
QA Contact: doronr → zach
Version: other → unspecified
Whiteboard: aok
no more scrolling News
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
v
Status: RESOLVED → VERIFIED
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.