Closed Bug 186698 Opened 22 years ago Closed 20 years ago

Cmd-DownArrow followed by Cmd-UpArrow fails

Categories

(Camino Graveyard :: General, defect)

Product:
Camino Graveyard
Component:
General
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 241142

People

(Reporter: sbwoodside, Assigned: sfraser_bugs)

References

(
URL
)

Details

(Keywords: qawanted)

Attachments

(1 file)

testcase.html
(deleted), text/html
Details
On the site http://www.balancingact-africa.com/news/back/balancing-act_105.html I load the page then hit Cmd-DownArrow, goes to the bottom of the page, and then I hit Cmd-UpArrow, which does nothing. It should go back to the top of the page. 2002122004 I've seen this on other pages. I've also experienced times when after doing a search, the Cmd-Arrow keys don't work.
odd, ->sfraser
Assignee: saari → sfraser
Testcase please.
Status: NEW → ASSIGNED
Keywords: qawanted
Me? I can still reproduce it...
Yes you! ;) Please try to reduce the URL to a testcase, by eliminating all HTML in the page that doesn't affect the problem. Then attach your reduced testcase. This process will probably allow you to discover the element on the page that causes the bug.
*** Bug 184314 has been marked as a duplicate of this bug. ***
another one (much simpler!!!!) http://www.umcs.maine.edu/~ftp/wisr/wisr8/papers/allen/allen.html
Attached file testcase.html (deleted) —
Comment on attachment 112024 [details] testcase.html You have to make your window short to see the problem occur. Then type Cmd-DownArrow and Cmd-UpArrow. the second Cmd-key will not work.
The testcase is based on http://www.umcs.maine.edu/~ftp/wisr/wisr8/papers/allen/allen.html ... on the original page you cannot even Cmd-DownArrow to start with, on the testcase you can Cmd-DownArrow but not Cmd-UpArrow. Seems to me an easier workaround would be to just remap Cmd-UpArrow and -DownArrow to Home and End respectively.
The bug also affects this page: http://www.umcs.maine.edu/~ftp/wisr/wisr8/papers/allen/allen.html I played around with the HTML file and found the element that seems to cause it. I got it down to this: <html> <head> test </head> <body> [snip a lot of text] <p> // this is the kicker </body> </html> The presence of an extra paragraph tag directly before the closing body tag causes it. Putting a </p> tag after the offending <p> doesn't help, and having only a closing </p> tag (strange HTML to say the least) will scroll normally. This behavior persists even if there are NO closing </body> or </html> tags at the bottom (bad HTML, but most things will render it)
Concerning the balancingact-africa page and cmd-up function: I just looked at the balancingact-africa.com link that has the problem with cmd-up, and got it to go away by deleting the <p></p> pair at the top of the code, except this time, BOTH a <p> AND a </p> tag were sufficient to cause the bug. Jim
cmd-downarrow isn't working at all in as of Camino 2003081810 let alone cmd-uparrow. Is this regression from the switch to the trunk after the 0.7 release?
WFM using 2004110408 (v0.8+) NB on 10.3.5. Sounds like this was fixed by Bug 241142 *** This bug has been marked as a duplicate of 241142 ***
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: