Bug 104351 - Accessible text-attributes-changed signals should not be emitted when starting new paragraph
Summary: Accessible text-attributes-changed signals should not be emitted when startin...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.2.3 release
Hardware: All Linux (All)
: low minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: accessibility
Depends on: 71556
Blocks: a11y-Linux
  Show dependency tree / graph
 
Reported: 2016-12-02 11:09 UTC by Aron Budea
Modified: 2025-01-20 03:09 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Aron Budea 2016-12-02 11:09:49 UTC 
This is a followup report for bug 71556 ("Accessible text-attributes-changed signals should only be emitted when the text attributes have changed [a11y]").
The majority of the issues is gone with Jacobo's fix, but there's still a small remaining issue:

"After the patch, most of the unwanted text-attributes-changed events are now gone. Still, the event shows up when you type the first letter of a new paragraph." [1]


The fix for the majority of bug 71556 for reference:
http://cgit.freedesktop.org/libreoffice/core/commit/?id=dddae1f0b950f1ce8ab4bcd24991f1917fa36aa6

"fdo#71556: Remove unwanted a11y event on text insertion"


[1] https://bugs.documentfoundation.org/show_bug.cgi?id=71556#c8
Comment 1 Xisco Faulí 2019-01-23 11:24:23 UTC 
Hi Noel/Michael,
Since you fix bug 117935, I thought you might be interested in this one as well...
Comment 2 QA Administrators 2023-01-20 03:24:40 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2025-01-20 03:09:23 UTC 
Dear Aron Budea,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug