[Libreoffice-bugs] [Bug 156930] LibreOffice - Calc - Basic - Stop Statement

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156930

Werner Tietz  changed:

   What|Removed |Added

 Resolution|--- |NOTABUG
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Werner Tietz  ---
I never saw this »stop« statement in practice, but IMHO it does exactly what
the helppage says and what I would expect …

NOTABUG!

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

[Libreoffice-ux-advise] [Bug 149611] Allow the page to adhere to the theme of the system.

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149611

Buovjaga  changed:

   What|Removed |Added

 OS|All |Linux (All)

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

[Libreoffice-bugs] [Bug 149611] Allow the page to adhere to the theme of the system.

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149611

Buovjaga  changed:

   What|Removed |Added

 OS|All |Linux (All)

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

[Libreoffice-bugs] [Bug 156894] kf5/qt6: Dark system themes don't automatically enable corresponding dark icon themes

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156894

Jeff Fortin Tam  changed:

   What|Removed |Added

 Depends on||148764


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=148764
[Bug 148764] Icon themes need to include metadata and different variants in one
package
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 127138] gtk3/gtk4: Dark system themes don't automatically enable corresponding dark icon themes

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=127138

Jeff Fortin Tam  changed:

   What|Removed |Added

 Depends on||148764


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=148764
[Bug 148764] Icon themes need to include metadata and different variants in one
package
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148764] Icon themes need to include metadata and different variants in one package

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148764

Jeff Fortin Tam  changed:

   What|Removed |Added

 Blocks||156894, 127138


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=127138
[Bug 127138] gtk3/gtk4: Dark system themes don't automatically enable
corresponding dark icon themes
https://bugs.documentfoundation.org/show_bug.cgi?id=156894
[Bug 156894] kf5/qt6: Dark system themes don't automatically enable
corresponding dark icon themes
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 156750] Add "Sort" as a protection property to allow sorting on protected/locked sheet

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156750

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 156748] CALC adopting Excel border line weights has corrupted existing sheets especially with Conditional Formatting

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156748

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 156584] Embedded database registered url rule

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156584

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 152572] Writer crashes when scrolling a large document with mouse wheel

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152572

--- Comment #10 from QA Administrators  ---
Dear Ondrej Neff,

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.

[Libreoffice-bugs] [Bug 151807] Whenever I open a file with LibreOffice a Windows security message immediately pops up

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151807

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

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.

[Libreoffice-bugs] [Bug 128581] [Meta] Panel docking

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128581
Bug 128581 depends on bug 151504, which changed state.

Bug 151504 Summary: Navigator dialog docked above sidebar increases size while 
editing document
https://bugs.documentfoundation.org/show_bug.cgi?id=151504

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 151504] Navigator dialog docked above sidebar increases size while editing document

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151504

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

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.

[Libreoffice-bugs] [Bug 151150] very long time to execute a macro when libreoffice calc file is started after start of the system (7mn) since V7

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151150

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 151150] very long time to execute a macro when libreoffice calc file is started after start of the system (7mn) since V7

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151150

--- Comment #13 from QA Administrators  ---
Dear Jacques Bernède,

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.

[Libreoffice-bugs] [Bug 150563] Table jumps between pages when moving cursor

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150563

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 150533] Font and font size fields overwrite field rather than clear first creating illegible gibberish

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150533

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 150563] Table jumps between pages when moving cursor

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150563

--- Comment #5 from QA Administrators  ---
Dear Ian McInerney,

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.

[Libreoffice-bugs] [Bug 150533] Font and font size fields overwrite field rather than clear first creating illegible gibberish

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150533

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

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.

[Libreoffice-bugs] [Bug 150456] Using Function/Button - Clone Formation - does not hit a Cell accurate in a spread sheet

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150456

--- Comment #4 from QA Administrators  ---
Dear Dr. Wilfried Benner,

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.

[Libreoffice-bugs] [Bug 150456] Using Function/Button - Clone Formation - does not hit a Cell accurate in a spread sheet

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150456

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 140657] LibreOffice Impress cannot page down or up, affects Zoom windows

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=140657

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 140657] LibreOffice Impress cannot page down or up, affects Zoom windows

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=140657

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

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.

[Libreoffice-bugs] [Bug 153861] Crash in: _chkstk

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153861

--- Comment #2 from QA Administrators  ---
Dear Michael Dewsbury,

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.

[Libreoffice-bugs] [Bug 151854] External Links Can't Import Online Table; Have to Download the HTML First Before Importing

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151854

--- Comment #5 from QA Administrators  ---
Dear Stanislaus J. Pinasthika,

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.

[Libreoffice-bugs] [Bug 150646] Unable to change font color in spreadsheet cells

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150646

--- Comment #5 from QA Administrators  ---
Dear John Mildfelt,

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.

[Libreoffice-bugs] [Bug 151737] Reports recovery of file every time system is shut down

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151737

--- Comment #10 from QA Administrators  ---
Dear Scott franco,

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.

[Libreoffice-bugs] [Bug 149427] Backwards incompatibility: table ids parsed from links to external HTML files

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149427

--- Comment #3 from QA Administrators  ---
Dear Dan Dascalescu,

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.

[Libreoffice-bugs] [Bug 94075] If you select an image direct after caption was selected, "keep aspect" on mouse-resizing is broken

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=94075

--- Comment #9 from QA Administrators  ---
Dear Stefan,

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.

[Libreoffice-bugs] [Bug 139369] UI Inconsistent screen refresh for conditional Data Bar formatting depending on sort criteria and data values

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139369

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

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.

[Libreoffice-bugs] [Bug 90871] Drop-down and pop-up menus can open down behind Windows taskbar [Windows, multimonitor]

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=90871

--- Comment #36 from QA Administrators  ---
Dear Gordo,

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.

[Libreoffice-bugs] [Bug 134203] Layout loop for single cell table splitting across 23 pages with tables within; SwFrame::setRootFrame -> SwFrame::UnionFrame

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=134203

--- Comment #15 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.

[Libreoffice-bugs] [Bug 126010] Very blurry image in odt export from google docs depending on zoom level

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=126010

--- Comment #15 from QA Administrators  ---
Dear carlosjosepita,

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.

[Libreoffice-bugs] [Bug 156931] JPEG XL support

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156931

Telesto  changed:

   What|Removed |Added

 CC||heiko.tietze@documentfounda
   ||tion.org
  Component|Base|filters and storage
   Keywords||needsDevEval

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

[Libreoffice-bugs] [Bug 122096] FILEOPEN XLSX Conditional formatting with cell contains condition is imported with quotation marks

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=122096

--- Comment #10 from ady  ---
As of a recent LO Dev 24.2, IMHO the "Contains" conditional format is not
working as expected, whether it is imported from xlsx, or in a new (ods) file.

IMHO, the "Contains" type of condition should not require to use quotation
marks in order to return TRUE for the condition on non-numeric values.
(However, I am not sure whether changing this might have compatibility problems
with older versions.)

A condition such as 'Contains 1' should be evaluated independently of whether
the value in the cell is text or number. If users want to restrict this to a
specific type of value (e.g. either numeric values only, or text values only),
they should add an additional condition.

Currently, we have a somewhat-confusing situation. For example, starting from
attachment 147527 (from comment 1), if the condition is modified (menu Format >
Conditional > Manage > Edit) from:

'Contains "1,23"'

to:

'Contains 1,23' (without the quotation marks around the value)

it results in all empty cells being TRUE for the condition; this result is not
intuitive, or even not understandable/logical at all (at least for users).

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

[Libreoffice-bugs] [Bug 156943] Comments on an indented paragraph get indented as well

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156943

--- Comment #3 from Nadie Nada Nunca  ---
Created attachment 189169
  --> https://bugs.documentfoundation.org/attachment.cgi?id=189169=edit
Sample DOCX

I forgot to clarify that I'm working with a DOCX file.

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

[Libreoffice-bugs] [Bug 156943] Comments on an indented paragraph get indented as well

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156943

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #2 from m.a.riosv  ---
Please attach a sample file.

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

[Libreoffice-bugs] [Bug 156941] By editing exist PDF file in LibreOffice Draw are all 'r' replaced by 'n'

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156941

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #1 from m.a.riosv  ---
Please can you attach a sample PDF file to test?

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

[Libreoffice-bugs] [Bug 156938] Recovery process reverts to previous version

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156938

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #1 from m.a.riosv  ---
How do you have set up:
Menu/Tools/Options/Load/Save

If backup option is enabled, then recover is for the version at opening the
file.

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

[Libreoffice-bugs] [Bug 156936] Cannot overlay text over a .jpg in Writer

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156936

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #1 from m.a.riosv  ---
Please attach a sample file.

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

[Libreoffice-bugs] [Bug 156934] After update to 7.6 extensions are not listed anymore

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156934

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #3 from m.a.riosv  ---
I have no problem with
Version: 7.6.1.1 (X86_64) / LibreOffice Community
Build ID: c7cda394c5de06de37d8109c310df89a4d4c3a98
CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: default; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL threaded

Please test in safe mode, Menu/Help/Restart in Safe Mode

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

[Libreoffice-bugs] [Bug 156784] LO freezes if delete the first column on the table and the TC are hidden, pressing Ctrl+A

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156784

--- Comment #4 from László Németh  ---
@Julien: thanks for your feedback!

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

[Libreoffice-bugs] [Bug 103100] [META] Writer table bugs

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103100
Bug 103100 depends on bug 156784, which changed state.

Bug 156784 Summary: LO freezes if delete the first column on the table and the 
TC are hidden, pressing Ctrl+A
https://bugs.documentfoundation.org/show_bug.cgi?id=156784

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 156784] LO freezes if delete the first column on the table and the TC are hidden, pressing Ctrl+A

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156784

László Németh  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||nem...@numbertext.org
 Status|NEW |RESOLVED

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

[Libreoffice-bugs] [Bug 156784] LO freezes if delete the first column on the table and the TC are hidden, pressing Ctrl+A

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156784

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:24.2.0

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

[Libreoffice-commits] core.git: sw/qa sw/source

2023-08-26 Thread László Németh (via logerrit)
 sw/qa/uitest/writer_tests7/tdf156784.py |   38 
 sw/source/core/crsr/crsrsh.cxx  |9 +++
 sw/source/core/frmedt/fetab.cxx |3 +-
 3 files changed, 49 insertions(+), 1 deletion(-)

New commits:
commit e16e84c44fc7517529c8a183fbd8f97c0c3e380e
Author: László Németh 
AuthorDate: Thu Aug 24 16:27:16 2023 +0200
Commit: László Németh 
CommitDate: Sun Aug 27 01:20:27 2023 +0200

tdf#156784 sw tracked table column: fix crash at Select All

Section starting table with hidden deleted first column
freezed at Select All, resulting crash because of infinite
recursion during waiting frame creation of a hidden cell
without frame in Hide Changes mode.

Regression from commit d1004cdd6a445ae73673b0ca360ae034b0ec09f2
"tdf#150673 sw offapi: add change tracking of table column deletion".

Change-Id: I15d9fa0138261d7a95c6e34a8d07fb2e001d0c7d
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/156056
Tested-by: Jenkins
Reviewed-by: László Németh 

diff --git a/sw/qa/uitest/writer_tests7/tdf156784.py 
b/sw/qa/uitest/writer_tests7/tdf156784.py
new file mode 100644
index ..5cac8fc628db
--- /dev/null
+++ b/sw/qa/uitest/writer_tests7/tdf156784.py
@@ -0,0 +1,38 @@
+# -*- tab-width: 4; indent-tabs-mode: nil; py-indent-offset: 4 -*-
+#
+# This file is part of the LibreOffice project.
+#
+# This Source Code Form is subject to the terms of the Mozilla Public
+# License, v. 2.0. If a copy of the MPL was not distributed with this
+# file, You can obtain one at http://mozilla.org/MPL/2.0/.
+#
+from uitest.framework import UITestCase
+from uitest.uihelper.common import get_url_for_data_file
+
+# Bug 156784 - crash fix: Select All in section starting table with hidden 
first column
+
+class tdf156784(UITestCase):
+def test_tdf156784(self):
+with 
self.ui_test.load_file(get_url_for_data_file("TC-table-del-add.docx")) as 
self.document:
+
+xToolkit = 
self.xContext.ServiceManager.createInstance('com.sun.star.awt.Toolkit')
+
+# accept all tracked changes
+self.xUITest.executeCommand(".uno:AcceptAllTrackedChanges")
+
+# delete first column
+self.xUITest.executeCommand(".uno:DeleteColumns")
+
+# hide changes
+self.xUITest.executeCommand(".uno:ShowTrackedChanges")
+
+# select cell content
+self.xUITest.executeCommand(".uno:SelectAll")
+
+# This resulted crashing (select section starting table with 
hidden first column)
+self.xUITest.executeCommand(".uno:SelectAll")
+
+# show changes
+self.xUITest.executeCommand(".uno:ShowTrackedChanges")
+
+# vim: set shiftwidth=4 softtabstop=4 expandtab:
diff --git a/sw/source/core/crsr/crsrsh.cxx b/sw/source/core/crsr/crsrsh.cxx
index f22e0bc9450a..4d69e2a6d705 100644
--- a/sw/source/core/crsr/crsrsh.cxx
+++ b/sw/source/core/crsr/crsrsh.cxx
@@ -77,6 +77,7 @@
 #include 
 #include 
 #include 
+#include 
 
 using namespace com::sun::star;
 using namespace util;
@@ -2168,6 +2169,14 @@ void SwCursorShell::UpdateCursor( sal_uInt16 eFlags, 
bool bIdleEnd )
 // created, because there used to be a Frame here!
 if ( !pFrame )
 {
+// skip, if it is a hidden deleted cell without frame
+if ( GetLayout()->IsHideRedlines() )
+{
+const SwStartNode* pNd = 
pShellCursor->GetPointNode().FindTableBoxStartNode();
+if ( pNd && pNd->GetTableBox()->GetRedlineType() == 
RedlineType::Delete )
+return;
+}
+
 do
 {
 CalcLayout();
diff --git a/sw/source/core/frmedt/fetab.cxx b/sw/source/core/frmedt/fetab.cxx
index dced56c1f2a0..59b031ce772a 100644
--- a/sw/source/core/frmedt/fetab.cxx
+++ b/sw/source/core/frmedt/fetab.cxx
@@ -1175,7 +1175,8 @@ bool SwFEShell::CanUnProtectCells() const
 {
 SwFrame *pFrame = GetCurrFrame();
 do {
-pFrame = pFrame->GetUpper();
+if ( pFrame )
+pFrame = pFrame->GetUpper();
 } while ( pFrame && !pFrame->IsCellFrame() );
 if( pFrame )
 {


[Libreoffice-bugs] [Bug 156928] Python macro dialog box buttons are always greyed out

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156928

--- Comment #6 from LucasLibre  ---
Just to update from the original post:

Steps to Reproduce:
1. Open Writer
2. Go to Tools > Macros > Organise Macros > Python …

Expected Results:
The Delete and Rename buttons should work in the same way as the Basic,
Beanshell, and Javascript macro dialogs. The Create and Edit buttons should
probably be removed until a Python macro editor is included in LO.

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

[Libreoffice-bugs] [Bug 156928] Python macro dialog box buttons are always greyed out

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156928

LucasLibre  changed:

   What|Removed |Added

 OS|Windows (All)   |All
Version|24.2.0.0 alpha0+ Master |Inherited From OOo

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

[Libreoffice-bugs] [Bug 156928] Python macro dialog box buttons are always greyed out

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156928

LucasLibre  changed:

   What|Removed |Added

Summary|Python macro dialog box |Python macro dialog box
   |buttons are greyed out if   |buttons are always greyed
   |JRE is uninstalled  |out

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

[Libreoffice-bugs] [Bug 153721] Rename "Move Chapter Up/Down" to "Move Heading+Text Up/Down" in Navigator

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153721

--- Comment #34 from Jim Raykowski  ---
Oh WoW! I see I have already responded to your comment #22 question a couple
months ago. Sorry for the noise.

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

[Libreoffice-bugs] [Bug 153721] Rename "Move Chapter Up/Down" to "Move Heading+Text Up/Down" in Navigator

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153721

--- Comment #33 from Jim Raykowski  ---
(In reply to sdc.blanco from comment #22)
> Is there any reason why this feature cannot be active in the other mode of
> Navigator?
> (which would then make the move up/down commands irrelevant in the context
> menu).

Whew! It took me some time to find your comment that I remembered being asked
but forgot where it was asked. Here is a link to a patch that makes chapter
moves possible by drag and drop when the Navigator is in the
all-content-types/categories navigation view mode:
https://gerrit.libreoffice.org/c/core/+/153854

I wonder if the tdf# for the patch should be associated with this bug report
comment #22?

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

[Libreoffice-bugs] [Bug 51510] FILESAVE: Exporting documents with embedded SVG to doc or docx converts the image to low-resolution pixel graphics

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=51510

--- Comment #33 from Regina Henschel  ---
The export uses ShapeExport::WriteGraphicObjectShapePart() in
oox/source/export/shape.cxx.
That calls DrawingML::WriteXGraphicBlip() in oox/source/export/drawingml.cxx
That calls DrawingML::WriteImage()
That calls GraphicExport::writeToStorage()
Inside that method is a switch over aLink.GetType(). In case of an SVG-image
GetType() returns GfxLinkType::NativeSvg. But the switch has no case for that.
Therefore default: is executed.
The default case determines rGraphic.GetType() which is in this case
GraphicType::Bitmap. I don't know, why it is that type and could not find the
place were it was set.

I'm no expert and have found the above with Visual Studio. Nevertheless it
might give you a starting point. My try would be to add a case for SVG.

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

[Libreoffice-bugs] [Bug 149611] Allow the page to adhere to the theme of the system.

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149611

--- Comment #4 from third="Beedell", first="Roke" 
 ---
> https://ask.libreoffice.org/t/how-to-make-writer-page-adhere-to-system-lo-theme/95069/2?u=rokejulianlockhart

No, although it is a significant improvement.

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

[Libreoffice-ux-advise] [Bug 149611] Allow the page to adhere to the theme of the system.

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149611

--- Comment #4 from third="Beedell", first="Roke" 
 ---
> https://ask.libreoffice.org/t/how-to-make-writer-page-adhere-to-system-lo-theme/95069/2?u=rokejulianlockhart

No, although it is a significant improvement.

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

[Libreoffice-bugs] [Bug 156943] Comments on an indented paragraph get indented as well

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156943

--- Comment #1 from Nadie Nada Nunca  ---
Created attachment 189168
  --> https://bugs.documentfoundation.org/attachment.cgi?id=189168=edit
Bad formatting for comment

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

[Libreoffice-bugs] [Bug 156943] New: Comments on an indented paragraph get indented as well

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156943

Bug ID: 156943
   Summary: Comments on an indented paragraph get indented as well
   Product: LibreOffice
   Version: 7.6.0.2 rc
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: nadie.nada.nu...@mail.com

Description:
Writer seems to “borrow” the formatting of the paragraph you are commenting for
the comment itself. This leads to undesirable artifacts like the one in the
attachment.

Steps to Reproduce:
1. Insert a heading with wide left and right margins in the document.
2. Write a comment for that paragraph.

Actual Results:
See attachment.

Expected Results:
The comment should appear just like any other comment.


Reproducible: Always


User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no

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

[Libreoffice-bugs] [Bug 156942] "Fit width to text" shouldn't default to "extend width to fit whole paragraph on a single line"

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156942

Eyal Rozenberg  changed:

   What|Removed |Added

Summary|"Fit width to text" should  |"Fit width to text"
   |be less extreme by default  |shouldn't default to
   ||"extend width to fit whole
   ||paragraph on a single line"

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

[Libreoffice-ux-advise] [Bug 156942] "Fit width to text" shouldn't default to "extend width to fit whole paragraph on a single line"

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156942

Eyal Rozenberg  changed:

   What|Removed |Added

Summary|"Fit width to text" should  |"Fit width to text"
   |be less extreme by default  |shouldn't default to
   ||"extend width to fit whole
   ||paragraph on a single line"

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

[Libreoffice-bugs] [Bug 156942] "Fit width to text" should be less extreme by default

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156942

Eyal Rozenberg  changed:

   What|Removed |Added

 CC||eyalr...@gmx.com,
   ||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||tele...@surfxs.nl
   Keywords||needsUXEval

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

[Libreoffice-bugs] [Bug 156920] [META] Textbox/Drawing Object autofit functionality

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156920

Eyal Rozenberg  changed:

   What|Removed |Added

 Depends on||156942


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=156942
[Bug 156942] "Fit width to text" should be less extreme by default
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 156942] "Fit width to text" should be less extreme by default

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156942

Eyal Rozenberg  changed:

   What|Removed |Added

 Blocks||156920


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=156920
[Bug 156920] [META] Textbox/Drawing Object autofit functionality
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-ux-advise] [Bug 156942] "Fit width to text" should be less extreme by default

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156942

Eyal Rozenberg  changed:

   What|Removed |Added

 Blocks||156920


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=156920
[Bug 156920] [META] Textbox/Drawing Object autofit functionality
-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 156942] "Fit width to text" should be less extreme by default

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156942

Eyal Rozenberg  changed:

   What|Removed |Added

 CC||eyalr...@gmx.com,
   ||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||tele...@surfxs.nl
   Keywords||needsUXEval

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

[Libreoffice-bugs] [Bug 156942] New: "Fit width to text" should be less extreme by default

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156942

Bug ID: 156942
   Summary: "Fit width to text" should be less extreme by default
   Product: LibreOffice
   Version: 7.6.0.0 alpha1+
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Impress
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: eyalr...@gmx.com

The textbox Position and Size dialog, Position and Size tab has a "Fit width to
text" option. What it actually does is increase or decrease the textbox width
so that the widest paragraph fully fits on a _single line_.

While this is a useful feature, there is another way to "fit width", at least
when "Fit height" is disabled, which is: set the width so that the textbox text
fits in exactly the number of lines which fill the textbox horizontally without
exceeding its bounds.

Thus, for example,

*-*
| I like textboxes in |
| Impress & Draw. |
| |
*-*

(with no paragraph breaks inside the textbox) becomes

*-*
| I like  |
| textboxes in|
| Impress & Draw. |
*-*

no change to the height, decrease to the width to fill the vertical space for
the third line.

I claim the fact that this is not the default behavior is a bug. Why? Because:

1. The current behavior is very often undesirable: If you have a long stretch
of text, it will just extend beyond the boundaries of the slide and your
window.
2. By reducing the textbox height to one line's worth, or alternatively,
increasing the margins to only fit one line - one can get the same effect of
the existing behavior with this behavior.

So, if you ask me - we should just switch the behavior. Alternatively, we could
have the "fit width" option have three states: None, fit to single line, fit to
box height (not necessarily with these names).

--- 

Caveat: If this were to come to pass, the semantics of "Fit width" together
with "Fit height" would have to be reconsidered carefully. Although TBH, their
combination is kind of a mess today.

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

[Libreoffice-bugs] [Bug 103030] [META] Navigator sidebar deck and floating window

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103030
Bug 103030 depends on bug 147807, which changed state.

Bug 147807 Summary: Limiting to selected category limits to the category of 
selected item in tree
https://bugs.documentfoundation.org/show_bug.cgi?id=147807

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 147807] Limiting to selected category limits to the category of selected item in tree

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147807

Jim Raykowski  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 135310] [META] Writer outline folding bugs and enhancements

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=135310
Bug 135310 depends on bug 156282, which changed state.

Bug 156282 Summary: Outline Folding Toggle not available for entire Headings 
outline
https://bugs.documentfoundation.org/show_bug.cgi?id=156282

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 156282] Outline Folding Toggle not available for entire Headings outline

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156282

Jim Raykowski  changed:

   What|Removed |Added

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

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

[Libreoffice-ux-advise] [Bug 156940] Inconsistent behavior of "Fit width to text" between an increase and a decrease in width

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156940

--- Comment #1 from Eyal Rozenberg  ---
Created attachment 189167
  --> https://bugs.documentfoundation.org/attachment.cgi?id=189167=edit
Presentation used for the recording in 189166

Super-simple presentation with a textbox which I used for the screen recording.
Result of deleting the main content area in an new empty presentation, adding a
textbox, typing in the text and setting an orange background.

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

[Libreoffice-bugs] [Bug 105948] [META] Undo/Redo bugs and enhancements

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=105948
Bug 105948 depends on bug 81512, which changed state.

Bug 81512 Summary: Undo: Writer fails to restore Table Name
https://bugs.documentfoundation.org/show_bug.cgi?id=81512

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 81512] Undo: Writer fails to restore Table Name

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81512

Jim Raykowski  changed:

   What|Removed |Added

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

--- Comment #10 from Jim Raykowski  ---
See Bug 144673 for details of patch that fixes this bug.

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

[Libreoffice-bugs] [Bug 156940] Inconsistent behavior of "Fit width to text" between an increase and a decrease in width

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156940

--- Comment #1 from Eyal Rozenberg  ---
Created attachment 189167
  --> https://bugs.documentfoundation.org/attachment.cgi?id=189167=edit
Presentation used for the recording in 189166

Super-simple presentation with a textbox which I used for the screen recording.
Result of deleting the main content area in an new empty presentation, adding a
textbox, typing in the text and setting an orange background.

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

[Libreoffice-bugs] [Bug 156941] New: By editing exist PDF file in LibreOffice Draw are all 'r' replaced by 'n'

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156941

Bug ID: 156941
   Summary: By editing exist PDF file in LibreOffice Draw are all
'r' replaced by 'n'
   Product: LibreOffice
   Version: 7.4.7.2 release
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Draw
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: jab...@gmail.com

Description:
When I open any PDF file through Draw, all lower case 'r's are written as lower
case 'n'.

Actual Results:
Opening PDF file to edit and words with 'r' are writed by 'n'. For example
"Print" as "Pnint", "World" as "Wonld" etc.

Expected Results:
I search for and correct wrong words manually.


Reproducible: Always


User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: DrawingDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes

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

[Libreoffice-bugs] [Bug 156920] [META] Textbox/Drawing Object autofit functionality

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156920

Eyal Rozenberg  changed:

   What|Removed |Added

 Depends on||156940


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=156940
[Bug 156940] Inconsistent behavior of "Fit width to text" between an increase
and a decrease in width
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 156940] Inconsistent behavior of "Fit width to text" between an increase and a decrease in width

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156940

Eyal Rozenberg  changed:

   What|Removed |Added

Version|7.6.0.0 alpha1+ |7.6.0.3 release
 Blocks||156920
   Keywords||needsUXEval
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=156920
[Bug 156920] [META] Textbox/Drawing Object autofit functionality
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-ux-advise] [Bug 156940] Inconsistent behavior of "Fit width to text" between an increase and a decrease in width

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156940

Eyal Rozenberg  changed:

   What|Removed |Added

Version|7.6.0.0 alpha1+ |7.6.0.3 release
 Blocks||156920
   Keywords||needsUXEval
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=156920
[Bug 156920] [META] Textbox/Drawing Object autofit functionality
-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-bugs] [Bug 156940] New: Inconsistent behavior of "Fit width to text" between an increase and a decrease in width

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156940

Bug ID: 156940
   Summary: Inconsistent behavior of "Fit width to text" between
an increase and a decrease in width
   Product: LibreOffice
   Version: 7.6.0.0 alpha1+
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Impress
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: eyalr...@gmx.com

Created attachment 189166
  --> https://bugs.documentfoundation.org/attachment.cgi?id=189166=edit
The effect of width-increasing and width-decreasing edits on a textbox

A textbox can be set to "Fit width to text". In that state, when one edits the
textbox and changes the width - e.g. by joining or splitting lines - it stands
to reason that the user see an indication of what the automatically-resized
textbox will look like with the text having been edited.

Well, this happens, but - not consistently. In the attached video, you'll see a
textbox, with an orange color background and two paragraphs of text, being
edited twice: 

* Once decreasing the width by inserting a paragraph break 
* Then again by increasing the width by removing the break (de-selecting the
textbox between these two actions).

With the first action, we note that the grayish frame surrounding the textbox
doesn't change dimensions, nor does the background.

With the second action, the grayish frame is resized - that's the indication of
what the textbox will be like after the edit - while the background retains the
dimensions of the existing, non-resized, box.

The bug is the inconsistency between these two cases.

As for what to do, I like the behavior in the second case better, despite it
being a bit jarring to have some textbox features change and some remain as is,
so I'd like the second case behavior to apply to the first case as well.

Another option is two have all textbox features fit the altered size
immediately (i.e. like neither of the cases).

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

[Libreoffice-commits] core.git: cui/Library_cui.mk cui/qa cui/source cui/uiconfig cui/UIConfig_cui.mk include/svx sd/inc sd/qa sd/source sd/uiconfig

2023-08-26 Thread Tomaž Vajngerl (via logerrit)
 cui/Library_cui.mk |1 
 cui/UIConfig_cui.mk|1 
 cui/qa/uitest/tabpages/themepage.py|   87 -
 cui/source/factory/dlgfact.cxx |5 
 cui/source/inc/themepage.hxx   |   53 ---
 cui/source/tabpages/themepage.cxx  |  176 --
 cui/uiconfig/ui/themetabpage.ui|  557 -
 include/svx/dialogs.hrc|1 
 sd/inc/sdabstdlg.hxx   |2 
 sd/qa/unit/dialogs-test.cxx|2 
 sd/source/ui/dlg/dlgpage.cxx   |9 
 sd/source/ui/dlg/sddlgfact.cxx |4 
 sd/source/ui/dlg/sddlgfact.hxx |2 
 sd/source/ui/func/fupage.cxx   |   29 -
 sd/source/ui/inc/dlgpage.hxx   |2 
 sd/uiconfig/sdraw/ui/drawpagedialog.ui |  181 +-
 16 files changed, 37 insertions(+), 1075 deletions(-)

New commits:
commit f4ed90bcad83ea24644c1cbf077b369ae05f004e
Author: Tomaž Vajngerl 
AuthorDate: Tue Aug 22 08:14:10 2023 +0200
Commit: Tomaž Vajngerl 
CommitDate: Sat Aug 26 23:19:57 2023 +0200

sd: remove theme tab page

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

diff --git a/cui/Library_cui.mk b/cui/Library_cui.mk
index 03a1577ee66b..43d13810d5c1 100644
--- a/cui/Library_cui.mk
+++ b/cui/Library_cui.mk
@@ -229,7 +229,6 @@ $(eval $(call gb_Library_add_exception_objects,cui,\
 cui/source/tabpages/textanim \
 cui/source/tabpages/textattr \
 cui/source/tabpages/TextColumnsPage \
-cui/source/tabpages/themepage \
 cui/source/tabpages/tparea \
 cui/source/tabpages/tpbitmap \
 cui/source/tabpages/tpcolor \
diff --git a/cui/UIConfig_cui.mk b/cui/UIConfig_cui.mk
index 6985163f6922..a863e155dd04 100644
--- a/cui/UIConfig_cui.mk
+++ b/cui/UIConfig_cui.mk
@@ -219,7 +219,6 @@ $(eval $(call gb_UIConfig_add_uifiles,cui,\
cui/uiconfig/ui/textcolumnstabpage \
cui/uiconfig/ui/textdialog \
cui/uiconfig/ui/textflowpage \
-   cui/uiconfig/ui/themetabpage \
cui/uiconfig/ui/thesaurus \
cui/uiconfig/ui/toolbarmodedialog \
cui/uiconfig/ui/transparencytabpage \
diff --git a/cui/qa/uitest/tabpages/themepage.py 
b/cui/qa/uitest/tabpages/themepage.py
deleted file mode 100644
index 0145f0345492..
--- a/cui/qa/uitest/tabpages/themepage.py
+++ /dev/null
@@ -1,87 +0,0 @@
-#
-# This Source Code Form is subject to the terms of the Mozilla Public
-# License, v. 2.0. If a copy of the MPL was not distributed with this
-# file, You can obtain one at http://mozilla.org/MPL/2.0/.
-#
-
-from libreoffice.uno.propertyvalue import convert_property_values_to_dict
-from libreoffice.uno.propertyvalue import mkPropertyValues
-from uitest.framework import UITestCase
-from uitest.uihelper.common import get_state_as_dict
-from uitest.uihelper.common import select_pos
-from uitest.uihelper.common import select_by_text
-
-# Test for cui/source/tabpages/themepage.cxx.
-class Test(UITestCase):
-
-def testThemePage(self):
-# Given an Impress document with a master page that has a theme:
-with self.ui_test.create_doc_in_start_center("impress") as component:
-template = self.xUITest.getTopFocusWindow()
-
self.ui_test.close_dialog_through_button(template.getChild("close"))
-doc = self.xUITest.getTopFocusWindow()
-editWin = doc.getChild("impress_win")
-drawPage = component.getDrawPages().getByIndex(0)
-master = drawPage.MasterPage
-theme = mkPropertyValues({
-"Name": "nameA",
-"ColorSchemeName": "colorSetA",
-"ColorScheme": tuple([
-0x00,  # dk1
-0x00,  # lt1
-0x00,  # dk2
-0x00,  # lt2
-0xff,  # accent1
-0x00,  # accent2
-0x00,  # accent3
-0x00,  # accent4
-0x00,  # accent5
-0x00,  # accent6
-0x00,  # hlink
-0x00,  # folHlink
-])
-})
-master.ThemeUnoRepresentation = theme
-
-# When changing the name of the theme:
-self.xUITest.executeCommand(".uno:SlideMasterPage")
-with self.ui_test.execute_dialog_through_command(".uno:PageSetup") 
as xDialog:
-xTabs = xDialog.getChild("tabcontrol")
-# Select RID_SVXPAGE_THEME.
-select_pos(xTabs, "3")
-themeName = xDialog.getChild("themeName")
-themeName.executeAction("TYPE", 
mkPropertyValues({"KEYCODE":"CTRL+A"}))
-themeName.executeAction("TYPE", 
mkPropertyValues({"KEYCODE":"BACKSPACE"}))
-

[Libreoffice-bugs] [Bug 156922] VIEWING: spreadsheet table in .docx file seems to import fine then numbers shift after mouseclick or PDF export

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156922

m.a.riosv  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |NOTABUG

--- Comment #3 from m.a.riosv  ---
The formula in row 2 is:
=AVERAGE() -> 10 if I3 has 10
that it is not similar to row 3
=AVERAGE()
and different form row 4
=AVERAGE(), this seems should be the right formula.
Writer gets the same values as Word at update.
So there is not a bug.

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

[Libreoffice-ux-advise] [Bug 156939] "Fit height to text" is misleading, only regards growing rather than shrinking

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156939

Eyal Rozenberg  changed:

   What|Removed |Added

   Keywords||needsDevAdvice, needsUXEval
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||tele...@surfxs.nl

--- Comment #1 from Eyal Rozenberg  ---
Seeing this with:

Version: 7.6.0.3 (X86_64) / LibreOffice Community
Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265
CPU threads: 4; OS: Linux 6.4; UI render: default; VCL: gtk3
Locale: en-IL (en_IL); UI: en-US

but it goes way back.

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

[Libreoffice-bugs] [Bug 156939] "Fit height to text" is misleading, only regards growing rather than shrinking

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156939

Eyal Rozenberg  changed:

   What|Removed |Added

   Keywords||needsDevAdvice, needsUXEval
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||tele...@surfxs.nl

--- Comment #1 from Eyal Rozenberg  ---
Seeing this with:

Version: 7.6.0.3 (X86_64) / LibreOffice Community
Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265
CPU threads: 4; OS: Linux 6.4; UI render: default; VCL: gtk3
Locale: en-IL (en_IL); UI: en-US

but it goes way back.

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

[Libreoffice-bugs] [Bug 156918] "Autofit text" is ambiguous + users expect both interpretations on the context menu

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156918

Eyal Rozenberg  changed:

   What|Removed |Added

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

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

[Libreoffice-ux-advise] [Bug 156918] "Autofit text" is ambiguous + users expect both interpretations on the context menu

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156918

Eyal Rozenberg  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 156920] [META] Textbox/Drawing Object autofit functionality

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156920

Eyal Rozenberg  changed:

   What|Removed |Added

 Depends on||156939


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=156939
[Bug 156939] "Fit height to text" is misleading, only regards growing rather
than shrinking
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 156939] "Fit height to text" is misleading, only regards growing rather than shrinking

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156939

Eyal Rozenberg  changed:

   What|Removed |Added

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


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=156920
[Bug 156920] [META] Textbox/Drawing Object autofit functionality
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 156939] New: "Fit height to text" is misleading, only regards growing rather than shrinking

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156939

Bug ID: 156939
   Summary: "Fit height to text" is misleading, only regards
growing rather than shrinking
   Product: LibreOffice
   Version: 7.6.0.0 alpha1+
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Impress
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: eyalr...@gmx.com

The text box Position and Size dialog, in the Position and Size tab, has the
setting "Fit height to text".

When this is checked, the textbox height will only be fit to the text length if
the text length _exceeds_ the original/no-text height of the textbox. If the
text requires less height - the textbox will maintain its original height.

This behavior is _inconsistent_ with the "Fit width to text", which _does_
shrink the textbox horizontally if the text does not fill even one full line.

This bug is not about the functionality, but about the label. While the
functionality remains as it is now - the label should be rephrased to capture
it more exactly and not confuse users.

So, instead of "Fit height to text" it should something like:

* "Stretch height to fit text"
* "Extend height to fit text"
* "Increase height to fit text"
* "Increase height on text overflow"

etc.

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

[Libreoffice-bugs] [Bug 156938] New: Recovery process reverts to previous version

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156938

Bug ID: 156938
   Summary: Recovery process reverts to previous version
   Product: LibreOffice
   Version: 7.5.5.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: amoz.ecker...@gmail.com

Description:
Multiple files open in Writer version 7.5.5.2
Select File --> Close on one file, and Writer shuts down closing all other file
windows.
Start Writer back up and it presents the option to "recover" the files that
closed automatically.  If you hit yes, it doesn't actually recover the file but
reverts to some previous version from more than a day ago causing lost work.

Steps to Reproduce:
1.Have multiple files open
2.Select file --? close one file (Writer shuts down and closes all windows)
3.Start Writer again
4.Select files to recover
5.Get angry when the file is from 2 days ago and you lost work that you
actually had saved.

Actual Results:
The recovered files are not the latest version.  It's like recovery means go
back in time to some previous save point and trash the actual most recent save. 

Expected Results:
I would expect "recovery" to mean: the program shutdown suddenly, so we saved
everything just to make sure you didn't loose anything.  


Reproducible: Sometimes


User Profile Reset: No

Additional Info:
Version: 7.5.5.2 (X86_64) / LibreOffice Community
Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e
CPU threads: 20; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded

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

[Libreoffice-bugs] [Bug 122096] FILEOPEN XLSX Conditional formatting with cell contains condition is imported with quotation marks

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=122096

--- Comment #9 from Michaela  ---
Still repro with:
Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: e46e663cc350d89e4997095466d675b875eb2e04
CPU threads: 12; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win

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

[Libreoffice-bugs] [Bug 156918] "Autofit text" is ambiguous + users expect both interpretations on the context menu

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156918

--- Comment #9 from Eyal Rozenberg  ---
(In reply to V Stuart Foote from comment #8)
> Sorry but that is absolute nonsense! ... Users must RTM!...
> we absolutely must insist that users RTM and continue to author
> comprehensive user manuals

Come on, Stuart... the overwhelming majority of users of office suites have not
read the manual for decades, and will not read the manual in the future. And
nobody "insists" that they do this. 


> Functional software is by its nature *NOT* self documenting. 

First let's make the distinction between "requires documentation to use" and
"self-documenting"; but ignoring that, it's certainly true that:

* A lot of functional software requires reading documentation in order to use.
* Non-requiring-documentation-to-use is indeed not part of the _nature_ of
functional software.

still, a decent office suite like LO doesn't require documentation to use. Not
because this non-requirement is in the "nature" of an office suite, but because
if it required reading a manual it would be a poor office suite. Which LO
isn't.

> Which is why the project makes considerable effort to document use, and
> provides localized Help builds online, and installed.  

Help and manuals are useful for many users, for sure. But the UI must not rely
on them being read. They are at most a "secondary line of defense" to partially
borrow from Telesto's phrasing.

> We can only do so much with UI hints and reasonable UX considerations--

We can do enough :-)

and that is the case here. Yes, there is some functionality is
super-complicated and can't be fully related to the user intuitively. But
that's really very little - especially in Impress/Draw.

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

[Libreoffice-ux-advise] [Bug 156918] "Autofit text" is ambiguous + users expect both interpretations on the context menu

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156918

--- Comment #9 from Eyal Rozenberg  ---
(In reply to V Stuart Foote from comment #8)
> Sorry but that is absolute nonsense! ... Users must RTM!...
> we absolutely must insist that users RTM and continue to author
> comprehensive user manuals

Come on, Stuart... the overwhelming majority of users of office suites have not
read the manual for decades, and will not read the manual in the future. And
nobody "insists" that they do this. 


> Functional software is by its nature *NOT* self documenting. 

First let's make the distinction between "requires documentation to use" and
"self-documenting"; but ignoring that, it's certainly true that:

* A lot of functional software requires reading documentation in order to use.
* Non-requiring-documentation-to-use is indeed not part of the _nature_ of
functional software.

still, a decent office suite like LO doesn't require documentation to use. Not
because this non-requirement is in the "nature" of an office suite, but because
if it required reading a manual it would be a poor office suite. Which LO
isn't.

> Which is why the project makes considerable effort to document use, and
> provides localized Help builds online, and installed.  

Help and manuals are useful for many users, for sure. But the UI must not rely
on them being read. They are at most a "secondary line of defense" to partially
borrow from Telesto's phrasing.

> We can only do so much with UI hints and reasonable UX considerations--

We can do enough :-)

and that is the case here. Yes, there is some functionality is
super-complicated and can't be fully related to the user intuitively. But
that's really very little - especially in Impress/Draw.

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

[Libreoffice-bugs] [Bug 156937] New: Insert Textbox button in Insert menu appears to be activated (like a toggle button)

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156937

Bug ID: 156937
   Summary: Insert Textbox button in Insert menu appears to be
activated (like a toggle button)
   Product: LibreOffice
   Version: 24.2.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: tele...@surfxs.nl

Description:
Insert Textbox button in Insert menu appears to be activated (like a toggle
button)

Steps to Reproduce:
1. Open Draw (also Impress)
2. Press F2
3. Drag a textbox
4. Click outside the textbox -> Textbox vanishes (not my preference, and there
is a bug about this; but OK)
5. Expand the menu 'Insert'

Notice a blue square behind the button

Actual Results:
Blue square, as if it where an toggle button

Expected Results:
No blue background


Reproducible: Always


User Profile Reset: No

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

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

[Libreoffice-bugs] [Bug 156934] After update to 7.6 extensions are not listed anymore

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156934

--- Comment #2 from ThP  ---
Not even the dictionaries are listed.

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

[Libreoffice-bugs] [Bug 156934] After update to 7.6 extensions are not listed anymore

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156934

--- Comment #1 from ThP  ---
Went back to 7.5.5. Problem remains.

Tried to install LanguageTool-6.2.oxt. LO says 6.0 is already installed, but
update fails.

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

[Libreoffice-commits] core.git: sd/source

2023-08-26 Thread Tomaž Vajngerl (via logerrit)
 sd/source/ui/view/drviewsf.cxx |   18 +-
 1 file changed, 17 insertions(+), 1 deletion(-)

New commits:
commit a535bacb2adeb491e919992a38e891945ca248f0
Author: Tomaž Vajngerl 
AuthorDate: Sun Aug 20 12:53:31 2023 +0200
Commit: Tomaž Vajngerl 
CommitDate: Sat Aug 26 21:05:00 2023 +0200

sd: disable ThemeDialog when not in a master page

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

diff --git a/sd/source/ui/view/drviewsf.cxx b/sd/source/ui/view/drviewsf.cxx
index 08d75842a187..83832f7ba561 100644
--- a/sd/source/ui/view/drviewsf.cxx
+++ b/sd/source/ui/view/drviewsf.cxx
@@ -37,12 +37,13 @@
 #include 
 #include 
 #include 
+#include 
 #include 
 #include 
-
 #include 
 
 #include 
+#include 
 #include 
 #include 
 #include 
@@ -468,6 +469,21 @@ void DrawViewShell::GetAttrState( SfxItemSet& rSet )
 }
 break;
 
+case SID_THEME_DIALOG:
+{
+bool bDisable = true;
+SdrPageView* pPageView = mpDrawView->GetSdrPageView();
+if (pPageView)
+{
+SdPage* pPage = 
dynamic_cast(pPageView->GetPage());
+if (pPage && pPage->IsMasterPage())
+bDisable = false;
+}
+if (bDisable)
+rSet.DisableItem(nWhich);
+}
+break;
+
 case SID_STYLE_FAMILY2:
 case SID_STYLE_FAMILY3:
 case SID_STYLE_FAMILY5:


[Libreoffice-commits] core.git: include/svx sd/qa sd/source svx/sdi

2023-08-26 Thread Tomaž Vajngerl (via logerrit)
 include/svx/svxids.hrc |6 ++--
 sd/qa/unit/uiimpress.cxx   |   50 -
 sd/source/ui/view/drtxtob1.cxx |   24 ---
 sd/source/ui/view/drviews2.cxx |   33 +--
 svx/sdi/svx.sdi|4 +--
 5 files changed, 42 insertions(+), 75 deletions(-)

New commits:
commit 6471181b66ebe634e9ffbdc2b55dbf1da17a3acf
Author: Tomaž Vajngerl 
AuthorDate: Fri Aug 18 22:31:51 2023 +0200
Commit: Tomaž Vajngerl 
CommitDate: Sat Aug 26 21:04:37 2023 +0200

svx: remove theme related parameters for Color and FillColor

For SvxColorItem, XFillColorItem, XLineColorItem,... we set the
ComplexColor via the JSON additional UNO Command argument, so we
don't need the parameters to set the theme color and LumOff and
LumMod color modifiers for the UNO Command. Actually this has
broken the setting the colors in certain situations, so we must
remove this.

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

diff --git a/include/svx/svxids.hrc b/include/svx/svxids.hrc
index 97832803a7d8..7cc55ac02813 100644
--- a/include/svx/svxids.hrc
+++ b/include/svx/svxids.hrc
@@ -452,9 +452,9 @@ class XFillGradientItem;
 #define SID_ATTR_TEXTCOLUMNS_SPACING( SID_SVX_START + 341 )
 
 // FREE ( SID_SVX_START + 342 )
-#define SID_ATTR_COLOR_THEME_INDEX  
TypedWhichId( SID_SVX_START + 343 )
-#define SID_ATTR_COLOR_LUM_MOD  
TypedWhichId( SID_SVX_START + 344 )
-#define SID_ATTR_COLOR_LUM_OFF  
TypedWhichId( SID_SVX_START + 345 )
+// FREE ( SID_SVX_START + 343 )
+// FREE ( SID_SVX_START + 344 )
+// FREE ( SID_SVX_START + 345 )
 
 #define SID_SB_CONNECTIONPOOLING( SID_SVX_START + 348 )
 #define SID_SB_DBREGISTEROPTIONS( SID_SVX_START + 349 )
diff --git a/sd/qa/unit/uiimpress.cxx b/sd/qa/unit/uiimpress.cxx
index c99d4bd5df49..61ab0c301ed6 100644
--- a/sd/qa/unit/uiimpress.cxx
+++ b/sd/qa/unit/uiimpress.cxx
@@ -47,6 +47,7 @@
 #include 
 #include 
 #include 
+#include 
 
 #include 
 #include 
@@ -1019,13 +1020,22 @@ CPPUNIT_TEST_FIXTURE(SdUiImpressTest, 
testCharColorTheme)
 dispatchCommand(mxComponent, ".uno:SelectAll", {});
 
 // When picking a theme color on the sidebar:
-uno::Sequence aColorArgs = {
-comphelper::makePropertyValue("Color", 
static_cast(0xdae3f3)), // 80% light blue
-comphelper::makePropertyValue("ColorThemeIndex", 
static_cast(4)), // accent 1
-comphelper::makePropertyValue("ColorLumMod", 
static_cast(2000)),
-comphelper::makePropertyValue("ColorLumOff", 
static_cast(8000)),
-};
-dispatchCommand(mxComponent, ".uno:Color", aColorArgs);
+{
+model::ComplexColor aComplexColor;
+aComplexColor.setThemeColor(model::ThemeColorType::Accent1);
+aComplexColor.addTransformation({ model::TransformationType::LumMod, 
2000 });
+aComplexColor.addTransformation({ model::TransformationType::LumOff, 
8000 });
+
+OUString aJSON
+= OStringToOUString(model::color::convertToJSON(aComplexColor), 
RTL_TEXTENCODING_UTF8);
+
+// When setting the fill color of that shape, with theme metadata & 
effects:
+uno::Sequence aColorArgs = {
+comphelper::makePropertyValue("Color.Color", sal_Int32(0xdae3f3)), 
// 80% light blue
+comphelper::makePropertyValue("Color.ComplexColorJSON", 
uno::Any(aJSON)),
+};
+dispatchCommand(mxComponent, ".uno:Color", aColorArgs);
+}
 
 // Then make sure the theme "metadata" is set in the document model:
 pView->EndTextEditCurrentView();
@@ -1063,14 +1073,24 @@ CPPUNIT_TEST_FIXTURE(SdUiImpressTest, 
testFillColorTheme)
  uno::UNO_QUERY);
 xController->select(uno::Any(xShape));
 
-// When setting the fill color of that shape, with theme metadata & 
effects:
-uno::Sequence aColorArgs = {
-comphelper::makePropertyValue("FillColor", 
static_cast(0xed7d31)), // orange
-comphelper::makePropertyValue("ColorThemeIndex", 
static_cast(4)), // accent 1
-comphelper::makePropertyValue("ColorLumMod", 
static_cast(4000)),
-comphelper::makePropertyValue("ColorLumOff", 
static_cast(6000)),
-};
-dispatchCommand(mxComponent, ".uno:FillColor", aColorArgs);
+// Change fill color
+{
+model::ComplexColor aComplexColor;
+aComplexColor.setThemeColor(model::ThemeColorType::Accent1);
+aComplexColor.addTransformation({ model::TransformationType::LumMod, 
4000 });
+

[Libreoffice-bugs] [Bug 127569] Print preview does not show hidden text when it's set to be printed

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=127569

Dieter  changed:

   What|Removed |Added

 CC||heiko.tietze@documentfounda
   ||tion.org

--- Comment #5 from Dieter  ---
Still the same in

Version: 7.6.0.3 (X86_64) / LibreOffice Community
Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL threaded


But there is something I don't understand: If "Hidden Text" is selected in
options menu, why is it deselected in print dialog?

For me expected behaviour would be
1. If you select "Hidden Text" in optionas dialog, it is a general setting and
therefore also active in print dialog of every document
2. If you select "Hidden Text" in print dialog, it is a setting only for the
actual document and this option is deselected in options dialog

Heiko, can you give some insights?

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

[Libreoffice-bugs] [Bug 156936] New: Cannot overlay text over a .jpg in Writer

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156936

Bug ID: 156936
   Summary: Cannot overlay text over a .jpg in Writer
   Product: LibreOffice
   Version: 7.5.3.2 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: tom05...@yahoo.com

Description:
I added a .jpg as the background to a page in Writer. When I try to overlay
text over the graphic it does not let me do it. If I take the document to
Microsoft Word and overlay the text over the graphic in Microsoft Word, then
bring that document back into Writer then it seems to work.

Steps to Reproduce:
1.Open new document in Writer
2.Insert a .jpg and stretch to fill the page
3.Select to wrap text Through the graphic
4. Anchor graphic to Character
5. Enter Returns to get to position to type text.
6. Type text to go over graphic. Note that text goes behind graphic.
7. I tried sending graphic to back but did not work.

Actual Results:
The text stays behind the graphic and no matter what I tried it would not come
to the front to overlay the graphic.

Expected Results:
The text does not overlay the graphic. It goes behind it. It seems to work if
you save the document then open it in Microsoft Word. Make it overlay then
reopen in it Writer.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.5.3.2 (X86_64) / LibreOffice Community
Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3
CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 98290] [META] Better shortcuts on macOS

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98290

Dieter  changed:

   What|Removed |Added

 Depends on||156705


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=156705
[Bug 156705] macOS keybindings for Home/End malfunctioning
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 156705] macOS keybindings for Home/End malfunctioning

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156705

Dieter  changed:

   What|Removed |Added

 Blocks||98290


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=98290
[Bug 98290] [META] Better shortcuts on macOS
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 156918] "Autofit text" is ambiguous + users expect both interpretations on the context menu

2023-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156918

--- Comment #8 from V Stuart Foote  ---
(In reply to Eyal Rozenberg from comment #7)
> (In reply to V Stuart Foote from comment #4)
> > This is a RTM issue
> 
> There is no such thing as a RTM issue regarding the UI. If you need to read
> the  manual to understand anything, then the UI is buggy in terms of
> usability.
> 
> > users should
> 
> Actually, they shouldn't. The manual is a convenience feature for people who
> like to learn how to use an application that way. 
> 
> There are exceptions, I suppose, like super-complex / heavily-configurable
> features - where perhaps you really must have the user read the manual. But
> that's not the general case and not the case here.
> 
> Also, the users don't read the manual, and won't. (And I make it a point not
> to bias my QA work by whatever the manual says.)

Sorry but that is absolute nonsense! Functional software is by its nature *NOT*
self documenting. Users must RTM!

Which is why the project makes considerable effort to document use, and
provides localized Help builds online, and installed.  

We can only do so much with UI hints and reasonable UX considerations--but we
absolutely must insist that users RTM and continue to author comprehensive user
manuals and localized Help.

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

  1   2   >