[Bug 116108] Add option to fit images into their cell

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=116108

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

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

[Bug 155285] Cell anchored callout loses position in save and reload

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155285

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

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

[Bug 87740] [META] Anchor and text wrapping bugs and enhancements

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=87740

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||158592


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158592
[Bug 158592] Control anchored and fit to cell jumps to different cell when
changing Anchor setting in Control Properties
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 107742] [META] Form control bugs and enhancements

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107742

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||158592


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158592
[Bug 158592] Control anchored and fit to cell jumps to different cell when
changing Anchor setting in Control Properties
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158592] New: Control anchored and fit to cell jumps to different cell when changing Anchor setting in Control Properties

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158592

Bug ID: 158592
   Summary: Control anchored and fit to cell jumps to different
cell when changing Anchor setting in Control
Properties
   Product: LibreOffice
   Version: Inherited From OOo
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: stephane.guil...@libreoffice.org
CC: samuel.mehrbr...@allotropia.de
Blocks: 87740, 107742

If the anchoring of a form control that was resized to fit the cell is set "to
cell" from the Control Properties dialog, it moves to another cell toward the
top left.

Steps:
1. Open Calc (or open attachment and jump to step 6)
2. Insert > Form Control > Text box
3. Trace the control further than column C and row 2 (for example, on cell E10)
4. right-click on the control > Anchor > To cell (or "resize with cell", same
thing)
5. right-click on the control > Fit to cell size
6. right-click on the control > Control properties > Anchor > To cell
(repeatedly)

Result: the control jumps from cell to cell at each click, until it settles in
cell C2. The change can't be undone.
Same happens with other controls, e.g. a Numerical Field.

Note that the setting does not have the option "To cell (resize with cell)",
which might be related to the issue?

Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 0ddd9f7e055a0c1ecb120de3e40c3fdb8373e9dc
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Also reproduced with sample file in Ooo 3.3, so issue is inherited (although
the option to "Fit to Cell Size" was only added in 6.1 for bug 116108).

Seems to have to do with the position of the top-right corner, possibly because
of rounding.

Samuel, I thought you might be interested?


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=87740
[Bug 87740] [META] Anchor and text wrapping bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107742
[Bug 107742] [META] Form control bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158588] ODT bloats in file size by factor 4 by saving without changes, font embedding options based on two checkboxes should be redesigned

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158588

OfficeUser  changed:

   What|Removed |Added

 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org
   Keywords||needsUXEval

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

[Bug 112059] Events fired by subform changed, when form is write-protected

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=112059

--- Comment #14 from Robert Großkopf  ---
Behavior still exists in
Version: 24.2.0.0.alpha1 (X86_64) / LibreOffice Community
Build ID: 06946980c858649160c634007e5fac9a5aa81f38
CPU threads: 6; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb)
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Calc: threaded

Don't know why "AfterRecordChange should appear when there isn't any record,
which could be shown and could be changed.

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

[Bug 158587] Improve column/row highlighting in Calc

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158587

Buovjaga  changed:

   What|Removed |Added

 CC||ilmari.lauhakangas@libreoff
   ||ice.org

--- Comment #5 from Buovjaga  ---
So should the extra highlighting be deactivated in case multiple cells are
selected?

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

[Bug 133092] [META] Crash bugs

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=133092

BogdanB  changed:

   What|Removed |Added

 Depends on||158505


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158505
[Bug 158505] Crash exporting .docx file to Pdf
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 101258] [META] Bibliography bugs and enhancements

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=101258

BogdanB  changed:

   What|Removed |Added

 Depends on||158505


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158505
[Bug 158505] Crash exporting .docx file to Pdf
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158505] Crash exporting .docx file to Pdf

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158505

BogdanB  changed:

   What|Removed |Added

 Blocks||101258, 133092
 CC||buzea.bog...@libreoffice.or
   ||g


Referenced Bugs:

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

[Bug 108252] [META] Cell-related bugs and enhancements (including formatting)

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108252

BogdanB  changed:

   What|Removed |Added

 Depends on||158555


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158555
[Bug 158555] [NatNum12] does not allow literal text to the left of 0
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158555] [NatNum12] does not allow literal text to the left of 0

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158555

BogdanB  changed:

   What|Removed |Added

 Blocks||108252
 CC||buzea.bog...@libreoffice.or
   ||g


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=108252
[Bug 108252] [META] Cell-related bugs and enhancements (including formatting)
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 103304] [META] Page style dialog bugs and enhancements

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103304

BogdanB  changed:

   What|Removed |Added

 Depends on||158572


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158572
[Bug 158572] Translation problem in Calc - Portuguese PT
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158572] Translation problem in Calc - Portuguese PT

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158572

BogdanB  changed:

   What|Removed |Added

 Blocks||103304
 CC||buzea.bog...@libreoffice.or
   ||g


Referenced Bugs:

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

[Bug 158584] Problem "Save As" from LibreOffice Writer to fileformat: "Word 2003 XML (.xml)" - width of table(s) decreases to 2%

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158584

BogdanB  changed:

   What|Removed |Added

 CC||buzea.bog...@libreoffice.or
   ||g
 Blocks||108254


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=108254
[Bug 108254] [META] File format filters (import/export) bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 108254] [META] File format filters (import/export) bugs and enhancements

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108254

BogdanB  changed:

   What|Removed |Added

 Depends on||158584


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158584
[Bug 158584] Problem "Save As" from LibreOffice Writer to fileformat: "Word
2003 XML (.xml)" - width of table(s) decreases to 2%
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158591] New: gdb prints "No symbol 'xxx' in current context" when debuging on riscv64

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158591

Bug ID: 158591
   Summary: gdb prints "No symbol 'xxx' in current context" when
debuging on riscv64
   Product: LibreOffice
   Version: unspecified
  Hardware: Other
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: sakura...@outlook.com

Description:
I am working with the latest commit of the source code on an riscv64 machine.
But gdb behaves not correctly.

When I print a variable, such as xxx, gdb prints "No symbol 'xxx' in current
context". I can't print the value of any variable. But other functions of gdbs
are working fine, such as setting breakpoint and print stack.

What should I do to fix this?

Steps to Reproduce:
On a riscv64 machine, build libreoffice with "--enable-debug". Then debug any
.cxx file and print any variable.

Actual Results:
gdb prints "No symbol 'xxx' in current context"

Expected Results:
The value of the variable printed.


Reproducible: Always


User Profile Reset: No

Additional Info:
gdb version 13.2
gcc version 13.2

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

[Bug 116979] [META] Regression introduced by Aw080

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=116979
Bug 116979 depends on bug 122735, which changed state.

Bug 122735 Summary: Entering a group does not make the other objects paler / 
dimmed anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=122735

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED

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

[Bug 108640] [META] Object meta bugs and enhancements

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108640
Bug 108640 depends on bug 122735, which changed state.

Bug 122735 Summary: Entering a group does not make the other objects paler / 
dimmed anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=122735

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED

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

[Bug 158590] Interface design bug "Scale" for Draw documents

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158590

Mike Kaganski  changed:

   What|Removed |Added

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

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

[Bug 158590] Interface design bug "Scale" for Draw documents

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158590

--- Comment #1 from Mike Kaganski  ---
(In reply to juani...@gmail.com from comment #0)
> This means that if I want to change the scale used for the current document,
> I must change the scale on the "options" dialog

https://wiki.documentfoundation.org/ReleaseNotes/7.2#User_Interface

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

[Bug 158577] Allow locking down adding new trusted authors

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158577

QA Administrators  changed:

   What|Removed |Added

   Keywords||bibisectRequest

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

[Bug 158340] Page Style Header and Footer tabs: Add setting for choosing Header Right/Left Footer Right/Left

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158340

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 158332] Areas from the context menu remain after exiting the presentation (VCL gtk3, DE kde and Xfce)

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158332

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 158334] EDITING selecting and deselecting a connector is slow

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158334

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 158523] Whole pages of Comments are not PRINTING or exported to PDF in margins

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158523

--- Comment #4 from QA Administrators  ---
[Automated Action] NeedInfo-To-Unconfirmed

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

[Bug 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98259
Bug 98259 depends on bug 106196, which changed state.

Bug 106196 Summary: EDITING Impress doesn't recognize shortcuts for bulleted 
lists
https://bugs.documentfoundation.org/show_bug.cgi?id=106196

   What|Removed |Added

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

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

[Bug 158523] Whole pages of Comments are not PRINTING or exported to PDF in margins

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158523

QA Administrators  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

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

[Bug 155237] Items on drawing moved between different sessions, and now unable to correct or delete them

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155237

--- Comment #3 from QA Administrators  ---
Dear Gordon Patnude,

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 106196] EDITING Impress doesn't recognize shortcuts for bulleted lists

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=106196

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 104485] Alphabetizing text selection function in Writer

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104485

--- Comment #6 from QA Administrators  ---
Dear Dr. Pam Halton,

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 106196] EDITING Impress doesn't recognize shortcuts for bulleted lists

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=106196

--- Comment #7 from QA Administrators  ---
Dear doriano.mag,

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 104485] Alphabetizing text selection function in Writer

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104485

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 155734] It takes too long time to open an '.odt' document

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155734

--- Comment #2 from QA Administrators  ---
Dear Ole Jansen,

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 94512] SIDEBAR collapses when previewing a document

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=94512

--- Comment #11 from QA Administrators  ---
Dear Jean-Francois Nifenecker,

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 92762] WRITER paragraph with list style is different from paragraph style + separate list style

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=92762

--- Comment #9 from QA Administrators  ---
Dear Philippe Jung,

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 82170] FILEOPEN: MSO ODT - Incorrect indent for bullets and numbering

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=82170

--- Comment #14 from QA Administrators  ---
Dear Yousuf Philips (jay) (retired),

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 76736] ODF import: default-cell-style-name attribute is ignored everywhere when last of table row has no such attribute.

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=76736

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

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 72442] UI: When I try to add a hyperlink to a bookmark in the same document, the list with bookmarks closes itself

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=72442

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

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 37903] EDITING: Moving object using ALT - cursor keys also moves the object behind it

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=37903

--- Comment #20 from QA Administrators  ---
Dear gleppert,

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 58270] Spaces between 'Category and Numbering' cross-references should be a non-breaking space

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=58270

--- Comment #14 from QA Administrators  ---
Dear Olivier Diotte,

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 33154] Interaction (Execute) is generally buggy

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=33154

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

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 139472] Adding internal hyperlinks to unnamed slides causes links to break when switching UI languages due to link anchors pointing to the localised names

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139472

--- Comment #6 from QA Administrators  ---
Dear Gael Langlais,

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 120310] Ambiguous error message returned when attempting to use certain special characters in field names

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=120310

--- Comment #16 from QA Administrators  ---
Dear elflng.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 119431] External database jdbc hsqldb, Crash in the case of SELECT, SQL query, access to the database

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=119431

--- Comment #28 from QA Administrators  ---
Dear Krzysztof,

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 112059] Events fired by subform changed, when form is write-protected

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=112059

--- Comment #13 from QA Administrators  ---
Dear Robert Großkopf,

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 114041] There is some lag around images when reducing a selection by scrolling upwards

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=114041

--- Comment #8 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 107839] BeforeUpdating and AfterUpdating events are not firing when records are edited in a Table Control

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107839

--- Comment #14 from QA Administrators  ---
Dear Howard Johnson,

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 109326] [META] Data filter bugs and enhancements

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=109326

Aron Budea  changed:

   What|Removed |Added

 Depends on||158440


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158440
[Bug 158440] Filter for background should take colors in empty cells
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158440] Filter for background should take colors in empty cells

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158440

Aron Budea  changed:

   What|Removed |Added

 Blocks||109326


Referenced Bugs:

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

[Bug 126084] DOCX/OOXML support of SVG images via Office Drawing extension and fallback (published schema)

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=126084

--- Comment #11 from Commit Notification 
 ---
Tomaž Vajngerl committed a patch related to this issue.
It has been pushed to "master":

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

tdf#126084 document OOXML SVG tests and import

It will be available in 24.2.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.

[Bug 158249] Document with one landscape page doesn't switch back to portrait when PRINTING.

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158249

Kira Tubo  changed:

   What|Removed |Added

Version|7.6.2.1 release |4.4.7.2 release
 CC||kira.t...@gmail.com

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

[Bug 143148] Use pragma once instead of include guards (Episode 2: Endgame)

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143148

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

https://git.libreoffice.org/core/commit/7081b28dd6ed1ab8b8d6528d94e44e5dc3b3121d

tdf#143148 Use pragma once instead of include guards

It will be available in 24.2.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.

[Bug 66791] FORMATTING: Incorrect application of "Asian text font" for quotation marks when the paragraph contains a mixture of western and asian characters

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=66791

--- Comment #29 from Kevin Suo  ---
See a related articles:

中西文混合排版中标点符号的渲染
https://blog.1a23.com/2020/06/28/zhong-xi-wen-hunhe-paiban-zhong-biaodian-fuhao-de-xuanran/

中英混排中的标点符号问题 https://www.hutrua.com/blog/2018/07/22/punctuation.html

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

[Bug 116979] [META] Regression introduced by Aw080

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=116979
Bug 116979 depends on bug 122735, which changed state.

Bug 122735 Summary: Entering a group does not make the other objects paler / 
dimmed anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=122735

   What|Removed |Added

 Status|VERIFIED|REOPENED
 Resolution|FIXED   |---

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

[Bug 108640] [META] Object meta bugs and enhancements

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108640
Bug 108640 depends on bug 122735, which changed state.

Bug 122735 Summary: Entering a group does not make the other objects paler / 
dimmed anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=122735

   What|Removed |Added

 Status|VERIFIED|REOPENED
 Resolution|FIXED   |---

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

[Bug 137080] LibreOffice should use built-in OpenType Feature Small Capitals (smcp tag) when the typeface has it instead of simulated Small Capitals

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137080

--- Comment #4 from nj  ---
Might I bump this issue? For, if it is related to small caps in PowerPoint
files ending up always as actual capitals within Impress, then that this a
fairly serious problem. (Impress compatibility with PointPoint has come a long
away. It is a shame to let that compatibility founder on a small but important
point such as this one.)

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

[Bug 158590] New: Interface design bug "Scale" for Draw documents

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158590

Bug ID: 158590
   Summary: Interface design bug "Scale"  for Draw documents
   Product: LibreOffice
   Version: 3.3.0 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Draw
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: juani...@gmail.com

Description:
The basic problem is that no distinction is made between "default scale" and
"document scale".

Draw saves scales (for dimensions) on a per document basis as when re-oppened
the scale initially used for that document is used independently of my
currently set default values (a good feature). The problem is not the
behaviour, but the interface which lets me change the "options" for scale. This
means that if I want to change the scale used for the current document, I must
change the scale on the "options" dialog, and re-save the document. The problem
with this approach is that I have also effectively changed the default scale
for new documents (not necessarily an intended behaviour on the user's part).  



Steps to Reproduce:
1 Open an existing draw document with a set scale
2.Change the scale in option and save the document
3.Create a new draw document

Actual Results:
Creating a new document uses the new scale

Expected Results:
In this specific scenario the intended result was to change the scale of only
the opened document.


Reproducible: Always


User Profile Reset: No

Additional Info:
More appropriately, the scale in the "options" dialog should be reworded as
"default scale", and only affect the scale for new documents. A new "document
scale" property should be accessible (maybe through the "format page"
interface) to change the scale of the current document separately form the
"default scale".

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

[Bug 87078] Cross-reference dialogue in Sidebar

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=87078

RGB  changed:

   What|Removed |Added

 CC||rgb.m...@gmail.com

--- Comment #6 from RGB  ---
(In reply to Heiko Tietze from comment #2)
> [...] But before we start with a new UI wouldn't it make sense
> to integrate the function into the navigator? For instance you right click
> the headings entry that should be inserted and below the current options
> (which should be removed by the way since none of them is not context
> sensitive) would offer 'Insert cross-reference >' with 'Page', 'Chapter',
> 'Reference' etc. below.
> 
> Would that work? [...]

Bug 36310 suggests a new "drag & drop mode" from the navigator to insert
cross-references.

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

[Bug 158589] Add option to save Font Replacement Table

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158589

m.a.riosv  changed:

   What|Removed |Added

   Severity|normal  |enhancement

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

[Bug 158587] Improve column/row highlighting in Calc

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158587

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #4 from m.a.riosv  ---
I'm with Ady

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

[Bug 158584] Problem "Save As" from LibreOffice Writer to fileformat: "Word 2003 XML (.xml)" - width of table(s) decreases to 2%

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158584

m.a.riosv  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 CC||miguelangelrv@libreoffice.o
   ||rg
 Ever confirmed|0   |1

--- Comment #2 from m.a.riosv  ---
Reproducible
Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 0ddd9f7e055a0c1ecb120de3e40c3fdb8373e9dc
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded

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

[Bug 158581] file>properties>statistics>lines expand the line field

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158581

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #1 from m.a.riosv  ---
Please paste here the information on Menu/Help/About LibreOffice (There is an
icon to copy)

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

[Bug 158589] New: Add option to save Font Replacement Table

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158589

Bug ID: 158589
   Summary: Add option to save Font Replacement Table
   Product: LibreOffice
   Version: 7.6.4.1 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: j22...@gmail.com

Description:
Some users spend quite some time creating a Font Replacement Table to avoid
proprietary fonts. It would be nice to offer them the option to save the table
so they can retrieve it eg. in case of a fresh install.

Steps to Reproduce:
1. Options -> LibreOffice -> Fonts
2. Populate the Replacement Table
3. Install a fresh copy of LO


Actual Results:
You have to re-populate the Replacement Table

Expected Results:
There is a button 'Load replacement table' that populates the table.
Note I am not suggesting that the fonts have to be saved (this is obviously out
of the scope of LO), but only the replacement table. 
If you load the table and there is a font that is not installed (either in the
'Font' or 'Replace with' columns) then it could be shown in italics following
the current behavior of LO when you open a document that is supposed to be in a
font that you have not installed. Then the user can know that entry in the
Replacement Table is not going to make any difference because one or both of
those fonts need to be installed first.


Reproducible: Always


User Profile Reset: No

Additional Info:
This is an example of a very useful and rather long replacement table:

https://blog.documentfoundation.org/blog/2020/09/08/libreoffice-tt-replacing-microsoft-fonts/

It must be quite tedious to populate it one by one.

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

[Bug 158588] ODT bloats in file size by factor 4 by saving without changes, font embedding options based on two checkboxes should be redesigned

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158588

--- Comment #4 from OfficeUser  ---
I assume that all LibreOffice applications are affected by these issues. But I
only tested Writer.

Please also have a look at:
https://www.reddit.com/r/libreoffice/comments/136b8ni/fonts_embedding_what_those_options_actually_do/

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

[Bug 158588] ODT bloats in file size by factor 4 by saving without changes, font embedding options based on two checkboxes should be redesigned

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158588

OfficeUser  changed:

   What|Removed |Added

Summary|ODT bloats in file size by  |ODT bloats in file size by
   |factor 4 by saving without  |factor 4 by saving without
   |changes |changes, font embedding
   ||options based on two
   ||checkboxes should be
   ||redesigned

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

[Bug 158588] ODT bloats in file size by factor 4 by saving without changes

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158588

--- Comment #3 from OfficeUser  ---
In addition I found:

There are two checkboxed to set which fonts to embedd.

It looks like "Only embed used fonts" seems to have no effect stand-alone. It
produces the same file size as if there is non of these two checkboxes
checkedd.

This is why I ask to replace these two checkboxes by three three radio buttons.
That would lead to a clear user experience.

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

[Bug 96886] Allow to change mouse pointer into a "laser pointer" during slide show

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=96886

--- Comment #11 from j22...@gmail.com ---
Created attachment 191305
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191305=edit
This is how it would work

Note: if you have VLC you may see an empty video. Try disabling 'hardware
decoding' or use another video player.

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

[Bug 96886] Allow to change mouse pointer into a "laser pointer" during slide show

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=96886

--- Comment #10 from j22...@gmail.com ---
I add my comments here to have everything in one place. Bonus track: I show it
on a video.


Description:
It would be great if there was an option to select a "fading pen" or "laser
pointer" (not sure what the right name would be). This is simply a pen that
fades in some seconds, thus making your remark transient (and therefore not
ruining your slide if you still need to show it a bit more time).

Steps to Reproduce:
If you want to highlight/remark on something while showing a slide (maybe
replying to a question about something you did not stress in the presentation),
you have the option to mark it using the 'mouse as pen' option. You can also
use this tool while presenting for the first time, depending on your style and
choice.
However, everything that you do on the slide ends up kind of messing up the
visuals of that particular slide.

Actual Results:
At that point, you have to right-click and select "Erase all ink on slide".

There are two problems with this:
1. It is a little bit of an interruption to the flow of the talk, and 
2. you either wait until you have a lot of 'ink' on the slide and then erase
all of it, or you have to 'write and erase' many times.

Expected Results:
Both problems would be avoided if the ink disappeared by itself. This is, the
ink stays only a few seconds, long enough to be seen by the audience (and thus,
highlight your point), but at the same time it doesn't matter how much you
scribble, your slide will eventually be clean again.


Reproducible: Always


User Profile Reset: No

Additional Info:
I shamelessly took this idea from another program: a neat online whiteboard
application called ExcaliDraw (www.excalidraw.com). In that application, you
can select something called 'laser pointer' (which I think is a good name!)
which will draw a line that fades out after 2-3 seconds (and it does so very
elegantly following the same trajectory used by the pointer). You can see how
it works in the attached video. It is open source and we should give them
credit.

I think it would be a very nice addition to Impress.
Thanks for all your work and let's continue improving LO!!


Note: if you have VLC you may see an empty video. Try disabling 'hardware
decoding' or use another video player.

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

[Bug 158588] ODT bloats in file size by factor 4 by saving without changes

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158588

--- Comment #2 from OfficeUser  ---
Created attachment 191304
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191304=edit
embedded fonts.png

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

[Bug 158588] ODT bloats in file size by factor 4 by saving without changes

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158588

--- Comment #1 from OfficeUser  ---
Created attachment 191303
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191303=edit
File new.odt

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

[Bug 158588] New: ODT bloats in file size by factor 4 by saving without changes

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158588

Bug ID: 158588
   Summary: ODT bloats in file size by factor 4 by saving without
changes
   Product: LibreOffice
   Version: 7.6.2.1 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: framework
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: norbert.n...@gmx.de

Created attachment 191302
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191302=edit
File old.dt

I have a strange finding. After saving a odt from 2021 ("File old.odt") without
any changes in LibreOffice 7.6.2.1 the file size multiplicates ("File
new.odt").

"File old.odt": 993,2 kB
"File new.odt": 4.1 MB

After investigating the extracted content of the odt/zip files I found the
reason:
By saving without any changes in recent LibreOffice build  addiontinal fonts
have been embedded into the odt file. Why? (see "embedded fonts.png")



Version: 7.6.2.1 (X86_64) / LibreOffice Community
Build ID: 60(Build:1)
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Ubuntu package version: 4:7.6.2~rc1-0ubuntu0.18.04.1~lo1
Calc: threaded

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

[Bug 158578] Some PowerPoint files require extremely long loading times

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158578

--- Comment #5 from m.a.riosv  ---
I can't understand how it works in safe mode and not with a reset profile.

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

[Bug 158523] Whole pages of Comments are not PRINTING or exported to PDF in margins

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158523

--- Comment #3 from tim  ---
The attached file did not fix the problem. There are a couple of issues with
that file. If you look carefully, you will find that the file has 61 pages, but
the last page says it is page 64. So the conversion to PDF left the blank pages
out. Also, the original file had only 58 pages, including blank pages, so the
ODT file did not export properly. It looks like it changed all of the fonts.
(Note: I sent the ODT file with embedded fonts. It should have opened properly
with 58 pages, but I might have done something wrong there.)

None-the-less, you can see the problem in the file you created. You will see on
page 59 (labeled page 62) that there are no comments in the margin. There
should be three comments there. This page corresponds with the original ODT
file page 56, which has three comments. So, despite the fact that the page
numbers and fonts are mess up, you can see that the problem still exists.

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

[Bug 158585] add 'laser pointer' to presentations

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158585

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||stephane.guillou@libreoffic
   ||e.org
 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Stéphane Guillou (stragu) 
 ---
Thanks for the suggestion. This is already tracked in bug 96886, so marking as
duplicate.
Please feel free to comment about the "trailing" aspect there if you feel it is
needed.

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

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

[Bug 96886] Allow to change mouse pointer into a "laser pointer" during slide show

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=96886

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||j22...@gmail.com

--- Comment #9 from Stéphane Guillou (stragu) 
 ---
*** Bug 158585 has been marked as a duplicate of this bug. ***

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

[Bug 89673] EDITING - can't use the regular context menu on misspelled words

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=89673

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||kaese...@gmail.com

--- Comment #11 from Stéphane Guillou (stragu) 
 ---
*** Bug 158567 has been marked as a duplicate of this bug. ***

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

[Bug 158567] Right-click on misspelled words only offers spelling-related functions, no formatting options

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158567

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE
 CC||stephane.guillou@libreoffic
   ||e.org

--- Comment #1 from Stéphane Guillou (stragu) 
 ---
Thanks for the report. I agree this could be improved, it's very common to have
both the usual actions + the spellcheck suggestions in the one context menu
nowadays, for example in web browsers.
Issue is already tracked in bug 89673 so marking as duplicate.

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

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

[Bug 156379] Writer file properties: word count lacks space to display 4 and more digits

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156379

Rafael Lima  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|libreoffice-b...@lists.free |rafael.palma.l...@gmail.com
   |desktop.org |

--- Comment #6 from Rafael Lima  ---
Proposed patch here:
https://gerrit.libreoffice.org/c/core/+/160367

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

[Bug 158587] Improve column/row highlighting in Calc

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158587

--- Comment #3 from ady  ---
FWIW, the additional row+column highlighting is supposed to help in easier
location of the cell that has the current focus.

Expanding the extra row+column highlighting to cover every selected range might
be counterproductive regarding the original goal of the feature.

IMO, the new optional row+column highlighting should be relevant for cell's
_focus_, not for range _selection_, which already has its own highlight, both
on the cell/range itself and on the row/column headers.

In the "simpler range" case, the "home" cell of the selection has its
row+column highlighted, so the range is easily seen, not to mention it is all
already highlighted by itself and at the row/column headers.

What would be expected to be highlighted if there are several non-contiguous
ranges selected? IMO, that would not be useful.

BTW, as an additional help for users, the traditional Name Box shows the cell
or range (either focused or selected).

I'm not convinced that expanding the row+column highlighting to the entire
selection would be an improvement; I'm worried it would be counterproductive.

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

[Bug 158541] simplify start-center document selection

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158541

--- Comment #15 from V Stuart Foote  ---
(In reply to Heiko Tietze from comment #11)
> More precisely: select per click (or arrow keys), open with double-click (or
> enter). And hover just shows the usual tooltip if the cursor rests over the
> control. And shows the pin icons to give a hint on the possibility.
> 
> Any argument against this solution?
(In reply to Mike Kaganski from comment #13)
> (In reply to Buovjaga from comment #12)
> 
> This workflow would become much more relevant, if (when) we add options to
> the thumbnails: e.g., allow to use the same filter as last time (or redo the
> type detection, as it happens now). Double-click is not the "workflow
> complication" problem needing much attention - double-clicking is used
> ~universally.
> 
> +1 from me.

OK so meaning, we move SC to single-click selection and double-click open? On
mouse over still only exposes the tooltip, but does it continue to show the 75%
transparent selection color?

If so, +1 for implementing a on-mouse-over / single click / double click
selection sequence cross platform for SC.

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

[Bug 158587] Improve column/row highlighting in Calc

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158587

--- Comment #2 from Rafael Lima  ---
I tend to agree with this. The first time I tested the feature, I was expecting
that selecting a range would highlight all rows and columns in the selection.

The resulting behavior is also weird when cells are merged and when the user
select multiple ranges.

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

[Bug 158587] Improve column/row highlighting in Calc

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158587

--- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> ---
Created attachment 191301
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191301=edit
Image with problem

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

[Bug 107977] [META] Calc feature enhancements

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107977

Roman Kuznetsov <79045_79...@mail.ru> changed:

   What|Removed |Added

 Depends on||158587


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158587
[Bug 158587] Improve column/row highlighting in Calc
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158587] Improve column/row highlighting in Calc

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158587

Roman Kuznetsov <79045_79...@mail.ru> changed:

   What|Removed |Added

 CC||79045_79...@mail.ru
   Keywords||needsUXEval
 Blocks||107977
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=33
   ||201
   Severity|normal  |enhancement


Referenced Bugs:

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

[Bug 158587] New: Improve column/row highlighting in Calc

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158587

Bug ID: 158587
   Summary: Improve column/row highlighting in Calc
   Product: LibreOffice
   Version: 24.2.0.0 alpha1+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: 79045_79...@mail.ru

Description:
Improve column/row highlighting in Calc

After Sahil's patches for bug 33201 we have the opportunity to highlight
current rows/columns by cursor placement (use Tools -> Options -> LibreOffice
Calc -> View -> Column/Row highlighting option for enabling). It works great if
you select only one cell.

But if you try to select cell range then that feature doesn't work as I
expected.
Look at the image in attachment -> I selected some cell range but Calc
highlighted only one row and only one column instead all rows/all columns for
cell range.

I suggest to change current behavior to more right.

Steps to Reproduce:
-

Actual Results:
Columns/rows highlighting works only for one selected cell even if you selected
some cell range

Expected Results:
Columns/rows highlighting works for any amount of selected cells


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: a9ad36ae46ff76c0d59b0d170314fdd3a9ee5d35
CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win
Locale: ru-RU (ru_RU); UI: en-US
Calc: CL threaded

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

[Bug 158586] FILEOPEN RTF: missing page break

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158586

--- Comment #1 from Justin L  ---
I identified, using 7.6 bibisect,
commit f24ad883b15a8112d7dfeb4de14afaf67da30a47
Author: Michael Stahl on Thu Nov 9 19:54:19 2023 +0100
tdf#153178 writerfilter: do not create text frame spuriously

Reviewed-on: https://gerrit.libreoffice.org/c/core/+/159228

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

[Bug 113340] [META] RTF (text) paragraph-related issues

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113340

Justin L  changed:

   What|Removed |Added

 Depends on||158586


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158586
[Bug 158586] FILEOPEN RTF: missing page break
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 152885] FILEOPEN RTF Page break and section break result in extra paragraph

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152885

Justin L  changed:

   What|Removed |Added

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

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

[Bug 158586] New: FILEOPEN RTF: missing page break

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158586

Bug ID: 158586
   Summary: FILEOPEN RTF: missing page break
   Product: LibreOffice
   Version: 7.6.4.1 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Keywords: bibisected, bisected, filter:rtf, regression
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: jl...@mail.com
CC: jl...@mail.com, michael.st...@allotropia.de
Blocks: 113340

A backport to LO 7.6.4 caused an RTF file to lose its first page break.

Steps to reproduce.
-open attachment 191090 (A011-min-cleaned.rtf)
-it should be two pages long - with the first page being empty.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=113340
[Bug 113340] [META] RTF (text) paragraph-related issues
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158556] DOCX Document That Opens/Loads Extremely Slowly

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158556

Timur  changed:

   What|Removed |Added

   Keywords||bibisected, bisected,
   ||regression
 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1
 CC||mikekagan...@hotmail.com
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=13
   ||3560

--- Comment #3 from Timur  ---
It is always good idea to test previous versions. 
File loaded in 80 seconds for me, until the regression commit from bug 133560,
already in 7.5.6, 7.6.0 beta and 24.2 master:
source sha:ba07bfcda6b9f256f636708e52283be0f3a90c8a

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

[Bug 158584] Problem "Save As" from LibreOffice Writer to fileformat: "Word 2003 XML (.xml)" - width of table(s) decreases to 2%

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158584

--- Comment #1 from Alex  ---
Created attachment 191300
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191300=edit
width of table(s) in "Word 2003 XML (.xml)" file decreases to 2%

 width of table(s) in "Word 2003 XML (.xml)" file decreases to 2%
Please, see on YouTube - https://www.youtube.com/watch?v=vQoBuug6guM

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

[Bug 158585] add 'laser pointer' to presentations

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158585

--- Comment #1 from j22...@gmail.com ---
Created attachment 191299
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191299=edit
This is how it would look like

Note: if you have VLC you may see an empty video. Try disabling 'hardware
decoding' or use another video player.

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

[Bug 158585] New: add 'laser pointer' to presentations

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158585

Bug ID: 158585
   Summary: add 'laser pointer' to presentations
   Product: LibreOffice
   Version: 7.6.3.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Impress
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: j22...@gmail.com

Description:
It would be great if there was an option to select a "fading pen" or "laser
pointer" (not sure what the right name would be). This is simply a pen that
fades in some seconds, thus making your remark transient (and therefore not
ruining your slide if you still need to show it a bit more time).

Steps to Reproduce:
If you want to highlight/remark on something while showing a slide (maybe
replying to a question about something you did not stress in the presentation),
you have the option to mark it using the 'mouse as pen' option. You can also
use this tool while presenting for the first time, depending on your style and
choice.
However, everything that you do on the slide ends up kind of messing up the
visuals of that particular slide.

Actual Results:
At that point, you have to right-click and select "Erase all ink on slide".

There are two problems with this:
1. It is a little bit of an interruption to the flow of the talk, and 
2. you either wait until you have a lot of 'ink' on the slide and then erase
all of it, or you have to 'write and erase' many times.

Expected Results:
Both problems would be avoided if the ink disappeared by itself. This is, the
ink stays only a few seconds, long enough to be seen by the audience (and thus,
highlight your point), but at the same time it doesn't matter how much you
scribble, your slide will eventually be clean again.


Reproducible: Always


User Profile Reset: No

Additional Info:
I shamelessly took this idea from another program: a neat online whiteboard
application called ExcaliDraw (www.excalidraw.com). In that application, you
can select something called 'laser pointer' (which I think is a good name!)
which will draw a line that fades out after 2-3 seconds (and it does so very
elegantly following the same trajectory used by the pointer). You can see how
it works in the attached video. It is open source and we should give them
credit.

I think it would be a very nice addition to Impress.
Thanks for all your work and let's continue improving LO!!


Note: if you have VLC you may see an empty video. Try disabling 'hardware
decoding' or use another video player.

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

[Bug 158476] Start Center shows black background behind icons after launching LibreOffice with OS dark-mode and LO appearance light (macOS)

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158476

--- Comment #4 from Telesto  ---
(In reply to steve from comment #2)
Settings > View > Appearance > Mode: Dark
Settings > Application Colors > Custom Colors > Scheme: Untouched (default)
OS-mode > Control Center > click Display > Dark Mode.

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

[Bug 158058] FILEOPEN RTF Next page break with different orientation imported incorrectly

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158058

Justin L  changed:

   What|Removed |Added

Version|24.2.0.0 alpha0+|Inherited From OOo
 CC||jl...@mail.com

--- Comment #4 from Justin L  ---
It was only 3 pages long in OOo 3.3 (but with page 3/page 4 combined).

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

[Bug 158584] New: Problem "Save As" from LibreOffice Writer to fileformat: "Word 2003 XML (.xml)" - width of table(s) decreases to 2%

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158584

Bug ID: 158584
   Summary: Problem "Save As" from LibreOffice Writer to
fileformat: "Word 2003 XML (.xml)" - width of table(s)
decreases to 2%
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rabota2020@gmail.com

Description:
When you working in LibreOffice Writer and try to "Save As" in a special format
"Word 2003 XML (.xml)" your text with table(s). Than, when You try to open just
saved "Word 2003 XML (.xml)" file, that width of table(s) is damaged (decreases
to 2%).
Please, see on YouTube - https://www.youtube.com/watch?v=vQoBuug6guM

Steps to Reproduce:
1 step. Create any text document in LibreOffice.
2 step. Insert a table of any width and with any number of columns (even
without text)
3 step. Save As to fileformat: "Word 2003 XML (.xml)"
4 step. Open just saved file (.xml)
5 step. You can see that width of table decreases to 2% (broken).

Actual Results:
Width of table(s) decreases to 2% (broken) 

Expected Results:
the table(s) must be saved correctly


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.6.1.2 (X86_64) / LibreOffice Community
Build ID: f5defcebd022c5bc36bbb79be232cb6926d8f674
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: ru-RU (ru_RU.UTF-8); UI: ru-RU
Calc: threaded

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

[Bug 158058] FILEOPEN RTF Next page break with different orientation imported incorrectly

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158058

Justin L  changed:

   What|Removed |Added

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

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

[Bug 113340] [META] RTF (text) paragraph-related issues

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113340

Justin L  changed:

   What|Removed |Added

 Depends on||158583


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158583
[Bug 158583] FILEOPEN RTF: break splits paragraph across two pages
-- 
You are receiving this mail because:
You are the assignee for the bug.

  1   2   3   >