Em Mon, 2012-07-30 às 15:19 +0200, Andre Klapper escreveu:
> Currently accessibility (a11y) bug reports in random modules/products
> can only be found by querying for the "accessibility" keyword.
>
> Bugzilla does not allow "binding" an email address to a certain keyword
> to automaticall create b
On 08/10/2012 07:15 PM, Andre Klapper wrote:
> On Tue, 2012-07-31 at 12:28 +0200, Piñeiro wrote:
>> Sorry Andre, I misunderstood you when
>> we were talking about this at the GUADEC.
> I also misunderstood you (and maybe didn't make it clear). Sorry.
And following the list of sorries, sorry for my
On Tue, 2012-07-31 at 12:28 +0200, Piñeiro wrote:
> Sorry Andre, I misunderstood you when
> we were talking about this at the GUADEC.
I also misunderstood you (and maybe didn't make it clear). Sorry.
> I thought that you were
> proposing something like accessibility-banshee, accessibility-bla. In
(Cross-posting again to all lists, so no removing parts of the original
mail)
On 07/30/2012 05:06 PM, Bryen M Yunashko wrote:
> I think this is great, and will make it much easier for those of us who
> file bugs against accessibility. Having a component, rather than
> knowing to type in accessibi
Kyle wrote:
> Rather than making a11y out of sight out of mind for specific application
> developers, my thought is that an a11y component could, if handled
> correctly, bring it into focus. Ideally, the a11y component would
> automatically send the bug to the a11y team, who would in turn be able
On Mon, 2012-07-30 at 12:01 -0400, Kyle wrote:
> Rather than making a11y out of sight out of mind for specific
> application developers, my thought is that an a11y component could, if
> handled correctly, bring it into focus. Ideally, the a11y component
> would automatically send the bug to the a11
Rather than making a11y out of sight out of mind for specific application
developers, my thought is that an a11y component could, if handled correctly,
bring it into focus. Ideally, the a11y component would automatically send the
bug to the a11y team, who would in turn be able to make specific c
I think this is great, and will make it much easier for those of us who
file bugs against accessibility. Having a component, rather than
knowing to type in accessibility (or a11y?) in keyword will greatly
improve things in Bugzilla.
But I do worry about some accessibility bugs falling through the
Currently accessibility (a11y) bug reports in random modules/products
can only be found by querying for the "accessibility" keyword.
Bugzilla does not allow "binding" an email address to a certain keyword
to automaticall create bugmail whenever a specific keyword is added.
Having accessibility en
