Greetings,
It actually comforts me to know the onclick issue is a firefox one.
Again, I was merely trying to give impressions based on my own
experiences. I have created a fresh Firefox profile,
used it to start Firefox, and was able to duplicate three of the issues
I have reported. The screen redrawing issue I reported can be duplicated
on three sites, including my own brandoncole.net. The visited/same page
link issue may be some quirky javascript thing, but I was able to
duplicate that on one site as well even after having deleted both cache
and browsing history. Lastly, the issue with having to manually turn on
browse mode after I clicked a button using the enter key also still
existed. I will say, though, that my original browse mode issue, the one
where browse mode wouldn't instantly activate when the browser was
started until I pressed something, appears to be gone in a fresh
profile. Sorry for all this trouble. Just trying to help make this the
WE it should be. Heheh.Aaron Smith wrote:
Thanks for the feedback, Brandon.
The onClick issues have been addressed as much as possible in
Window-Eyes. The outstanding issues are Mozilla issues, and have been
noted in the Mozilla BugZilla database.
I am not able to duplicate your redraw issue on a site with frames, so
it's time to start narrowing things down to figure out where the
problem lies. I would begin by running Firefox with a fresh, default
profile. You can do this by running Firefox from the command line with
a -p (that's dash p) parameter. This will bring up the profile dialog,
where you can create a new profile, and run Firefox with it. That will
cause Firefox to run as if it were first installed, with no add-ons or
customizations. We need to know if the problem continues using this
fresh profile.
If it does not, then there is some add-on or customization that is
causing the Window-Eyes to have problems. If the problem continues to
happen with the fresh profile, then we need to see if there are other
pages with frames that also demonstrate the problem, or if it is
specific to one page.
I'm also not able to duplicate your visited link problem, so it's time
to investigate that further as well. Remove your history, and delete
page cache to see if that makes a difference. Remove or disable
add-ons, or use the fresh profile, to see if that makes a difference.
The number of issues and features that have gone into Window-Eyes 7.0
is staggering, so it's important that you get as detailed and
possible, and do as much investigative work as possible on your end,
so that we can get your reported problems duplicated, and resolved
more quickly.
We had many Firefox 3 reports from both private and public beta
testers, and have resolved all of the ones that we tracked in our own
bug tracking database. So if you have outstanding issues, you need to
make sure they are reported, with as much detail as possible, to
[EMAIL PROTECTED] In addition, assure that you get an
acknowledgment that the problems have been duplicate, and marked down
for investigation. Otherwise, it can easily be overlooked as list
chatter, and we may miss a problem that you find important.
I hope that helps.
Aaron
Brandon Cole wrote:
I feel it is our duty to be totally honest here, and so I shall. I do
not think WE7.0 is ready for release at this point. Support for
Firefox 3, which is a much-advertised feature, is at best,
incomplete. The browse mode issues that I, and several others have
reported still exist in FF3, as do the Onclick issue and screen
refresh issues I have reported.
To clarify, Window-eyes now doesn't even report certain things that
really are onclicks as such. This causes problems on certain web
sites. Also, the previously mentioned screen redraw issue, where one
must continuously redraw the screen when browsing sites that use
frames. I have reasons for wishing to continue to use Firefox, and
while I understand the needs of one individual need not be meant if
it doesn't benefit the whole, I am not the only one who has
experienced some of these issues. I only repete all this because my
previous reports meant with no response. There is no indication these
issues are being addressed.
On another note, there is a brand new FF3 issue I have discovered.
Certain visited links are appearing as same page links, when in fact
they are not. This is probably the most minor of the issues I have
noticed, but it deserves to be reported. OI am also still having the
reading issue when composing a message in Thunderbird, but I admit
that may be a script problem rather than a Window-eyes one. I hope I
haven't ruffled too many feathers, but I felt my honest opinion
should be stated. Thanks.
If you reply to this message it will be delivered to the original
sender only. If your reply would benefit others on the list and
your message is related to GW Micro, then please consider sending
your message to [email protected] so the entire list will receive it.
All GW-Info messages are archived at http://www.gwmicro.com/gwinfo,
and can be searched through and sorted using the search
form at the bottom of the page.
If you wish to unsubscribe from this list, send a message to
[EMAIL PROTECTED] and include leave gw-info in the body of the
message.
If you reply to this message it will be delivered to the original
sender only. If your reply would benefit others on the list and
your message is related to GW Micro, then please consider sending
your message to [email protected] so the entire list will receive it.
All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be
searched through and sorted using the search
form at the bottom of the page.
If you wish to unsubscribe from this list, send a message to
[EMAIL PROTECTED] and include leave gw-info in the body
of the message.
