Closed Bug 131511 Opened 23 years ago Closed 23 years ago

Print Preview causes back button to stop working and keyboard shortcuts to fail

Categories

(Core :: Print Preview, defect)

x86
Windows 98
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 128489

People

(Reporter: sneswhiz, Assigned: rods)

References

()

Details

Steps to reproduce: 1. Go to any page 2. Go to http://cube.ign.com/ 3. Reload if interstital ad appears 4. Go to print preview 5. Close print preview At this point, the back button does not work. If I click the drop-down menu next to the back button, I see "GameCube" as the first entry, which should not occur since that is the page I am currently on. Clicking on that entry does nothing. If I then return to the page before that using the drop-down menu, it goes back and loads properly, but then crashes after 1-2 seconds. Also, after using the print preview on that site, keyboard shortcuts (such as Ctrl+R, Ctrl+L) do not work. Instead, the computer beeps.
Another problem: After finishing step 5, visit another page. Click Back. Neither the back nor forward buttons work. Clicking the drop-down menu next to Forward causes an empty box to show up next to the arrow for Back.
*** This bug has been marked as a duplicate of 128489 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Bug 128489 does not include Mozilla's crashing, though. I reproduced the crash consistently several times earlier tonight, reporting through Talkback each time. I then tried about 10 minutes ago, and Mozilla would no longer crash. 2 minutes ago, though, it did. I don't know how to get the Talkback numbers, though.
that's a fair point. it still looks like the same bug to me. could you go over to the other bug and add your notes about the crashing? to get the talkback incident id, you just need to run the talkback app, which on windows will be in the "components" folder (so probably C:\Program Files\mozilla.org\Mozilla\components\talkback.exe)
verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.