Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Couple of bugs/complaints

0 views
Skip to first unread message

Eric O

unread,
Nov 26, 2009, 12:05:39 AM11/26/09
to
I sure do appreciate Firefox, especially how much faster it has been
since 3 and 3.5. But I have a bug or complaint to file. It has
continued for a long time so I don't know if anyone's working on it.

I don't know if this is exactly a Mozilla problem or an Adobe problem
-- possibly one of each. When Adobe Reader is running inside a
Firefox tab the following happens.

When you leave the tab (focus another tab or another window in
Windows.. this was true on Vista and is still true in Win7) and then
return to it, if you were viewing a PDF slideshow, you should expect
that upon returning focus to the tab displaying Adobe Reader your
scroller should work, your PageUp/Down keys and your arrow keys should
work if that is the mode you were in when you left the tab. Instead,
they are disabled, and you have to right-click inside the window and
re-select any mode at the top of the context menu to re-enable the
paging foward/back functions. This is rather annoying and costing me
a lot of time. What really makes the worst of it (and proves that
it's a bug, not intended behavior, IMO) is that when you right-click
for the context menu so you can select a mode (either "select" or
"hand" modes will work), you note that one of them is already selected
(in my case "select" mode). So for that reason alone, if nothing
else, you see that either select mode is ambiguous or it is being
incorrectly displayed as active. This leads to why I think this might
be a bug on the Mozilla side, because whether this erroneous behavior
happens or not depends on what I do in the other browser tabs while my
focus is away from the tab containing Adobe Reader. If I click inside
the other tabs and scroll around, that's what seems to be more likely
to disable scrolling/paging in the PDF tab when I return to it. If I
only view the other tabs and/or use their scrollbar, it is less likely
to cause the problem.

Thanks.

0 new messages