[Bug 88918] Edit→Hyperlink… is greyed out when an object with a hyperlink is selected in Draw

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=88918

Zachary Yona  changed:

   What|Removed |Added

   Assignee|magica...@duck.com  |libreoffice-b...@lists.free
   ||desktop.org
 Status|ASSIGNED|NEW

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160651] New: allow to change the order of conditional formattings

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160651

Bug ID: 160651
   Summary: allow to change the order of conditional formattings
   Product: LibreOffice
   Version: 24.2.2.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: cales...@scientia.org

Hey.

Conditional formattings have apparently an order in which they're evaluated.

This becomes obvious when e.g. multiple formattings change the styles of the
same range.
I actually use that behaviour quite often in more complex formattings.

The problem is, that from the dialogue at Format / Conditional / Manage, it's
not possible to change their order (and the dialogue doesn't even seem to show
their real order).

What I do then is to delete the right one of the "conflicting" conditional
formattings, and re-create it as a new one with exactly the same settings. And
voila, the behaviour on the spreadsheet changes.


Would be nice if the dialogue would:
- show their real order
- had up/down buttons to move the entries.


Thanks,
Chris.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160650] New: allow to set comments/descriptions for conditional formattings

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160650

Bug ID: 160650
   Summary: allow to set comments/descriptions for conditional
formattings
   Product: LibreOffice
   Version: 24.2.2.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: cales...@scientia.org

Hey.

Conditional formattings can get quite complex, and especially in the overview
dialogue (from Format / Conditional Manage), which shows only the range and the
first (but not further) conditions, it's often not easy to see what a certain
condition does.

It would be nice if one could add a comment/description to each entry and that
would be shown in that list.

Thanks,
Chris.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160649] Calc scrolling in the calc main window is disabled while the "Manage Conditional Fomatting" dialogue is open

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160649

Christoph Anton Mitterer  changed:

   What|Removed |Added

   Severity|normal  |minor

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160649] New: Calc scrolling in the calc main window is disabled while the "Manage Conditional Fomatting" dialogue is open

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160649

Bug ID: 160649
   Summary: Calc scrolling in the calc main window is disabled
while the "Manage Conditional Fomatting" dialogue is
open
   Product: LibreOffice
   Version: 24.2.2.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: cales...@scientia.org

Hi.

When going to the Format / Conditional / Manage dialogue, which lists the
existing conditional formattings (and for each the Range they affect as well as
the First Condition, it is not possible anymore - while the dialogue is open,
to scroll in the spreadsheet (e.g. via the scroll bars).

This would however quite often be handy, when one looks for a certain condition
and wants to see what's contained in the Range of an entry.

Interestingly, scrolling *does* work again, when from that dialogue, selecting
the Edit button.

Cheers,
Chris.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160648] New: after leaving the Edit-dialogue of an entry in the conditional formattings, the selection spuriously jumps to another one

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160648

Bug ID: 160648
   Summary: after leaving the Edit-dialogue of an entry in the
conditional formattings, the selection spuriously
jumps to another one
   Product: LibreOffice
   Version: 24.2.2.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: cales...@scientia.org

Hey.

When going to Format / Conditional / Manage dialogue, a window pops up with a
list of conditional formats.

Assuming that there are more entries the following happens on some (though not
all entries) quite often:

When selecting an entry, clicking the Edit Button and then leaving the
Edit-dialogue again, spuriously another entry in the list gets selected.

This is quite annoying and often led me to either delete a wrong entry or
subsequently edit a wrong one.


Cheers,
Chris.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 108441] [META] Database table bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=108441
Bug 108441 depends on bug 108057, which changed state.

Bug 108057 Summary: Primary key should default to AutoValue=Yes when type is 
integer
https://bugs.documentfoundation.org/show_bug.cgi?id=108057

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 108057] Primary key should default to AutoValue=Yes when type is integer

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=108057

Adolfo Jayme Barrientos  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 157403] UI: Navigator in Sidebar does not show new slide/page or objects after file reload (Impress/Draw)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=157403

--- Comment #8 from Commit Notification 
 ---
Jim Raykowski committed a patch related to this issue.
It has been pushed to "libreoffice-24-2":

https://git.libreoffice.org/core/commit/419fc9947bdcef8d5ef4e6305be62c07d0d0854a

Resolves tdf#157403 sidebar SdNavigator does not show new slide/page

It will be available in 24.2.4.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 157403] UI: Navigator in Sidebar does not show new slide/page or objects after file reload (Impress/Draw)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=157403

Commit Notification  changed:

   What|Removed |Added

 Whiteboard|target:24.8.0   |target:24.8.0 target:24.2.4

-- 
You are receiving this mail because:
You are the assignee for the bug.

core.git: Branch 'libreoffice-24-2' - sd/source

[Jim Raykowski (via logerrit)]

 sd/source/ui/dlg/navigatr.cxx |4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

New commits:
commit 419fc9947bdcef8d5ef4e6305be62c07d0d0854a
Author: Jim Raykowski 
AuthorDate: Wed Apr 3 11:27:21 2024 -0800
Commit: Adolfo Jayme Barrientos 
CommitDate: Sat Apr 13 06:17:26 2024 +0200

Resolves tdf#157403 sidebar SdNavigator does not show new slide/page

after file reload

Change-Id: I8ba7ffac3c098cf388a67e3454c5986b5a8b1f3f
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/165767
Tested-by: Jenkins
Reviewed-by: Jim Raykowski 
(cherry picked from commit 1dbe90cb078bddaf8bbd333823762744158c92bb)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/165934
Reviewed-by: Adolfo Jayme Barrientos 

diff --git a/sd/source/ui/dlg/navigatr.cxx b/sd/source/ui/dlg/navigatr.cxx
index f1a4a66c1e5f..8741a2c913b4 100644
--- a/sd/source/ui/dlg/navigatr.cxx
+++ b/sd/source/ui/dlg/navigatr.cxx
@@ -662,7 +662,7 @@ void SdNavigatorWin::RefreshDocumentLB( const OUString* 
pDocName )
 
 ::sd::DrawDocShell* pCurrentDocShell =
   dynamic_cast< ::sd::DrawDocShell *>( SfxObjectShell::Current() );
-SfxObjectShell* pSfxDocShell = SfxObjectShell::GetFirst([](const 
SfxObjectShell*){return true;}, false);
+SfxObjectShell* pSfxDocShell = SfxObjectShell::GetFirst();
 while( pSfxDocShell )
 {
 ::sd::DrawDocShell* pDocShell = dynamic_cast< ::sd::DrawDocShell 
*>( pSfxDocShell );
@@ -691,7 +691,7 @@ void SdNavigatorWin::RefreshDocumentLB( const OUString* 
pDocName )
 
 maDocList.push_back( aInfo );
 }
-pSfxDocShell = SfxObjectShell::GetNext( *pSfxDocShell, [](const 
SfxObjectShell*){return true;}, false );
+pSfxDocShell = SfxObjectShell::GetNext(*pSfxDocShell);
 }
 }
 mxLbDocs->set_active(nPos);

[Bug 98886] FILEOPEN: Incorrect symbols in formulas in .docx

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=98886

--- Comment #11 from Alexander  ---
Created attachment 193655
  --> https://bugs.documentfoundation.org/attachment.cgi?id=193655=edit
New screenshot

I make new screenshot. Relative to the initial state, the overlines appeared,
but the Gothic font did not.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160645] Shut Down

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160645

BogdanB  changed:

   What|Removed |Added

 CC||buzea.bog...@libreoffice.or
   ||g
   Hardware|ARM |All
 OS|macOS (All) |All

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160422] SLIDESHOW: Define Cursor per Slide, e.g. Arrow, Cross, Laser

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160422

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160424] Poor keyboard mnemonic ("access key") for field insertion in French

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160424

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160415] Combo box items from dialog editor are displayed at a wrong place

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160415

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160416] KF6/QT6 Interface hangs after importing an image

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160416

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 103314] [META] Templates bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=103314
Bug 103314 depends on bug 156338, which changed state.

Bug 156338 Summary: Templates. Imperfections dialog, rsp. confusing template 
manager behavior
https://bugs.documentfoundation.org/show_bug.cgi?id=156338

   What|Removed |Added

 Status|NEEDINFO|RESOLVED
 Resolution|--- |INSUFFICIENTDATA

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 156338] Templates. Imperfections dialog, rsp. confusing template manager behavior

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=156338

--- Comment #7 from QA Administrators  ---
Dear AB,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 156338] Templates. Imperfections dialog, rsp. confusing template manager behavior

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=156338

QA Administrators  changed:

   What|Removed |Added

 Resolution|--- |INSUFFICIENTDATA
 Status|NEEDINFO|RESOLVED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 156253] Unable to control placement of connecting line between text boxes

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=156253

QA Administrators  changed:

   What|Removed |Added

 Status|NEEDINFO|RESOLVED
 Resolution|--- |INSUFFICIENTDATA

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 156253] Unable to control placement of connecting line between text boxes

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=156253

--- Comment #7 from QA Administrators  ---
Dear kevinturner49,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 157775] Writer: lost calculations when a table is copied from one file to another

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=157775

--- Comment #3 from QA Administrators  ---
Dear accueil,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 157741] Show Comment: The show comment option displays the comment away from the source cell

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=157741

--- Comment #4 from QA Administrators  ---
Dear Hector,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 157774] Crash after installing the last version (7.6.2.1)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=157774

--- Comment #3 from QA Administrators  ---
Dear Marco Antonio,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 98886] FILEOPEN: Incorrect symbols in formulas in .docx

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=98886

--- Comment #10 from QA Administrators  ---
Dear Alexander,

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 97613] EDITING: CELL() function doesn't work as array inside arrays or in array functions like SUMPRODUCT()

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=97613

--- Comment #6 from QA Administrators  ---
Dear m.a.riosv,

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 96560] arrows change when exporting to doc in Writer

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=96560

--- Comment #8 from QA Administrators  ---
Dear yuval aviel,

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 95038] Chart: Add Arrow support to Line Charts

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=95038

--- Comment #12 from QA Administrators  ---
Dear Luke,

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 82760] Arrows from MSO shapes have wrong heads

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=82760

--- Comment #15 from QA Administrators  ---
Dear Ruslan Kabatsayev,

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 65940] FORMATTING: Arrow styles set to "none" are not saved

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=65940

--- Comment #12 from QA Administrators  ---
Dear aw-libreoffice,

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 80633] slow dialog layout / render ...

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=80633

--- Comment #15 from QA Administrators  ---
Dear Michael Meeks,

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 148529] FILEOPEN RTF Line shapes miss their line ending arrows

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=148529

--- Comment #4 from QA Administrators  ---
Dear Gabor Kelemen (allotropia),

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 144589] Down arrow icon has weird extra lines on right and top

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=144589

--- Comment #5 from QA Administrators  ---
Dear medmedin2014,

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 63814] Arrow-style can only be specified for right end of line for specific document

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=63814

--- Comment #10 from QA Administrators  ---
Dear Clemens Eisserer,

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 139634] Writer: Selection of words by double click and mouse move in comments

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=139634

--- Comment #6 from QA Administrators  ---
Dear Roland Kurmann,

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 139673] EDITING: Selection of words by double click and mouse move in Calc comments

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=139673

--- Comment #5 from QA Administrators  ---
Dear Roland Kurmann,

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 131669] No focus rectangle when hovering over arrow style and line width items in sidebar

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=131669

--- Comment #6 from QA Administrators  ---
Dear Telesto,

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 128950] With LO Base 6.2, it is no longer possible to change the Database connection type in "MySQL (Native)"

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=128950

--- Comment #24 from QA Administrators  ---
Dear Jean-Paul,

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 127995] Lines and line ends: Different arrow size left/right

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=127995

--- Comment #5 from QA Administrators  ---
Dear Florian,

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 126823] Draw/Impress: use defaults from the style for arrow head widths

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=126823

--- Comment #8 from QA Administrators  ---
Dear hardy,

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 126040] Loading arrow styles also changes the start and end style in the Line dialog

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=126040

--- Comment #4 from QA Administrators  ---
Dear Buovjaga,

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 126100] Arc with concave arrow has rendering error in certain configurations and arrow angles

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=126100

--- Comment #8 from QA Administrators  ---
Dear Buovjaga,

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 111728] Useless Arrow Style settings for shape objects

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=111728

--- Comment #9 from QA Administrators  ---
Dear Tamás Zolnai,

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 104130] SIDEBAR: Line and arrow style labels appearing in comboboxes of Line content panel

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=104130

--- Comment #17 from QA Administrators  ---
Dear Telesto,

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 107727] FILESAVE RTF: border-less text frame gets a border line

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=107727

--- Comment #16 from QA Administrators  ---
Dear Christian Nieber,

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

Hakim Ottey License Statement

[Hakim Ottey]

All of my past & future contributions to LibreOffice may be licensed under
the MPLv2/LGPLv3+ dual license.



-- 
Hakim Ottey
917-202-6061
Portfolio Website 
LinkedIn Profile 

core.git: sc/inc

[Andrea Gelmini (via logerrit)]

 sc/inc/pivot/PivotTableFormats.hxx |1 -
 1 file changed, 1 deletion(-)

New commits:
commit ce03b3f0879d1b8b564f00224b659ff59e77e932
Author: Andrea Gelmini 
AuthorDate: Sat Apr 13 00:58:16 2024 +0200
Commit: Taichi Haradaguchi <20001...@ymail.ne.jp>
CommitDate: Sat Apr 13 04:31:43 2024 +0200

Remove duplicated include

Change-Id: Ie70543c67549498d51eeb53d262b52f8ef1ec700
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/166043
Tested-by: Jenkins
Reviewed-by: Taichi Haradaguchi <20001...@ymail.ne.jp>

diff --git a/sc/inc/pivot/PivotTableFormats.hxx 
b/sc/inc/pivot/PivotTableFormats.hxx
index 3818b7f7c307..8c8ebcadffbd 100644
--- a/sc/inc/pivot/PivotTableFormats.hxx
+++ b/sc/inc/pivot/PivotTableFormats.hxx
@@ -13,7 +13,6 @@
 #include 
 #include 
 #include 
-#include 
 
 namespace sc
 {

core.git: sc/inc

[Andrea Gelmini (via logerrit)]

 sc/inc/pivot/PivotTableFormats.hxx |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit d76f1877f699c91f5e4a020641c6d65064bfb997
Author: Andrea Gelmini 
AuthorDate: Sat Apr 13 00:57:24 2024 +0200
Commit: Taichi Haradaguchi <20001...@ymail.ne.jp>
CommitDate: Sat Apr 13 04:31:25 2024 +0200

Fix typo

Change-Id: If0fbaae23b98d3bdd178473db8fdb8ab2263ef67
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/166042
Tested-by: Jenkins
Reviewed-by: Taichi Haradaguchi <20001...@ymail.ne.jp>

diff --git a/sc/inc/pivot/PivotTableFormats.hxx 
b/sc/inc/pivot/PivotTableFormats.hxx
index 3a4d12e16479..3818b7f7c307 100644
--- a/sc/inc/pivot/PivotTableFormats.hxx
+++ b/sc/inc/pivot/PivotTableFormats.hxx
@@ -33,7 +33,7 @@ struct Selection
 sal_uInt32 nDataIndex = 0;
 };
 
-/** Holds cell patter attributes and a selection information to which cells in 
the pivot table
+/** Holds cell pattern attributes and a selection information to which cells 
in the pivot table
  *  the pattern should be applied.
  */
 struct PivotTableFormat

core.git: sc/inc sc/qa sc/source

[Tomaž Vajngerl (via logerrit)]

 sc/inc/pivot/PivotTableFormats.hxx   |   14 ++-
 sc/qa/unit/PivotTableFormatsImportExport.cxx |   14 +++
 sc/source/filter/excel/xepivotxml.cxx|   65 +++
 sc/source/filter/excel/xestyle.cxx   |  115 ---
 sc/source/filter/inc/PivotTableFormat.hxx|5 -
 sc/source/filter/inc/xepivotxml.hxx  |1 
 sc/source/filter/inc/xestyle.hxx |8 +
 sc/source/filter/oox/PivotTableFormat.cxx|   15 ++-
 8 files changed, 184 insertions(+), 53 deletions(-)

New commits:
commit fc8dfe5c880ff4f64bf769df3088587d3358b027
Author: Tomaž Vajngerl 
AuthorDate: Fri Apr 12 22:55:47 2024 +0900
Commit: Tomaž Vajngerl 
CommitDate: Sat Apr 13 03:00:02 2024 +0200

pivot: Export Pivot Table "formats" element(s)

This change adds the "formats" element tree export for a pivot
table. The source are the formats (sc::PivotTableFormats) added to
the pivot table - in the ScDPSaveData class. This are currently set
on import but in the future hopefully those are also set through
the UI.

Change-Id: I5ed8f7e8d7ac248b0222a884fb97555ef6bb8427
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/166035
Tested-by: Jenkins
Reviewed-by: Tomaž Vajngerl 

diff --git a/sc/inc/pivot/PivotTableFormats.hxx 
b/sc/inc/pivot/PivotTableFormats.hxx
index 2665c088625c..3a4d12e16479 100644
--- a/sc/inc/pivot/PivotTableFormats.hxx
+++ b/sc/inc/pivot/PivotTableFormats.hxx
@@ -28,6 +28,7 @@ enum class FormatType
 /** Information to make a selection in the pivot table. */
 struct Selection
 {
+bool bSelected = false;
 sal_Int32 nField = 0;
 sal_uInt32 nDataIndex = 0;
 };
@@ -38,8 +39,17 @@ struct Selection
 struct PivotTableFormat
 {
 FormatType eType = FormatType::None;
+
+bool bDataOnly = true;
+bool bLabelOnly = false;
+bool bSelected = false;
+bool bOutline = false;
+std::optional oFieldPosition = std::nullopt;
+
 std::vector aSelections;
 std::shared_ptr pPattern;
+
+std::vector const& getSelections() const { return aSelections; }
 };
 
 /** A holder for a collection of PivotTableFormat */
@@ -50,9 +60,9 @@ class PivotTableFormats
 public:
 void add(PivotTableFormat const& rPivotTableFormat) { 
maFormats.push_back(rPivotTableFormat); }
 
-size_t size() { return maFormats.size(); }
+size_t size() const { return maFormats.size(); }
 
-std::vector const& getVector() { return maFormats; }
+std::vector const& getVector() const { return maFormats; 
}
 };
 }
 
diff --git a/sc/qa/unit/PivotTableFormatsImportExport.cxx 
b/sc/qa/unit/PivotTableFormatsImportExport.cxx
index 3cffe8cbc510..401e190b34f5 100644
--- a/sc/qa/unit/PivotTableFormatsImportExport.cxx
+++ b/sc/qa/unit/PivotTableFormatsImportExport.cxx
@@ -73,6 +73,8 @@ CPPUNIT_TEST_FIXTURE(ScPivotTableFormatsImportExport,
 
 
createScDoc("xlsx/pivot-table/PivotTableCellFormatsTest_1_DataFieldInRow_RowLabelColor.xlsx");
 assertDocument(*getScDoc());
+saveAndReload("Calc Office Open XML");
+assertDocument(*getScDoc());
 }
 
 CPPUNIT_TEST_FIXTURE(ScPivotTableFormatsImportExport,
@@ -85,6 +87,8 @@ CPPUNIT_TEST_FIXTURE(ScPivotTableFormatsImportExport,
 createScDoc(
 
"xlsx/pivot-table/PivotTableCellFormatsTest_2_DataFieldInRow_ColumnLabelColor.xlsx");
 assertDocument(*getScDoc());
+saveAndReload("Calc Office Open XML");
+assertDocument(*getScDoc());
 }
 
 CPPUNIT_TEST_FIXTURE(ScPivotTableFormatsImportExport,
@@ -98,6 +102,8 @@ CPPUNIT_TEST_FIXTURE(ScPivotTableFormatsImportExport,
 createScDoc(
 
"xlsx/pivot-table/PivotTableCellFormatsTest_3_DataFieldInColumn_ColumnLabelColor.xlsx");
 assertDocument(*getScDoc());
+saveAndReload("Calc Office Open XML");
+assertDocument(*getScDoc());
 }
 
 CPPUNIT_TEST_FIXTURE(ScPivotTableFormatsImportExport,
@@ -110,6 +116,8 @@ CPPUNIT_TEST_FIXTURE(ScPivotTableFormatsImportExport,
 
 
createScDoc("xlsx/pivot-table/PivotTableCellFormatsTest_4_DataFieldInColumn_DataColor.xlsx");
 assertDocument(*getScDoc());
+saveAndReload("Calc Office Open XML");
+assertDocument(*getScDoc());
 }
 
 CPPUNIT_TEST_FIXTURE(ScPivotTableFormatsImportExport,
@@ -124,6 +132,8 @@ CPPUNIT_TEST_FIXTURE(ScPivotTableFormatsImportExport,
 createScDoc("xlsx/pivot-table//"
 
"PivotTableCellFormatsTest_5_DataFieldInColumnAndTwoRowFields_DataColor.xlsx");
 assertDocument(*getScDoc());
+saveAndReload("Calc Office Open XML");
+assertDocument(*getScDoc());
 }
 
 CPPUNIT_TEST_FIXTURE(ScPivotTableFormatsImportExport,
@@ -137,6 +147,8 @@ CPPUNIT_TEST_FIXTURE(ScPivotTableFormatsImportExport,
 createScDoc(
 
"xlsx/pivot-table//PivotTableCellFormatsTest_6_SingleDataFieldInColumn_DataColor.xlsx");
 assertDocument(*getScDoc());
+saveAndReload("Calc Office Open XML");
+assertDocument(*getScDoc());
 }
 
 CPPUNIT_TEST_FIXTURE(ScPivotTableFormatsImportExport,
@@ -154,6 +166,8 @@ 

[Bug 160645] Shut Down

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160645

Armondo Lopez  changed:

   What|Removed |Added

 CC||armlo...@csumb.edu
 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

--- Comment #1 from Armondo Lopez  ---
Thank you for submitting the bug. I can confirm that it is present in

Version: 24.2.1.2 (X86_64) / LibreOffice Community
Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

as well as 

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: a2265e8faa099d9652efd12392c2877c2df1d1eb
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160566] formula object crops subscript

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160566

Armondo Lopez  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1
 CC||armlo...@csumb.edu

--- Comment #5 from Armondo Lopez  ---
Thank you for reporting the bug. 

Please attach a sample document, as this makes it easier for us to verify the
bug. I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' once the requested information is provided. 

(Note that the attachment will be public, remove any sensitive information
before attaching it.)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160617] Bulleted lists have different indentations

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160617

Armondo Lopez  changed:

   What|Removed |Added

 CC||armlo...@csumb.edu

--- Comment #5 from Armondo Lopez  ---
I am able to reproduce this behavior in

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: a2265e8faa099d9652efd12392c2877c2df1d1eb
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

as well as

Version: 24.2.1.2 (X86_64) / LibreOffice Community
Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

core.git: vcl/source

[Mike Kaganski (via logerrit)]

 vcl/source/gdi/CommonSalLayout.cxx |6 +++---
 vcl/source/outdev/text.cxx |2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)

New commits:
commit 01cabd3f998197f277300bcc71fc80e80642caed
Author: Mike Kaganski 
AuthorDate: Fri Apr 12 09:56:29 2024 +0100
Commit: Mike Kaganski 
CommitDate: Sat Apr 13 01:20:18 2024 +0200

Don't use lround when assigning to a double

Change-Id: Ifdfd351cf1f2848b754ec7a4c6f6cb9a56f478d5
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/165939
Tested-by: Jenkins
Reviewed-by: Mike Kaganski 

diff --git a/vcl/source/gdi/CommonSalLayout.cxx 
b/vcl/source/gdi/CommonSalLayout.cxx
index fc3a2a2bf79c..8211b9ea6aa9 100644
--- a/vcl/source/gdi/CommonSalLayout.cxx
+++ b/vcl/source/gdi/CommonSalLayout.cxx
@@ -555,9 +555,9 @@ bool 
GenericSalLayout::LayoutText(vcl::text::ImplLayoutArgs& rArgs, const SalLay
 nYOffset = nYOffset * nYScale;
 if (!GetSubpixelPositioning())
 {
-nAdvance = std::lround(nAdvance);
-nXOffset = std::lround(nXOffset);
-nYOffset = std::lround(nYOffset);
+nAdvance = std::round(nAdvance);
+nXOffset = std::round(nXOffset);
+nYOffset = std::round(nYOffset);
 }
 
 basegfx::B2DPoint aNewPos(aCurrPos.getX() + nXOffset, 
aCurrPos.getY() + nYOffset);
diff --git a/vcl/source/outdev/text.cxx b/vcl/source/outdev/text.cxx
index 80fb2b94bd40..ed782acf2ffb 100644
--- a/vcl/source/outdev/text.cxx
+++ b/vcl/source/outdev/text.cxx
@@ -1121,7 +1121,7 @@ std::unique_ptr OutputDevice::ImplLayout(const 
OUString& rOrigStr,
 {
 for(int i = 0; i < nLen; ++i)
 xDXPixelArray[i] = pDXArray.get(i);
-nEndGlyphCoord = std::lround(xDXPixelArray[nLen - 1]);
+nEndGlyphCoord = std::round(xDXPixelArray[nLen - 1]);
 }
 
 aLayoutArgs.SetDXArray(xDXPixelArray.get());

[Bug 160647] LO Writer 7.6.5.2 (and most anterior versions) cannot be used on wide screen monitors due to extreme performance issues

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160647

--- Comment #2 from lp.allar...@gmail.com ---
Forgot to mention that I tried playing with misc settings (and each time
restarting the program) to see if somehow things would become better. 
Unfortunately nothing made this issue improve or go away...

Settings I tried changing:
-Hardware acceleration
-Antialiasing
-Font antialiasing
-Themes
-OpenCL

I also ran the graphics tests (see attached ZIP file of the results):
-Graphics Backend used: svp
-Passed Tests: 67
-Quirky Tests: 35
-Failed Tests: 1
-Skipped Tests: 6

-- 
You are receiving this mail because:
You are the assignee for the bug.

core.git: solenv/vs

[Mike Kaganski (via logerrit)]

 solenv/vs/LibreOffice.natstepfilter |   12 +++-
 1 file changed, 11 insertions(+), 1 deletion(-)

New commits:
commit 4108a59dec851cae19012f790776c7d65b8ceef3
Author: Mike Kaganski 
AuthorDate: Fri Apr 12 09:37:11 2024 +0500
Commit: Mike Kaganski 
CommitDate: Sat Apr 13 01:19:45 2024 +0200

Add VclPtr operators to natstepfilter

And fix a vector-related filter

Change-Id: Icd3f5bd5a04a1385dff3f3413792a7aad544a506
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/166029
Tested-by: Jenkins
Reviewed-by: Mike Kaganski 

diff --git a/solenv/vs/LibreOffice.natstepfilter 
b/solenv/vs/LibreOffice.natstepfilter
index 6098ef9fb980..afd3428ace1f 100644
--- a/solenv/vs/LibreOffice.natstepfilter
+++ b/solenv/vs/LibreOffice.natstepfilter
@@ -9,7 +9,7 @@
 NoStepInto
 
 
->std::vector.*::operator[]
+std::vector.*::operator[]
 NoStepInto
 
 
@@ -24,4 +24,14 @@
 rtl::Reference.*::operator-
 NoStepInto
 
+
+VclPtr.*::operator-
+NoStepInto
+
+
+
+
+VclPtr.*::operator .* \*
+NoStepInto
+
 

core.git: oox/source sc/qa

[Mike Kaganski (via logerrit)]

 oox/source/drawingml/drawingmltypes.cxx |   12 +---
 oox/source/export/drawingml.cxx |   18 +-
 sc/qa/unit/subsequent_export_test3.cxx  |8 
 3 files changed, 22 insertions(+), 16 deletions(-)

New commits:
commit 6e3ed71f906c3571a6b6efb5335c26807b566a42
Author: Mike Kaganski 
AuthorDate: Fri Apr 12 09:16:12 2024 +0100
Commit: Mike Kaganski 
CommitDate: Sat Apr 13 01:19:00 2024 +0200

Use o3tl::convert in oox

Change-Id: I1cbc299e7e64eae48f0f6c896a8160bbe6e19c97
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/165938
Tested-by: Jenkins
Reviewed-by: Mike Kaganski 

diff --git a/oox/source/drawingml/drawingmltypes.cxx 
b/oox/source/drawingml/drawingmltypes.cxx
index 30fed83f4391..04668c6b9a72 100644
--- a/oox/source/drawingml/drawingmltypes.cxx
+++ b/oox/source/drawingml/drawingmltypes.cxx
@@ -92,22 +92,20 @@ float GetTextSize( std::u16string_view sValue )
 return fRet;
 }
 
-/** converts the ST_TextSpacingPoint to 1/100mm */
+/** converts the ST_TextSpacingPoint (1/100pt) to 1/100mm */
 sal_Int32 GetTextSpacingPoint( std::u16string_view sValue )
 {
 sal_Int32 nRet;
-if( ::sax::Converter::convertNumber( nRet, sValue, (SAL_MIN_INT32 + 360) / 
254, (SAL_MAX_INT32 - 360) / 254 ) )
+if( ::sax::Converter::convertNumber( nRet, sValue ) )
 nRet = GetTextSpacingPoint( nRet );
 return nRet;
 }
 
 sal_Int32 GetTextSpacingPoint(sal_Int32 nValue)
 {
-if (nValue > 0)
-nValue = (nValue * 254 + 360);
-else if (nValue < 0)
-nValue = (nValue * 254 - 360);
-return nValue / 720;
+constexpr auto mdFromPt = o3tl::getConversionMulDiv(o3tl::Length::pt, 
o3tl::Length::mm100);
+constexpr o3tl::detail::m_and_d md(mdFromPt.first, mdFromPt.second * 100);
+return o3tl::convertNarrowing(nValue);
 }
 
 float GetFontHeight( sal_Int32 nHeight )
diff --git a/oox/source/export/drawingml.cxx b/oox/source/export/drawingml.cxx
index 92aa84438e62..d14fd037f237 100644
--- a/oox/source/export/drawingml.cxx
+++ b/oox/source/export/drawingml.cxx
@@ -167,6 +167,14 @@ const char* g_aPredefinedClrNames[] = {
 "hlink",
 "folHlink",
 };
+
+/** converts 1/100mm to the ST_TextSpacingPoint (1/100pt) */
+sal_Int64 toTextSpacingPoint(sal_Int64 mm100)
+{
+constexpr auto mdToPt = o3tl::getConversionMulDiv(o3tl::Length::mm100, 
o3tl::Length::pt);
+constexpr o3tl::detail::m_and_d md(mdToPt.first * 100, mdToPt.second);
+return o3tl::convert(mm100, md.m, md.d);
+}
 }
 
 namespace oox::drawingml {
@@ -2491,7 +2499,7 @@ void DrawingML::WriteRunProperties( const Reference< 
XPropertySet >& rRun, bool
 *therefore to get original value CharKerning need to be convert.
 *
https://opengrok.libreoffice.org/xref/core/oox/source/drawingml/drawingmltypes.cxx#95
 **/
-nCharKerning = ((nCharKerning * 720)-360) / 254;
+nCharKerning = toTextSpacingPoint(nCharKerning);
 
 if ((bComplex && GetProperty(rXPropSet, "CharWeightComplex"))
 || GetProperty(rXPropSet, "CharWeight"))
@@ -3445,7 +3453,7 @@ void DrawingML::WriteLinespacing(const LineSpacing& 
rSpacing, float fFirstCharHe
XML_val, 
OString::number(static_cast(rSpacing.Height)*1000));
 }
 else if (rSpacing.Mode == LineSpacingMode::MINIMUM
- && fFirstCharHeight > static_cast(rSpacing.Height) * 0.001 
* 72.0 / 2.54)
+ && fFirstCharHeight > o3tl::convert(rSpacing.Height, 
o3tl::Length::mm100, o3tl::Length::pt))
 {
 // 100% proportional line spacing = single line spacing
 mpFS->singleElementNS(XML_a, XML_spcPct, XML_val,
@@ -3454,7 +3462,7 @@ void DrawingML::WriteLinespacing(const LineSpacing& 
rSpacing, float fFirstCharHe
 else
 {
 mpFS->singleElementNS( XML_a, XML_spcPts,
-   XML_val, 
OString::number(std::lround(rSpacing.Height / 25.4 * 72)));
+   XML_val, 
OString::number(toTextSpacingPoint(rSpacing.Height)));
 }
 }
 
@@ -3582,7 +3590,7 @@ bool DrawingML::WriteParagraphProperties(const 
Reference& rParagra
 mpFS->startElementNS(XML_a, XML_spcBef);
 {
 mpFS->singleElementNS( XML_a, XML_spcPts,
-   XML_val, 
OString::number(std::lround(nParaTopMargin / 25.4 * 72)));
+   XML_val, 
OString::number(toTextSpacingPoint(nParaTopMargin)));
 }
 mpFS->endElementNS( XML_a, XML_spcBef );
 }
@@ -3592,7 +3600,7 @@ bool DrawingML::WriteParagraphProperties(const 
Reference& rParagra
 mpFS->startElementNS(XML_a, XML_spcAft);
 {
 mpFS->singleElementNS( XML_a, XML_spcPts,
-   XML_val, 
OString::number(std::lround(nParaBottomMargin / 25.4 * 72)));
+   XML_val, 
OString::number(toTextSpacingPoint(nParaBottomMargin)));
 }
 mpFS->endElementNS( XML_a, XML_spcAft );
 }
diff 

[Bug 160647] LO Writer 7.6.5.2 (and most anterior versions) cannot be used on wide screen monitors due to extreme performance issues

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160647

--- Comment #1 from lp.allar...@gmail.com ---
Created attachment 193654
  --> https://bugs.documentfoundation.org/attachment.cgi?id=193654=edit
Graphics test results

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160647] New: LO Writer 7.6.5.2 (and most anterior versions) cannot be used on wide screen monitors due to extreme performance issues

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160647

Bug ID: 160647
   Summary: LO Writer 7.6.5.2 (and most anterior versions) cannot
be used on wide screen monitors due to extreme
performance issues
   Product: LibreOffice
   Version: 7.6.5.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: lp.allar...@gmail.com

Description:
LO Writer 7.6.5.2 (and most anterior versions) cannot be used on wide screen
monitors due to extreme visual performance issues.  Scrolling a simple 10 pages
document (created in LO and not a MS word document imported in LO) is nearly
impossible without experiencing extreme stutter and choppy scrolling and even
the program interface (such as resizing the navigator or Styles browser) is not
smooth.  CPU is maxed out due to extremely poor performance. 

Reducing the program window to a smaller size immediately lakes the performance
issue go away.

The issue is so severe that I abandoned Writer completely due to this poor
performance.  I also noticed with each LO update thing are getting worst.

I am thinking this issue is somehow related to the other issue I experienced
with Calc which has extreme stutter when typing
(https://bugs.documentfoundation.org/show_bug.cgi?id=152657)

Actual Results:
See problem description

Expected Results:
See problem description


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.6.5.2 (X86_64) / LibreOffice Community
Build ID: 38d5f62f85355c192ef5f1dd47c5c0c0c6d6598b
CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: en-CA (en_CA.UTF-8); UI: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

core.git: sc/source

[Caolán McNamara (via logerrit)]

 sc/source/core/tool/interpr4.cxx | 1036 +++
 1 file changed, 520 insertions(+), 516 deletions(-)

New commits:
commit d490efe410a54f1860578728027d1ec0439f0ba9
Author: Caolán McNamara 
AuthorDate: Fri Apr 12 17:37:30 2024 +0100
Commit: Caolán McNamara 
CommitDate: Sat Apr 13 00:52:40 2024 +0200

Related: tdf#160056 call FormulaCompiler::IsOpCodeJumpCommand just once

rearrange to reuse previous calculation

Change-Id: Ibda0388e020dac995e5667af09767b0314720935
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/166039
Tested-by: Jenkins
Reviewed-by: Caolán McNamara 

diff --git a/sc/source/core/tool/interpr4.cxx b/sc/source/core/tool/interpr4.cxx
index dc0bd397707f..4408b04aa695 100644
--- a/sc/source/core/tool/interpr4.cxx
+++ b/sc/source/core/tool/interpr4.cxx
@@ -4030,540 +4030,544 @@ StackVar ScInterpreter::Interpret()
 PushWithoutError( *pCur );
 nCurFmtType = SvNumFormatType::UNDEFINED;
 }
-else if (!FormulaCompiler::IsOpCodeJumpCommand( eOp ) &&
-((aTokenMatrixMapIter = maTokenMatrixMap.find( pCur)) !=
- maTokenMatrixMap.end()) &&
-(*aTokenMatrixMapIter).second->GetType() != svJumpMatrix)
-{
-// Path already calculated, reuse result.
-const sal_uInt8 nParamCount = pCur->GetParamCount();
-if (sp >= nParamCount)
-nStackBase = sp - nParamCount;
-else
-{
-SAL_WARN("sc.core", "Stack anomaly with calculated path at "
-<< aPos.Tab() << "," << aPos.Col() << "," << aPos.Row()
-<< "  " << aPos.Format(
-ScRefFlags::VALID | ScRefFlags::FORCE_DOC | 
ScRefFlags::TAB_3D, )
-<< "  eOp: " << static_cast(eOp)
-<< "  params: " << static_cast(nParamCount)
-<< "  nStackBase: " << nStackBase << "  sp: " << sp);
-nStackBase = sp;
-assert(!"underflow");
-}
-sp = nStackBase;
-PushTokenRef( (*aTokenMatrixMapIter).second);
-}
 else
 {
-// previous expression determines the current number format
-nCurFmtType = nRetTypeExpr;
-nCurFmtIndex = nRetIndexExpr;
-// default function's format, others are set if needed
-nFuncFmtType = SvNumFormatType::NUMBER;
-nFuncFmtIndex = 0;
-
-if (FormulaCompiler::IsOpCodeJumpCommand( eOp ))
-nStackBase = sp;// don't mess around with the jumps
-else
+const bool bIsOpCodeJumpCommand = 
FormulaCompiler::IsOpCodeJumpCommand(eOp);
+if (!bIsOpCodeJumpCommand &&
+   ((aTokenMatrixMapIter = maTokenMatrixMap.find( pCur)) !=
+maTokenMatrixMap.end()) &&
+   (*aTokenMatrixMapIter).second->GetType() != svJumpMatrix)
 {
-// Convert parameters to matrix if in array/matrix formula and
-// parameters of function indicate doing so. Create JumpMatrix
-// if necessary.
-if ( MatrixParameterConversion() )
+// Path already calculated, reuse result.
+const sal_uInt8 nParamCount = pCur->GetParamCount();
+if (sp >= nParamCount)
+nStackBase = sp - nParamCount;
+else
 {
-eOp = ocNone;   // JumpMatrix created
+SAL_WARN("sc.core", "Stack anomaly with calculated path at 
"
+<< aPos.Tab() << "," << aPos.Col() << "," << 
aPos.Row()
+<< "  " << aPos.Format(
+ScRefFlags::VALID | ScRefFlags::FORCE_DOC | 
ScRefFlags::TAB_3D, )
+<< "  eOp: " << static_cast(eOp)
+<< "  params: " << static_cast(nParamCount)
+<< "  nStackBase: " << nStackBase << "  sp: " << 
sp);
 nStackBase = sp;
+assert(!"underflow");
 }
+sp = nStackBase;
+PushTokenRef( (*aTokenMatrixMapIter).second);
+}
+else
+{
+// previous expression determines the current number format
+nCurFmtType = nRetTypeExpr;
+nCurFmtIndex = nRetIndexExpr;
+// default function's format, others are set if needed
+nFuncFmtType = SvNumFormatType::NUMBER;
+nFuncFmtIndex = 0;
+
+if (bIsOpCodeJumpCommand)
+nStackBase = sp;// don't mess around with the jumps
 else
 {
-const sal_uInt8 nParamCount = pCur->GetParamCount();
- 

core.git: sc/source

[Caolán McNamara (via logerrit)]

 sc/source/core/tool/interpr4.cxx |   31 ++-
 1 file changed, 18 insertions(+), 13 deletions(-)

New commits:
commit 030b655963c182693c7b657dc6aa4d2fe85c17c6
Author: Caolán McNamara 
AuthorDate: Fri Apr 12 12:24:06 2024 +0100
Commit: Caolán McNamara 
CommitDate: Sat Apr 13 00:51:29 2024 +0200

Related: tdf#160056 don't call GetParamCount twice

GetParamCount: 290ms -> 175ms
Change-Id: Ic3a26b1e8035744dcab2da69a8ebd3b29dd2160a
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/166031
Tested-by: Jenkins
Reviewed-by: Caolán McNamara 

diff --git a/sc/source/core/tool/interpr4.cxx b/sc/source/core/tool/interpr4.cxx
index 5e5d513289d0..dc0bd397707f 100644
--- a/sc/source/core/tool/interpr4.cxx
+++ b/sc/source/core/tool/interpr4.cxx
@@ -4036,8 +4036,9 @@ StackVar ScInterpreter::Interpret()
 (*aTokenMatrixMapIter).second->GetType() != svJumpMatrix)
 {
 // Path already calculated, reuse result.
-if (sp >= pCur->GetParamCount())
-nStackBase = sp - pCur->GetParamCount();
+const sal_uInt8 nParamCount = pCur->GetParamCount();
+if (sp >= nParamCount)
+nStackBase = sp - nParamCount;
 else
 {
 SAL_WARN("sc.core", "Stack anomaly with calculated path at "
@@ -4045,7 +4046,7 @@ StackVar ScInterpreter::Interpret()
 << "  " << aPos.Format(
 ScRefFlags::VALID | ScRefFlags::FORCE_DOC | 
ScRefFlags::TAB_3D, )
 << "  eOp: " << static_cast(eOp)
-<< "  params: " << 
static_cast(pCur->GetParamCount())
+<< "  params: " << static_cast(nParamCount)
 << "  nStackBase: " << nStackBase << "  sp: " << sp);
 nStackBase = sp;
 assert(!"underflow");
@@ -4074,18 +4075,22 @@ StackVar ScInterpreter::Interpret()
 eOp = ocNone;   // JumpMatrix created
 nStackBase = sp;
 }
-else if (sp >= pCur->GetParamCount())
-nStackBase = sp - pCur->GetParamCount();
 else
 {
-SAL_WARN("sc.core", "Stack anomaly at " << aPos.Tab() << 
"," << aPos.Col() << "," << aPos.Row()
-<< "  " << aPos.Format(
-ScRefFlags::VALID | ScRefFlags::FORCE_DOC | 
ScRefFlags::TAB_3D, )
-<< "  eOp: " << static_cast(eOp)
-<< "  params: " << 
static_cast(pCur->GetParamCount())
-<< "  nStackBase: " << nStackBase << "  sp: " << 
sp);
-nStackBase = sp;
-assert(!"underflow");
+const sal_uInt8 nParamCount = pCur->GetParamCount();
+if (sp >= nParamCount)
+nStackBase = sp - nParamCount;
+else
+{
+SAL_WARN("sc.core", "Stack anomaly at " << aPos.Tab() 
<< "," << aPos.Col() << "," << aPos.Row()
+<< "  " << aPos.Format(
+ScRefFlags::VALID | ScRefFlags::FORCE_DOC 
| ScRefFlags::TAB_3D, )
+<< "  eOp: " << static_cast(eOp)
+<< "  params: " << 
static_cast(nParamCount)
+<< "  nStackBase: " << nStackBase << "  sp: " 
<< sp);
+nStackBase = sp;
+assert(!"underflow");
+}
 }
 }
 

core.git: Branch 'distro/cib/libreoffice-6-4' - desktop/source

[Stephan Bergmann (via logerrit)]

 desktop/source/minidump/minidump.cxx |6 ++
 1 file changed, 6 insertions(+)

New commits:
commit 344a00b2a4c358e3c0a66f0c163c874a5ebdcc08
Author: Stephan Bergmann 
AuthorDate: Fri Apr 12 17:42:45 2024 +0200
Commit: Stephan Bergmann 
CommitDate: Sat Apr 13 00:30:21 2024 +0200

At least capture (English-only) cURL error when something goes wrong

...so that svx/source/dialog/crashreportdlg.cxx can at least present that,
instead of confusingly being silent about the error

Change-Id: I5e8af5f8df4cbcad84f8b60c2de4c55621b28890
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/166037
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann 
(cherry picked from commit 324401ced3c2234903f9e0430a0380be968b492b)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/165941
Tested-by: allotropia jenkins 

diff --git a/desktop/source/minidump/minidump.cxx 
b/desktop/source/minidump/minidump.cxx
index 8b96d2ff37f1..e1f3eb4c5a94 100644
--- a/desktop/source/minidump/minidump.cxx
+++ b/desktop/source/minidump/minidump.cxx
@@ -184,7 +184,13 @@ static bool uploadContent(std::map& parameters, std::s
 response = response_body;
 
 if( CURLE_OK != cc )
+{
+if (response.empty())
+{
+response = curl_easy_strerror(cc);
+}
 return false;
+}
 
 return true;
 }

[Bug 147463] Clicking on field link scrolls to page, but focuses only 1/3 of the page in question

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=147463

--- Comment #7 from Haris  ---
Hi Telesto,

This is still reproducible in 

Stable Build
Version: 24.2.2.2 (AARCH64) / LibreOffice Community
Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01
CPU threads: 10; OS: macOS 14.1.2; UI render: Skia/Metal; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

Master/Daily Build
Version: 24.8.0.0.alpha0+ (AARCH64) / LibreOffice Community
Build ID: c4023d3ec604abfff38be2053e2989c7ec2ba8c1
CPU threads: 10; OS: macOS 14.1.2; UI render: Skia/Metal; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

core.git: desktop/source

[Stephan Bergmann (via logerrit)]

 desktop/source/minidump/minidump.cxx |6 ++
 1 file changed, 6 insertions(+)

New commits:
commit 6a4031ec8338b005682493f65744ebcbc30a5f81
Author: Stephan Bergmann 
AuthorDate: Fri Apr 12 17:42:45 2024 +0200
Commit: Stephan Bergmann 
CommitDate: Fri Apr 12 23:36:48 2024 +0200

At least capture (English-only) cURL error when something goes wrong

...so that svx/source/dialog/crashreportdlg.cxx can at least present that,
instead of confusingly being silent about the error

Change-Id: I5e8af5f8df4cbcad84f8b60c2de4c55621b28890
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/166037
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann 

diff --git a/desktop/source/minidump/minidump.cxx 
b/desktop/source/minidump/minidump.cxx
index 0a31fff6f285..90d23f51acf3 100644
--- a/desktop/source/minidump/minidump.cxx
+++ b/desktop/source/minidump/minidump.cxx
@@ -184,7 +184,13 @@ static bool uploadContent(std::map& parameters, std::s
 response = response_body;
 
 if( CURLE_OK != cc )
+{
+if (response.empty())
+{
+response = curl_easy_strerror(cc);
+}
 return false;
+}
 
 return true;
 }

[Bug 160375] Base does not manage relationships outside the default catalog/schema

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160375

--- Comment #6 from prrv...@gmail.com ---
Please find me a reviewers...

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160640] Text convert to a meta file wrong

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160640

--- Comment #3 from V Stuart Foote  ---
(In reply to Luca Rodenhäuser from comment #2)
> I will, that the Text is a meta file (Text to SVG). When I use the function
> in Impress, in Impress it converts, but when I export th e to a meta file
> converted Text it's in the pdf against Text and not how I want it a meta
> file.

Sorry, but that makes no sense. PDF is not a meta-file format (i.e. a vector
image). It you need a vector image format--export the Impress slide or Draw
page as a vector file, you have EMF, SVG, WMF to choose from.

Otherwise, the x-svm .svm held within the ODF archive's Pictures directory (the
ODF archive just a Zip file) that can be extracted. And the .svm opened
directly as a Draw image.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 108438] [META] Animated image bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=108438

Telesto  changed:

   What|Removed |Added

 Depends on||160646


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=160646
[Bug 160646] GIF don't animate in edit mode; are rendered as still images
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160646] GIF don't animate in edit mode; are rendered as still images

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160646

Telesto  changed:

   What|Removed |Added

 Blocks||108438


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=108438
[Bug 108438] [META] Animated image bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 143262] GIF image stops animating in edit mode after cropping (does work in presentation mode)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=143262

Telesto  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||6911

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 156911] GIF does not play in edit mode if the attributes "Name" or "Description" are set [EDITING]

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=156911

Telesto  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=14
   ||3262

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 156911] GIF does not play in edit mode if the attributes "Name" or "Description" are set [EDITING]

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=156911

Telesto  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=16
   ||0646

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 143262] GIF image stops animating in edit mode after cropping (does work in presentation mode)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=143262

Telesto  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=16
   ||0646

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160646] GIF don't animate in edit mode; are rendered as still images

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160646

Telesto  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=14
   ||3262,
   ||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||6911

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160646] New: GIF don't animate in edit mode; are rendered as still images

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160646

Bug ID: 160646
   Summary: GIF don't animate in edit mode; are rendered as still
images
   Product: LibreOffice
   Version: 24.2.0.0 alpha1+
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Impress
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: tele...@surfxs.nl

Description:
GIF don't animate in edit mode; are rendered as still images

Steps to Reproduce:
1. Open attachment 159163


Actual Results:
Still images in edit mode

Expected Results:
Animated images in edit mode. Although still images being a lot better for
performance 


Reproducible: Always


User Profile Reset: No

Additional Info:
Found in
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 748561425774fa40ab685fed80d113f7e8301158
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL threaded

and in
Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 898d5d470e24a6f2fb244fec24df33ba8855
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL threaded

Fine in
Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 77befddec9486403c471b2beafd4ca0fd2429c5a
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160640] Text convert to a meta file wrong

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160640

--- Comment #2 from Luca Rodenhäuser  ---
I will, that the Text is a meta file (Text to SVG). When I use the function in
Impress, in Impress it converts, but when I export th e to a meta file
converted Text it's in the pdf against Text and not how I want it a meta file.

-- 
You are receiving this mail because:
You are the assignee for the bug.

core.git: sc/source

[Caolán McNamara (via logerrit)]

 sc/source/filter/html/htmlpars.cxx |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 54d577ed22fd4bae093639be3056a722f5a40bb2
Author: Caolán McNamara 
AuthorDate: Fri Apr 12 15:24:53 2024 +0100
Commit: Caolán McNamara 
CommitDate: Fri Apr 12 21:40:09 2024 +0200

ofz#68004 Unknown Read

Change-Id: Id3e50e3a8522523d2b665e394d8f4a65b7f4df5d
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/166034
Tested-by: Jenkins
Reviewed-by: Caolán McNamara 

diff --git a/sc/source/filter/html/htmlpars.cxx 
b/sc/source/filter/html/htmlpars.cxx
index 83d9c01fbf7e..5d27f751ab6c 100644
--- a/sc/source/filter/html/htmlpars.cxx
+++ b/sc/source/filter/html/htmlpars.cxx
@@ -778,7 +778,7 @@ void ScHTMLLayoutParser::SetWidths()
 if ( pE->nTab == nTable && pE->nWidth )
 {
 SCCOL nCol = pE->nCol - nColCntStart;
-if ( nCol < nColsPerRow )
+if (nCol >= 0 && nCol < nColsPerRow)
 {
 if ( pE->nColOverlap == 1 )
 {

[Bug 160640] Text convert to a meta file wrong

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160640

V Stuart Foote  changed:

   What|Removed |Added

 CC||vsfo...@libreoffice.org

--- Comment #1 from V Stuart Foote  ---
Can not confirm, the ODF archive is saved with both an x-svm meta file (from
StarOffice legacy) and with a PNG raster. There will be a transformation
applied as needed to position or 

If I rotate or flip the textbox, on save and export to PDF the transforms for
the meta file are used for writing the PDF.

And if I extract the .svm or .png from the pictures directory of the ODF
archive, they behave as an image (i.e. the .svm text is not annotation).

This is true for both sd modules, Impress or Draw.

Version: 24.2.2.1 (X86_64) / LibreOffice Community
Build ID: bf759d854b5ab45b6ef0bfd22e51c6dc4fb8b882
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160629] Bullets and Numbering dialog in Writer does not say it's about an implicit list style

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160629

Robert Großkopf  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=16
   ||0617

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160617] Bulleted lists have different indentations

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160617

Robert Großkopf  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=16
   ||0629

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160629] Bullets and Numbering dialog in Writer does not say it's about an implicit list style

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160629

Robert Großkopf  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=16
   ||0617

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 160617] Bulleted lists have different indentations

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160617

Robert Großkopf  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 CC||rob...@familiegrosskopf.de
 Ever confirmed|0   |1

--- Comment #4 from Robert Großkopf  ---
Have had a look:
Bullets and numbering are formatted in another way when choosing the style
format:
Bullets use 0 mm on the left and tab to 4 mm
Numbering uses 6.3 mm on the left and tab to 7 mm.

If you try it with direct formatting it is both 6.3 mm to the left and 6.4 mm
for the tab.

Might be the default styles for Bullets and Numbering should be the same as the
styles, which you get by direct formatting.
I will set this one to NEW.

Tested with
Version: 24.2.2.2 (X86_64) / LibreOffice Community
Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01
CPU threads: 6; OS: Linux 6.4; UI render: default; VCL: kf5 (cairo+xcb)
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160645] New: Shut Down

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160645

Bug ID: 160645
   Summary: Shut Down
   Product: LibreOffice
   Version: 24.2.0.3 release
  Hardware: ARM
OS: macOS (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Draw
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: jk85...@icloud.com

Libreoffice goes down wenn closing 3D Effects.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160093] Navigator empty after inserting formula OLE object

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160093

Jim Raykowski  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #6 from Jim Raykowski  ---
(In reply to Stéphane Guillou (stragu) from comment #5)
> OK to mark as fixed and cherrypick to 24.2 and 7.6 if straight-forward?
Sorry for not marking this as fixed sooner. I think it would be OK to
cherrypick to 24.2 and 7.6.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 103030] [META] Navigator sidebar deck and floating window (also "Target in Document")

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=103030
Bug 103030 depends on bug 160093, which changed state.

Bug 160093 Summary: Navigator empty after inserting formula OLE object
https://bugs.documentfoundation.org/show_bug.cgi?id=160093

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160578] BASIC Runtime error. Object variable not set. Happens when the argument of sub procedure is not an object

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160578

Robert Großkopf  changed:

   What|Removed |Added

 CC||rob...@familiegrosskopf.de

--- Comment #1 from Robert Großkopf  ---
You couldn't print
pvArg.SupportsService("com.sun.star.table.Cell")

You could print "Object" instead.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 152220] macOS: UI in dark mode - tabs in dialogs get overlaid with previously shown tabs (macOS 10.15 and 11.7)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152220

V Stuart Foote  changed:

   What|Removed |Added

 CC||vsfo...@libreoffice.org
Summary|macOS: UI in dark mode -|macOS: UI in dark mode -
   |tabs in dialogs get |tabs in dialogs get
   |overlaid with previously|overlaid with previously
   |shown tabs (macOS 10 and|shown tabs (macOS 10.15 and
   |11) |11.7)

-- 
You are receiving this mail because:
You are the assignee for the bug.

core.git: offapi/org static/source unotest/source

[Stephan Bergmann (via logerrit)]

 offapi/org/libreoffice/embindtest/XTest.idl |3 
 static/source/embindmaker/embindmaker.cxx   |  160 ++--
 unotest/source/embindtest/embindtest.cxx|   22 +++
 unotest/source/embindtest/embindtest.js |   36 ++
 4 files changed, 212 insertions(+), 9 deletions(-)

New commits:
commit 3454a73a11722c45016c9b5aa0d95402fc1196f0
Author: Stephan Bergmann 
AuthorDate: Fri Apr 12 08:57:44 2024 +0200
Commit: Stephan Bergmann 
CommitDate: Fri Apr 12 20:52:54 2024 +0200

Embind: support .implement()-based JS UNO objects

Change-Id: I3a8bf5986b91b886547cfe57e49275f7c79ddc11
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/166020
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann 

diff --git a/offapi/org/libreoffice/embindtest/XTest.idl 
b/offapi/org/libreoffice/embindtest/XTest.idl
index b3b5237ce2b4..8817e94669fc 100644
--- a/offapi/org/libreoffice/embindtest/XTest.idl
+++ b/offapi/org/libreoffice/embindtest/XTest.idl
@@ -113,6 +113,9 @@ interface XTest {
 sequence getSequenceStruct();
 boolean isSequenceStruct([in] sequence value);
 void throwRuntimeException();
+void passJob([in] com::sun::star::task::XJob object);
+void passJobExecutor([in] com::sun::star::task::XJobExecutor object);
+void passInterface([in] com::sun::star::uno::XInterface object);
 };
 
 }; }; };
diff --git a/static/source/embindmaker/embindmaker.cxx 
b/static/source/embindmaker/embindmaker.cxx
index 4241d10b1575..07214c289681 100644
--- a/static/source/embindmaker/embindmaker.cxx
+++ b/static/source/embindmaker/embindmaker.cxx
@@ -501,7 +501,7 @@ void dumpAttributes(std::ostream& out, 
rtl::Reference const& manage
 }
 out << "->get" << attr.name << "(); }";
 }
-out << ")
";
+out << ", ::emscripten::pure_virtual())
";
 if (!attr.readOnly)
 {
 out << ".function(\"set" << attr.name << "\", ";
@@ -530,7 +530,7 @@ void dumpAttributes(std::ostream& out, 
rtl::Reference const& manage
 }
 out << "->set" << attr.name << "(the_value); }";
 }
-out << ")
";
+out << ", ::emscripten::pure_virtual())
";
 }
 }
 }
@@ -660,7 +660,7 @@ void dumpWrapper(std::ostream& out, 
rtl::Reference const& manager,
 {
 out << ", ::emscripten::allow_raw_pointers()";
 }
-out << ")
";
+out << ", ::emscripten::pure_virtual())
";
 }
 
 void dumpMethods(std::ostream& out, rtl::Reference const& manager,
@@ -676,18 +676,18 @@ void dumpMethods(std::ostream& out, 
rtl::Reference const& manager,
 else
 {
 out << ".function(\"" << meth.name << "\", &" << 
cppName(name)
-<< "::" << meth.name << ")
";
+<< "::" << meth.name << ", ::emscripten::pure_virtual())
";
 }
 }
 }
 
-rtl::Reference 
resolveBase(rtl::Reference const& manager,
-OUString const& name)
+rtl::Reference
+resolveInterface(rtl::Reference const& manager, OUString const& 
name)
 {
 auto const ent = manager->getManager()->findEntity(name);
 if (!ent.is() || ent->getSort() != unoidl::Entity::SORT_INTERFACE_TYPE)
 {
-throw CannotDumpException("bad interface base \"" + name + "\"");
+throw CannotDumpException("bad interface \"" + name + "\"");
 }
 return static_cast(ent.get());
 }
@@ -695,7 +695,7 @@ rtl::Reference 
resolveBase(rtl::Reference const& manager, OUString 
const& name,
 std::set& visitedBases)
 {
-auto const ent = resolveBase(manager, name);
+auto const ent = resolveInterface(manager, name);
 for (auto const& base : ent->getDirectMandatoryBases())
 {
 if (visitedBases.insert(base.name).second)
@@ -709,7 +709,7 @@ void dumpBase(std::ostream& out, 
rtl::Reference const& manager,
   OUString const& interface, OUString const& name, 
std::set& visitedBases,
   std::list const& baseTrail)
 {
-auto const ent = resolveBase(manager, name);
+auto const ent = resolveInterface(manager, name);
 for (auto const& base : ent->getDirectMandatoryBases())
 {
 if (visitedBases.insert(base.name).second)
@@ -723,6 +723,126 @@ void dumpBase(std::ostream& out, 
rtl::Reference const& manager,
 dumpMethods(out, manager, interface, ent, baseTrail);
 }
 
+void dumpWrapperClassMembers(std::ostream& out, rtl::Reference 
const& manager,
+ OUString const& interface, OUString const& name,
+ std::set& visitedBases)
+{
+auto const ent = resolveInterface(manager, name);
+for (auto const& base : ent->getDirectMandatoryBases())
+{
+if (visitedBases.insert(base.name).second)
+{
+dumpWrapperClassMembers(out, manager, interface, base.name, 
visitedBases);
+}
+}
+for (auto const& attr : 

[Bug 160510] When pasting text styled with character format to a new document that style isn't edit-able

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160510

Robert Großkopf  changed:

   What|Removed |Added

 CC||rob...@familiegrosskopf.de

--- Comment #7 from Robert Großkopf  ---
Tested the attached file with 
Version: 24.2.2.2 (X86_64) / LibreOffice Community
Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01
CPU threads: 6; OS: Linux 6.4; UI render: default; VCL: kf5 (cairo+xcb)
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Calc: threaded
"Taste" is editable here.

Get the same with LO 7.6.4 and LO 7.5.5 on the same system: OpenSUSE 15.6 Beta
64bit rpm Linux

Might be the behavior has something to do with user profile. So test it in safe
mode or with a renamed user profile

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 159802] Writer Document does not print with Form detail in 24.2 release

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159802

Robert Großkopf  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=16
   ||0628

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160628] PDF and PRINTING checkbox - form fields are not or wrong in an exported pdf or printout

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160628

Robert Großkopf  changed:

   What|Removed |Added

 CC||rob...@familiegrosskopf.de
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||9802

--- Comment #8 from Robert Großkopf  ---
Isn't this one a duplicate of
https://bugs.documentfoundation.org/show_bug.cgi?id=159802 ?

Please try with LO 24.2.2.2

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160605] Calc Sort via AU3, VBA/VBS external script doesn't sort.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160605

--- Comment #1 from Don  ---
I can confirm the problem is present in 24.2 release also.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160096] Validity list set to not show error message does not allow unlisted values to be entered

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160096

ady  changed:

   What|Removed |Added

 CC||nathan.rive...@outlook.fr

--- Comment #18 from ady  ---
*** Bug 160638 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160638] Validation lists and free entries

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160638

--- Comment #2 from ady  ---
(In reply to Julien Nabet from comment #1)
> If the value is not in the definition list, it shouldn't be possible to use
> it then.
> It was the case before 24.2.1 but this "feature" was a bug.
> Duplicate of tdf#159595
> 

The qualification of the old behavior as a bug comes from some (specific) LO
devs. Common users, especially experienced/older users of other spreadsheet
tools, will still call it a feature. This and similar reports will show up
repeatedly, as in tdf#160096.

*** This bug has been marked as a duplicate of bug 160096 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 147021] Use std::size() or std::ssize() instead of SAL_N_ELEMENTS() macro

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=147021

--- Comment #51 from Commit Notification 
 ---
Ashwani5009 committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/ea462462db187d87d978cb659df8ca81309fd2e7

tdf#147021 Replace SAL_N_ELEMENTS with std::size

It will be available in 24.8.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

-- 
You are receiving this mail because:
You are the assignee for the bug.

core.git: i18npool/qa i18npool/source

[Ashwani5009 (via logerrit)]

 i18npool/qa/cppunit/test_breakiterator.cxx|2 +-
 i18npool/source/nativenumber/nativenumbersupplier.cxx |6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)

New commits:
commit ea462462db187d87d978cb659df8ca81309fd2e7
Author: Ashwani5009 
AuthorDate: Thu Apr 11 23:53:25 2024 +0530
Commit: Ilmari Lauhakangas 
CommitDate: Fri Apr 12 19:54:13 2024 +0200

tdf#147021 Replace SAL_N_ELEMENTS with std::size

As part of the efforts in #145538 to replace the SAL_N_ELEMENTS()
macro with std::size() and std::ssize(), this commit performs the
necessary changes for a few files in the i18npool module.

Change-Id: Ic64be31b74cd74faf17497a47d6a15158b85184c
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/166013
Tested-by: Jenkins
Tested-by: Ilmari Lauhakangas 
Reviewed-by: Ilmari Lauhakangas 

diff --git a/i18npool/qa/cppunit/test_breakiterator.cxx 
b/i18npool/qa/cppunit/test_breakiterator.cxx
index 4463f46270e1..0f2629fe05ec 100644
--- a/i18npool/qa/cppunit/test_breakiterator.cxx
+++ b/i18npool/qa/cppunit/test_breakiterator.cxx
@@ -368,7 +368,7 @@ void TestBreakIterator::testWordBoundaries()
 }
 
 const sal_Int32 aSinglePositions[] = {0, 1, 3, 4, 6, 7, 9, 10};
-for (size_t j = 1; j < SAL_N_ELEMENTS(aTests); ++j)
+for (size_t j = 1; j < std::size(aTests); ++j)
 {
 OUString aTest = aBase.replaceAll("xx", OUStringChar(aTests[j]));
 sal_Int32 nPos = -1;
diff --git a/i18npool/source/nativenumber/nativenumbersupplier.cxx 
b/i18npool/source/nativenumber/nativenumbersupplier.cxx
index f57cc2022e2e..57e2355e15c0 100644
--- a/i18npool/source/nativenumber/nativenumbersupplier.cxx
+++ b/i18npool/source/nativenumber/nativenumbersupplier.cxx
@@ -668,7 +668,7 @@ OUString 
NativeNumberSupplierService::getNativeNumberString(const OUString& aNum
 
 std::size_t nStripCase = 0;
 size_t nCasing;
-for (nCasing = 0; nCasing < SAL_N_ELEMENTS(Casings); ++nCasing)
+for (nCasing = 0; nCasing < std::size(Casings); ++nCasing)
 {
 if (o3tl::starts_with(rNativeNumberParams, 
Casings[nCasing].aLiteral))
 {
@@ -1064,7 +1064,7 @@ static void makeHebrewNumber(sal_Int64 value, 
OUStringBuffer& output, bool isLas
 output.append(value == 1000 ? thousand : isLast ? thousands_last : 
thousands);
 } else {
 sal_Int16 nbOfChar = 0;
-for (sal_Int32 j = 0; num > 0 && j < 
sal_Int32(SAL_N_ELEMENTS(HebrewNumberCharArray)); j++) {
+for (sal_Int32 j = 0; num > 0 && j < 
sal_Int32(std::size(HebrewNumberCharArray)); j++) {
 if (num - HebrewNumberCharArray[j].value >= 0) {
 nbOfChar++;
 // https://en.wikipedia.org/wiki/Hebrew_numerals#Key_exceptions
@@ -1177,7 +1177,7 @@ static void makeCyrillicNumber(sal_Int64 value, 
OUStringBuffer& output, bool add
 addTitlo = false;
 }
 
-for (sal_Int32 j = 0; num > 0 && j < 
sal_Int32(SAL_N_ELEMENTS(CyrillicNumberCharArray)); j++) {
+for (sal_Int32 j = 0; num > 0 && j < 
sal_Int32(std::size(CyrillicNumberCharArray)); j++) {
 if (num < 20 && num > 10) {
 num -= 10;
 makeCyrillicNumber(num, output, false);

[Bug 36535] EDITING: Updating of Frame Style not working correctly, anchoring to character do not updates

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=36535

--- Comment #20 from Eyal Rozenberg  ---
Indeed, also seeing this with the reproduction instructions in comment #19 and:

24.2.0.2 (X86_64) / LibreOffice Community
Build ID: b1fd3a6f0759c6f806568e15c957f97194bbec8f
CPU threads: 4; OS: Linux 6.6; UI render: default; VCL: gtk3
Locale: en-IL (en_IL); UI: en-US

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 155089] No way to create pivot table compact layout from scratch

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155089

Michael Otto  changed:

   What|Removed |Added

 CC||micha.otto...@gmail.com
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=16
   ||0107

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160107] FORMATTING: Pivot Row field with Compact layout supports only Standard Format

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160107

Michael Otto  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||5089

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160396] PIVOTTABLE: Row Field's drop down menus missing when last Row Field set to Compact layout

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160396

Michael Otto  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160397] PIVOTTABLE: Compact layout missing Text values in Row Field

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160397

Michael Otto  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.