SitePoint Sponsor |
|
User Tag List
Results 1 to 7 of 7
Thread: firefox scroll lines
-
Mar 3, 2004, 10:09 #1
- Join Date
- Feb 2004
- Location
- Midsouth
- Posts
- 1,373
- Mentioned
- 0 Post(s)
- Tagged
- 0 Thread(s)
firefox scroll lines
is anyone else having a problem with firefox 0.8 leaving scroll lines on this site when you scroll up or down over like code boxes and things? its really strange, the slower you scroll it leaves more lines then if you scroll back down and up again faster it leaves fewer. i dont see it everywhere but its always happening on this site...
rynoguill
Ryan Guill, AKA Mark Roman
-
Mar 3, 2004, 22:00 #2
Which site? I've never seen it.
-
Mar 3, 2004, 22:06 #3
I just tried to duplicate it but couldn't. Apparently code boxes here can be buggy occasionally with Firefox though.
.
Zach Holman
good-tutorials — blog — twitter — last.fm
-
Mar 4, 2004, 08:26 #4
- Join Date
- Feb 2004
- Location
- Midsouth
- Posts
- 1,373
- Mentioned
- 0 Post(s)
- Tagged
- 0 Thread(s)
this site, and it doesnt do it every time... it seems like it happens more the longer i use it... im not sure even how to explain it. i may try to take a screen shot...
rynoguill
Ryan Guill, AKA Mark Roman
-
Mar 4, 2004, 08:56 #5
- Join Date
- Feb 2004
- Location
- Midsouth
- Posts
- 1,373
- Mentioned
- 0 Post(s)
- Tagged
- 0 Thread(s)
here is the before and after screen shots. the before is when i first load the page, or even after i have first scrolled down to the code box or quote box, and then the second is after i have scrolled down past it and came back up to it.
http://test.creopus.com/images/before.jpg
http://test.creopus.com/images/after.jpg
what do you guys think? the faster i scroll back up to it the further apart the lines are... is nobody else having this problem?rynoguill
Ryan Guill, AKA Mark Roman
-
Mar 9, 2004, 12:47 #6
- Join Date
- Feb 2004
- Location
- Midsouth
- Posts
- 1,373
- Mentioned
- 0 Post(s)
- Tagged
- 0 Thread(s)
Originally Posted by Rynoguill
rynoguill
Ryan Guill, AKA Mark Roman
-
Mar 9, 2004, 14:54 #7
Only thing I can think of is that it might be a memory issue... you using a lot of memory-intensive programs at the time?
.
Zach Holman
good-tutorials — blog — twitter — last.fm
Bookmarks