Paul Gevers wrote:
>> Justin B Rye wrote:
>>> A bit repetitive, and we should probably say "modern", not "recent"
>>> (for a start because that hints at the downside: its assumptions are
>>> *too* modern for my video hardware).
>>>
>>>Following upstream, GNOME in buster defaults to using
Hi Justin,
On 30-06-2019 13:54, Justin B Rye wrote:
> Justin B Rye wrote:
>> A bit repetitive, and we should probably say "modern", not "recent"
>> (for a start because that hints at the downside: its assumptions are
>> *too* modern for my video hardware).
>>
>>Following upstream, GNOME
Hi Justin,
On 30-06-2019 13:53, Justin B Rye wrote:
>> Does this subject (a11y on Wayland) warrant a note in "Issues to be
>> aware of for buster" chapter?
>
> Probably the "apps-in-gnome-on-wayland" issues section should link
> back to this whats-new section.
That's a good solution. I'll do
Justin B Rye wrote:
> A bit repetitive, and we should probably say "modern", not "recent"
> (for a start because that hints at the downside: its assumptions are
> *too* modern for my video hardware).
>
>Following upstream, GNOME in buster defaults to using the Wayland
>display
Paul Gevers wrote:
> I thinks we should document the switch of GNOME to Wayland as the
> default display server in the What's New section. Proposal attached.
> I've added d-a11y@l.d.o in X-D-CC, please keep them in the loop, because
> I think it is worth mentioning a recommendation to not use
Package: release-notes
X-Debbugs-CC: debian-accessibil...@lists.debian.org
Control: tags -1 patch pending
Hi all,
I thinks we should document the switch of GNOME to Wayland as the
default display server in the What's New section. Proposal attached.
I've added d-a11y@l.d.o in X-D-CC, please keep
6 matches
Mail list logo
