Re: Implementing accessibility non-regression check tool

[Jan-Marek Glogowski <glogow@xxxxxxxxxx>]

Am 29.08.2018 um 09:33 schrieb Samuel Thibault:
> Jan-Marek Glogowski, le mer. 29 août 2018 06:53:52 +0000, a ecrit:
>> Am August 28, 2018 4:04:37 PM UTC schrieb Samuel Thibault <sthibault@xxxxxxxx>:
>>> Samuel Thibault, le lun. 12 févr. 2018 15:30:59 +0100, a ecrit:
>>>> - At some point we'll get confident that we won't introduce other
>>>> big classes of warnings over hundreds of .ui files. That's the point
>>>> where we can say "ok, let's start fixing the existing issues over
>>>> all .ui files once for good". We can then run through .ui files one
>>>> by one, fixing the issues and removing the corresponding suppression
>>>> lines. These could be used as "easy hacks" entries, they are usually
>>>> just a few lines to fix.
>>
>> I'm not sure we want this handled as "easy hacks". The goal was to enable the checks always for the build. Is this implemented and can I enable it?
> 
> The checks are already enabled, and any new issue will fail the
> build.  The goal now is to fix existing issues (currently suppressed by
> suppression rules).

Great. Guess I should have checked :-)
Thanks for the additional info.

Jan-Marek
_______________________________________________
LibreOffice mailing list
LibreOffice@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/libreoffice