James Jolley wrote:
Take the www.teamxbox.com example I gave.
click any of the reviews and once the page opens, try and read it for a
while. I don't know what the problem at my end is, but the page keeps
exiting the HTML content and you always entd up back at the top after
reading for a while.
When raising issues, it's crucial to give the URL of a specific page
which isn't working for you, rather than the site as a whole, since
different pages can have very different underlying markup and code, even
if they seem superficially similar. I tried going to the following
review (this is in Safari 2):
http://reviews.teamxbox.com/xbox-360/1373/Stuntman-Ignition/p1/
and waited for the ping to indicate the page had finished loading. I was
able to navigate right through the entire page, including the review, in
a loop with ctrl option down. I was also able to pick the review
heading from the Item Chooser (ctrl option I), then ctrl option down
through the review itself.
Because I need Safari 2 for webpage testing at work and they can't be
safely run on the same machine, I'm afraid I can't test the same page in
Safari 3.
If you can provide reproducible steps at a particular URL in Safari 3,
you should report the problem. But it's crucial to be as specific as
possible if you want the developers to be able to isolate and fix the
problem (assuming it turns out to be a bug in VoiceOver or Safari,
rather than the webpage itself). See:
http://bugs.webkit.org/page.cgi?id=bug-writing.html
http://developer.mozilla.org/en/docs/Bug_writing_guidelines
http://www.gwmicro.com/blog/index.php/all/2007/08/15
for important guidance on explaining problems in a way that developers
can understand and act upon.
And here's a discussion about the proper place to file bug reports for
Safari 3:
http://webkit.org/blog/107/safari-beta-301-for-windows/
I'd tend to file web-related bugs with the WebKit engine project, since
there's a lot more transparency and bugs that crossover with VoiceOver
or Safari bugs specifically tend to be assigned a RADAR number anyhow.
For an example, I've just logged a bug about the Item Chooser menu not
including headings with WebKit Nightly:
http://bugs.webkit.org/show_bug.cgi?id=15132
Note that I explain how to reproduce my VoiceOver configuration.
This bug (if it is such) could also be affecting you with the WebKit
version used by Safari 3, but I don't know.
--
Benjamin Hawkes-Lewis
