https://bugs.documentfoundation.org/show_bug.cgi?id=149000
Heiko Tietze <heiko.tie...@documentfoundation.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needsUXEval |
Status|UNCONFIRMED |NEEDINFO
CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda
|.freedesktop.org |tion.org
Ever confirmed|0 |1
--- Comment #5 from Heiko Tietze <heiko.tie...@documentfoundation.org> ---
The topic was on the agenda of the design meeting.
The intended workflow is unclear. Why should you want to print issues rather
than fixing it? With external tools this might be different but running the
check again is cheap and simple.
One alternative is to have the issues in a dedicated sidebar tab along with
interactions to fix and tips why this is needed (MSO did a great job here).
And we could also insert annotations like comments into the document that could
be resolved when done. Since the list of issues might be long we would also
need a function to remove these annotation, in case the user decides to not
make the document fully accessible.
So the decision is WF/NAB unless the request is not to print the findings but,
for example, to export the inaccessible parts of the documents together with
the issue - and to fix it externally. But in this case it needs to be merged
back, which is a tricky task.
=> NEEDINFO
--
You are receiving this mail because:
You are on the CC list for the bug.
