Esther wrote:
> For example, there is a
> "Votes" link and a "Vote for this bug" link. Are we supposed to be
> voting on whether to have these bugs raised in priority to be fixed?

Yeah, you can vote to express your enthusiasm for a bug getting fixed, but to be honest I doubt the odd vote here and there has that much influence on the formal prioritisation process, which is described here:

http://webkit.org/quality/bugpriorities.html

Of course, if the whole VoiceOver-using community here votes, that's a more noticeable effort and might be relevant to the following clause from that that process document:

> If a bug is getting a lot of public attention, the priority may be moved up.

Ultimately, though, the quick way to get things fixed is to submit actual code to WebKit (I know at least some of you can code), or, when the problem is fundamentally VoiceOver not WebKit, nag Apple.

The advantage of adding it to the WebKit tracker is people outside Apple could submit patches to it, the bug reports can be searched by the community to see if a problem has already been reported, and everyone is free to suggest fixes for the problem.

Esther also wrote:
> Also, thank you for submitting the original bug report to get VO-Shift-M
> fixed in WebKit.

You're very welcome.

--
Benjamin Hawkes-Lewis

Reply via email to