[Libreoffice-bugs] [Bug 47055] EDITING: Cannot comment on block of text
https://bugs.documentfoundation.org/show_bug.cgi?id=47055 --- Comment #13 from jhanvipatel --- Call:+971503735841 Dubai escorts miss jhanvi https://www.jhan-vipatel.com offering elite independent escorts service at very cheap rates. Book our female model escorts in Dubai and enjoy fullest. Dubai call girls whatsapp number with real photos. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 47055] EDITING: Cannot comment on block of text
https://bugs.documentfoundation.org/show_bug.cgi?id=47055 --- Comment #12 from Reha Singh --- Call +971545963556 Hi i am Alisha famous hot Indian call girls in Discovery Gardens and independent escorts in Discovery Gardens provides you the most sensual intercourse and erotic fun. For hot call girls contact me for lovely nights. https://www.tanishka-mithal.com https://www.vip-dubaicallgirls.com https://www.dubai-callgirls.com https://www.jumeirahescorts.com https://www.45min-escortsservices.com https://www.reha-singh.com https://www.taniyaverma.com https://www.dubaivipgirls.com https://www.marina-callgirls.com https://www.callgirls-dubai-escorts.com https://www.dubaiescortscities.com https://www.burdubai-callgirls.com https://www.renu-kaur.com https://www.discoverygarden-escorts.com -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152055] Help should explain which LO options are saved in the current document
https://bugs.documentfoundation.org/show_bug.cgi?id=152055 Dieter changed: What|Removed |Added CC||dgp-m...@gmx.de, ||olivier.hallot@libreoffice. ||org Component|LibreOffice |Documentation -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152122] Improve Help Online (/text/shared/01/01010300.xhp)
https://bugs.documentfoundation.org/show_bug.cgi?id=152122 BogdanB changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |buzea.bog...@libreoffice.or |desktop.org |g Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 CC||buzea.bog...@libreoffice.or ||g -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152122] New: Improve Help Online (/text/shared/01/01010300.xhp)
https://bugs.documentfoundation.org/show_bug.cgi?id=152122 Bug ID: 152122 Summary: Improve Help Online (/text/shared/01/01010300.xhp) Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Documentation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: buzea.bog...@libreoffice.org CC: olivier.hal...@libreoffice.org Description: See https://help.libreoffice.org/7.5/en-US/text/shared/01/01010300.html?DbPAR=WRITER#bm_id3149687 #1 Business Contains contact information for business cards that use a layout from a 'Business Card, Work' category. Business card layouts are selected on the Business Cards tab. We are already on Business tab, so I consider the last sentence is copy paste from the above Private tab. CORRECT: Contains contact information for business cards that use a layout from a 'Business Card, Work' category. #2 The description for Reset button is there, but not for New Document. Add this: — New Document Creates a new document for editing. — #3 The first 2 menus do not exists in Writer: Medium and Business Card. First one should be deleted, and the second one should be changed in Writer, because the same “Label” appear for inserting labels or business cards in Writer. This is a UI change. Also I noticed that this 2 items Medium and Business Card, when you acces the link are splitting the content from Business Cards - Labels on 2 pages. Is much better how things are done for File - New - Labels - Labels https://help.libreoffice.org/7.5/en-US/text/shared/01/01010201.html?=SHARED=UNIX. Things are described here compact, on one page. Things should be done the same for Business Card. Steps to Reproduce: - Actual Results: - Expected Results: - Reproducible: Always User Profile Reset: No Additional Info: - -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152121] Improve Help Online (/text/shared/01/01010203.xhp)
https://bugs.documentfoundation.org/show_bug.cgi?id=152121 BogdanB changed: What|Removed |Added Ever confirmed|0 |1 Assignee|libreoffice-b...@lists.free |buzea.bog...@libreoffice.or |desktop.org |g CC||buzea.bog...@libreoffice.or ||g Status|UNCONFIRMED |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152121] New: Improve Help Online (/text/shared/01/01010203.xhp)
https://bugs.documentfoundation.org/show_bug.cgi?id=152121 Bug ID: 152121 Summary: Improve Help Online (/text/shared/01/01010203.xhp) Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Documentation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: buzea.bog...@libreoffice.org CC: olivier.hal...@libreoffice.org Description: See https://help.libreoffice.org/7.5/en-US/text/shared/01/01010203.html?DbPAR=WRITER#bm_id3149687 COLUMN - the description is incorrect, see the Writer tooltip, is much better. WRONG: “Enter the number of labels or business cards that you want to have in a row on your page.” CORRECT: “Enter the column in which you want to place your single label or business card.” ROW - the description is incorrect, see the Writer tooltip, is much better. WRONG: “Enter the number of rows of labels or business cards that you want to have on your page.” CORRECT: “Enter the row in which you want to place your single label or business card.” Steps to Reproduce: - Actual Results: - Expected Results: - Reproducible: Always User Profile Reset: No Additional Info: - -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151660] application window problem
https://bugs.documentfoundation.org/show_bug.cgi?id=151660 --- Comment #1 from Mike Little --- 1. Two screens: one landscape orientation, and the other, portrait orientation 2. Regression tested on… Version: 7.4.2.3 / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 4; OS: Mac OS X 13.0; UI render: default; VCL: osx Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded 3. Opened application on the landscape orientated screen from the ./soffice.sh script. 4. Application scales to the landscape orientated screen. 5. Opened application on the portrait orientated screen from the ./soffice.sh script. 6. Application scales to the portrait orientated screen. 7. Opened application on the landscape orientated screen from the ./soffice.sh script. 8. Application scales to the landscape orientated screen. 9. Opened application on the landscape orientated screen from the ./soffice.sh script. 10. Application scales to the landscape orientated screen. 11. Opened Writer. 12. Moved Writer from the landscape orientated screen to the portrait orientated screen and made the following observations: a. Manually resized the Writer application window and did not observe the application turning grey. b. Moving the Writer application from one screen to another did not have an impact. CONCLUSION: I WAS NOT ABLE TO CONFIRM WHAT PREVIOUSLY OBSERVED. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151427] Writer is not opening at last cursor position
https://bugs.documentfoundation.org/show_bug.cgi?id=151427 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 150657] CALC Chart elements disappear when the data columns are hidden
https://bugs.documentfoundation.org/show_bug.cgi?id=150657 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 151895] Support custom user variables in impress
https://bugs.documentfoundation.org/show_bug.cgi?id=151895 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 151905] Hang/freeze when copying inside the file open dialog with something on the (internal) LibreOffice clipboard (Win only?)
https://bugs.documentfoundation.org/show_bug.cgi?id=151905 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 151882] Theme color does not work for docx -> odt ->docx
https://bugs.documentfoundation.org/show_bug.cgi?id=151882 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 151830] Save as text with coding utf-8 destroys all non-ascii characters, replacing with question mark
https://bugs.documentfoundation.org/show_bug.cgi?id=151830 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 148709] Spurious crash report screen on start up of Libreoffice
https://bugs.documentfoundation.org/show_bug.cgi?id=148709 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 148709] Spurious crash report screen on start up of Libreoffice
https://bugs.documentfoundation.org/show_bug.cgi?id=148709 --- Comment #3 from QA Administrators --- Dear Chris Watson, 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 143941] LibreCalc freezes machine when shutting down [1]
https://bugs.documentfoundation.org/show_bug.cgi?id=143941 --- Comment #3 from QA Administrators --- Dear dpkesling, 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 149038] Adding support for RD Field Codes in .docx format
https://bugs.documentfoundation.org/show_bug.cgi?id=149038 --- Comment #2 from QA Administrators --- Dear Muhammad Hasan Firdaus, 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 98244] RTL: Sidebar background color widget does not have icon on correct side
https://bugs.documentfoundation.org/show_bug.cgi?id=98244 --- Comment #6 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 91904] Color drop down needs to be lower when expanded from toolbar on the left
https://bugs.documentfoundation.org/show_bug.cgi?id=91904 --- Comment #7 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97893] Snap Lines get disabled when enabling Snap to Snap Lines
https://bugs.documentfoundation.org/show_bug.cgi?id=97893 --- Comment #5 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 91816] FORMATTING indent right greyed out
https://bugs.documentfoundation.org/show_bug.cgi?id=91816 --- Comment #10 from QA Administrators --- Dear Becoming DAU, 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 90987] Pages/Slides pane does not remember its collapsed state on reopen
https://bugs.documentfoundation.org/show_bug.cgi?id=90987 --- Comment #17 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 88769] Improper SORTING on the date field for certain date formats
https://bugs.documentfoundation.org/show_bug.cgi?id=88769 --- Comment #10 from QA Administrators --- Dear Jacques, 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 80662] RTL: The update number of the java version number in Options dialog is on the wrong side
https://bugs.documentfoundation.org/show_bug.cgi?id=80662 --- Comment #7 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 83350] RTL: Status bar fields aligned to the left
https://bugs.documentfoundation.org/show_bug.cgi?id=83350 --- Comment #8 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 35574] doc with embedded tables formatting issues (see comment 14)
https://bugs.documentfoundation.org/show_bug.cgi?id=35574 --- Comment #18 from QA Administrators --- Dear digital ant, 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 138195] UI: Rename image/chart has no separate undo step (working correctly for textbox)
https://bugs.documentfoundation.org/show_bug.cgi?id=138195 --- Comment #3 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 137839] Shapes disappear after undo followed by Enter (caused by invisible selection; comment 2)
https://bugs.documentfoundation.org/show_bug.cgi?id=137839 --- Comment #5 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 133389] Date & time functions in StarBasic and Calc return different results
https://bugs.documentfoundation.org/show_bug.cgi?id=133389 --- Comment #4 from QA Administrators --- Dear Albrecht Müller, 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 131151] Arithmetic error in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=131151 --- Comment #8 from QA Administrators --- Dear Alexey, 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 130900] Enter Key broke animations in a textbox
https://bugs.documentfoundation.org/show_bug.cgi?id=130900 --- Comment #6 from QA Administrators --- Dear Pierre C, 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 126062] Save to disconnected shared folder is unfriendly, and shows strange errors
https://bugs.documentfoundation.org/show_bug.cgi?id=126062 --- Comment #4 from QA Administrators --- Dear Aron Budea, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114505] Changing icon theme while in RTL mode causes flipped icons in toolbar to misbehave
https://bugs.documentfoundation.org/show_bug.cgi?id=114505 --- Comment #7 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112992] RTL: Textbox, spinbox and combobox input fields should be right aligned
https://bugs.documentfoundation.org/show_bug.cgi?id=112992 --- Comment #6 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112623] Dragging snap point doesn't show snap point
https://bugs.documentfoundation.org/show_bug.cgi?id=112623 --- Comment #7 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112131] Unable to modify hyperlink target in document
https://bugs.documentfoundation.org/show_bug.cgi?id=112131 --- Comment #6 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107924] Row select command moves text cursor from cell
https://bugs.documentfoundation.org/show_bug.cgi?id=107924 --- Comment #5 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107485] Font name toolbar control shouldnt display non-english alternative name in english locale
https://bugs.documentfoundation.org/show_bug.cgi?id=107485 --- Comment #7 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107324] Inserted images not always aligned correctly to slide
https://bugs.documentfoundation.org/show_bug.cgi?id=107324 --- Comment #5 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107323] Inserted videos shouldnt exceed the margins of the page or sheet
https://bugs.documentfoundation.org/show_bug.cgi?id=107323 --- Comment #7 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107319] Clear direct formatting doesnt work with frame styled elements
https://bugs.documentfoundation.org/show_bug.cgi?id=107319 --- Comment #5 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102995] Data table dialog toolbar does not respect button icon size option
https://bugs.documentfoundation.org/show_bug.cgi?id=102995 --- Comment #5 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105749] Document-level snap and grid options not superseding global-level options
https://bugs.documentfoundation.org/show_bug.cgi?id=105749 --- Comment #5 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102305] Rotation of AutoLayout textboxes not applied
https://bugs.documentfoundation.org/show_bug.cgi?id=102305 --- Comment #5 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152120] Wrong font size and style for the selection of the dropdown content control
https://bugs.documentfoundation.org/show_bug.cgi?id=152120 Hossein changed: What|Removed |Added Blocks||107742 CC||vmik...@collabora.com Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107742 [Bug 107742] [META] Form control bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107742] [META] Form control bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107742 Hossein changed: What|Removed |Added Depends on||152120 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152120 [Bug 152120] Wrong font size and style for the selection of the dropdown content control -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152120] New: Wrong font size and style for the selection of the dropdown content control
https://bugs.documentfoundation.org/show_bug.cgi?id=152120 Bug ID: 152120 Summary: Wrong font size and style for the selection of the dropdown content control Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hoss...@libreoffice.org Description: When selecting an option from the list of options in the dropdown content control, sometimes wrong font size is used for the selection Steps to Reproduce: 1- Open attachment 182846 2- Click on the gray fields in 2nd row of the page 1 3- Select arbitrary options for the two fields (You may have to use keyboard, and alt+down key instead of mouse because of bug 152119) Actual Results: The font size and style for the two fields are different. Expected Results: The font size and style for both fields should be the same. This is the behavior in MS Word when opening the same file and working with the same fields. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: bcf09f9a9bde21aac1302cbead2b23822458 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107742] [META] Form control bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107742 Hossein changed: What|Removed |Added Depends on||152119 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152119 [Bug 152119] Dropdown content control for RTL fields no longer selectable by mouse -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152119] Dropdown content control for RTL fields no longer selectable by mouse
https://bugs.documentfoundation.org/show_bug.cgi?id=152119 Hossein changed: What|Removed |Added Blocks||107742 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107742 [Bug 107742] [META] Form control bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152119] Dropdown content control for RTL fields no longer selectable by mouse
https://bugs.documentfoundation.org/show_bug.cgi?id=152119 --- Comment #1 from Hossein --- The problem is also reproducible with X11, KF5 and GTK4: Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: bcf09f9a9bde21aac1302cbead2b23822458 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: x11 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: bcf09f9a9bde21aac1302cbead2b23822458 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: bcf09f9a9bde21aac1302cbead2b23822458 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk4 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Testing with attachment 182846 shows that at the same time, there is no problem with LTR fields: The down arrow is usable by mouse for the LTR fields, while mouse does not work with RTL fields. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152119] New: Dropdown content control for RTL fields no longer selectable by mouse
https://bugs.documentfoundation.org/show_bug.cgi?id=152119 Bug ID: 152119 Summary: Dropdown content control for RTL fields no longer selectable by mouse Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hoss...@libreoffice.org Description: After the fix provided by Miklos for tdf#151980, the Dropdown content control is drawn on the left, which is correct. But recently I can no longer select the drowpdown button. Steps to Reproduce: 1. Open attachment 183516 from the above mentioned issue 2. Try opening the dropdown content control using mouse Actual Results: You can not open the dropdown menu. Down arrow is shown but it is not usable. Expected Results: You should be able to open the dropdown menu as before Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: bcf09f9a9bde21aac1302cbead2b23822458 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128332] Paste image into empty content frame should work like clicking the center widget
https://bugs.documentfoundation.org/show_bug.cgi?id=128332 --- Comment #19 from Andrew --- Created attachment 183678 --> https://bugs.documentfoundation.org/attachment.cgi?id=183678=edit Impress vs. PowerPoint User Experience -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128332] Paste image into empty content frame should work like clicking the center widget
https://bugs.documentfoundation.org/show_bug.cgi?id=128332 --- Comment #18 from Andrew --- I attached a video showing the different user experience in Impress vs. Microsoft PowerPoint. Microsoft PowerPoint is way ahead of Impress on usability. This technique to be able to paste the clipboard into a content placeholder has worked in Microsoft Powerpoint since Microsoft Office XP/2000 or earlier. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152115] Hyperlink Target in document: The last user setting is not remembered
https://bugs.documentfoundation.org/show_bug.cgi?id=152115 V Stuart Foote changed: What|Removed |Added Summary|Target in document: The |Hyperlink Target in |last user setting is not|document: The last user |rememberd |setting is not remembered -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147906] Use std::hypot for Pythagorean addition
https://bugs.documentfoundation.org/show_bug.cgi?id=147906 --- Comment #11 from Commit Notification --- OmkarAcharekar committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/bcf09f9a9bde21aac1302cbead2b23822458 tdf#147906 Use std::hypot for Pythagorean addition It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114567] HYPERLINK DIALOG: "Target in document" dialog should display the level of headings
https://bugs.documentfoundation.org/show_bug.cgi?id=114567 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2115 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152115] Target in document: The last user setting is not rememberd
https://bugs.documentfoundation.org/show_bug.cgi?id=152115 V Stuart Foote changed: What|Removed |Added CC||rayk...@gmail.com See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||4567 --- Comment #2 from V Stuart Foote --- @Jim, think there might be something additional here for Hyperlink in Document, beyond your expanding headings in https://gerrit.libreoffice.org/c/core/+/109930 done for bug 114567 And maybe related, OPs concern of SB Navigator collapse in bug 152116 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112125] [META] Hyperlink dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=112125 V Stuart Foote changed: What|Removed |Added Depends on||152115 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152115 [Bug 152115] Target in document: The last user setting is not rememberd -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152115] Target in document: The last user setting is not rememberd
https://bugs.documentfoundation.org/show_bug.cgi?id=152115 V Stuart Foote changed: What|Removed |Added Ever confirmed|0 |1 CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vsfo...@libreoffice.org Keywords||needsUXEval Blocks||112125 Status|UNCONFIRMED |NEW --- Comment #1 from V Stuart Foote --- Confirmed, Version: 7.4.2.3 (x64) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL Following STR of OP the 'Target in document' pop-up (browse button of hldoctp.cxx) opens, using a tree sort order a bit different to SB, tree list collapses when closing and reopening in current launch. Would be helpful if the expanded tree list would remain, at least while picking the Target in Dialog during the current Hyperlink dialog session--collapsing as it does is annoying while trying to pick the exact target to use. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=112125 [Bug 112125] [META] Hyperlink dialog bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152114] Dates imported erroneously from Calc to Writer database fields
https://bugs.documentfoundation.org/show_bug.cgi?id=152114 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152114] Dates imported erroneously from Calc to Writer database fields
https://bugs.documentfoundation.org/show_bug.cgi?id=152114 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #4 from m.a.riosv --- Created attachment 183677 --> https://bugs.documentfoundation.org/attachment.cgi?id=183677=edit Sample with range dates Seems it happens with dates before 03/01/0001. Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: a81e957f5026373f3935390c786c21416fc74fcc CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152118] Dates imported erroneously from Calc to a Firebird database table
https://bugs.documentfoundation.org/show_bug.cgi?id=152118 --- Comment #5 from jcs...@libreoffice.org --- I have done the same test in a MariaDB database with a Direct connection and the results obtained are exactly the same but in MariaDB the record with ID = 3 has been imported, but the date showed in the table view is "03/01/0001" and the date actually stored is 31/12/. Note that the las date is not a valid date in Firebird, so it couldn't be imported in that database. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152114] Dates imported erroneously from Calc to Writer database fields
https://bugs.documentfoundation.org/show_bug.cgi?id=152114 --- Comment #3 from jcs...@libreoffice.org --- Sorry, the last comment is not to this bug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152114] Dates imported erroneously from Calc to Writer database fields
https://bugs.documentfoundation.org/show_bug.cgi?id=152114 --- Comment #2 from jcs...@libreoffice.org --- I have done the same test in a MariaDB database with a Direct connection and the results obtained are exactly the same but in MariaDB the record with ID = 3 has been imported, but the date showed in the table view is "03/01/0001" and the date actually stored is 31/12/. Note that the las date is not a valid date in Firebird, so it couldn't be imported in that database. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152118] Dates imported erroneously from Calc to a Firebird database table
https://bugs.documentfoundation.org/show_bug.cgi?id=152118 jcs...@libreoffice.org changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2114 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152114] Dates imported erroneously from Calc to Writer database fields
https://bugs.documentfoundation.org/show_bug.cgi?id=152114 jcs...@libreoffice.org changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2118 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152118] Dates imported erroneously from Calc to a Firebird database table
https://bugs.documentfoundation.org/show_bug.cgi?id=152118 --- Comment #4 from jcs...@libreoffice.org --- Created attachment 183676 --> https://bugs.documentfoundation.org/attachment.cgi?id=183676=edit Base file created in the test -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152118] Dates imported erroneously from Calc to a Firebird database table
https://bugs.documentfoundation.org/show_bug.cgi?id=152118 --- Comment #3 from jcs...@libreoffice.org --- Created attachment 183675 --> https://bugs.documentfoundation.org/attachment.cgi?id=183675=edit Firebird database file created in the test -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152118] Dates imported erroneously from Calc to a Firebird database table
https://bugs.documentfoundation.org/show_bug.cgi?id=152118 --- Comment #2 from jcs...@libreoffice.org --- Created attachment 183674 --> https://bugs.documentfoundation.org/attachment.cgi?id=183674=edit Original Calc file used to test -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152111] Add a protection-against-deletion checkbox to table/index generation dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=152111 m.a.riosv changed: What|Removed |Added Severity|normal |enhancement -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152118] Dates imported erroneously from Calc to a Firebird database table
https://bugs.documentfoundation.org/show_bug.cgi?id=152118 --- Comment #1 from jcs...@libreoffice.org --- Created attachment 183673 --> https://bugs.documentfoundation.org/attachment.cgi?id=183673=edit Image comparing the different data obtained -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152118] New: Dates imported erroneously from Calc to a Firebird database table
https://bugs.documentfoundation.org/show_bug.cgi?id=152118 Bug ID: 152118 Summary: Dates imported erroneously from Calc to a Firebird database table Product: LibreOffice Version: 7.4.2.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jcs...@libreoffice.org Description: When importing dates from a Calc test table to a Base Firebird database table, some dates are imported erroneously and furthermore are shown in differently depend on the way of view Steps to Reproduce: To perform this test, a Firebird database has been created in an external file. This type of database has been chosen because of the ease of creating it and accessing the data directly, without the need of a Base database. Although it is needed a Firebird server in order to know what data has actually been saved in the database. -- Step 1. Creation of the database. --- 1. Open Base 2. In the Database Wizard, select Connect to an existing database > Firebird External and click Next. 3. In step 2 of the wizard, Connection Settings, click the Create New button 4. In the Save As dialog, browse for a suitable location and name the FDB file in the Firebird database, for example DATES1.FDB and click the Save button 5. When you return to the Database Wizard, click the Next button 6. In step 3 of the wizard, Set up user authentication, leave everything blank, as is, and click the Next button 7. In step 4, leave the default options for Base to register the database, and then open the file. Click Finish 8. In the Save As dialog, search for a suitable location and save the database with the name Dates1.odb 9. The database will be created and opened -- Step 2. Import data from Calc to a Firebird table --- 1. With the database open, as we left it in the previous step, open the Calc Dates.ods file with the sample data 2. On Sheet1 containing the data, select all (Edit > Select All) 3. Select Edit > Copy menu (or Ctrl+C) 4. Switch to Base, and in the Tables section, right-click and select Paste from the context menu. 5. In the Copy Table dialog that appears, name the new table, for example Table1. Under Options, select Definition and data and check the Use the first line as column names box. and click Next. 6. In the next step, Apply columns, move the three columns to the right side. and click Next. 7. In the next step: a) Column ID, assign Field type: INTEGER, and do it Primary key (right-click over ID and select) b) Column TEXT, assign Field type VARCHAR and Length 12 c) Column DATE, assing Field type DATE 8. Click Create 9. A warning message appears “firebird_sdbc error: value exceeds the range for valid dates caused by 'isc_dsql_execute' Continue any way?”. Click Yes 10. Table1 has been created -- Step 3. View table data - To view the table data: 1. Double-click on the name of the newly created table 2. To see the dates in the same format as they had in the Calc table, right-click on the header of the DATE column and in the context menu select Column Format 3. In the Field Format dialog, on the Format tab, under Category, select Date, and under Format, select 31/12/1999. Click OK. 4. Observe the data. 5. Fields with ID = 1 and ID = 2 have erroneous dates 6. Field with ID = 3 has not been imported (maybe the warning message in the step 9 above) -- Step 4. View data in SQL command dialog 1. In Base menu, select Tools > SQL 2. In the box Command to execute write Select * from “Table1” 3. Check Run SQL command directly 4. Check Show output of “select” statements 5. Click on Execute button 6. Observe the results on Output box --Step 5. View data directly in Firebird - 1. On an operating system console run isql or isql-fb as needed 2. Connect to the database: CONNECT /path/to/folder/DATES1.FDB; 3. Show the data in the table Table1: SELECT * FROM "Table1"; 4. Observe the data. Actual Results: - Some dates are imported in an incorrect way - Depends on the way of view the data, the dates showed are different - Stored data are incorrect and are showed incorrectly Expected Results: The imported dates should be the same in any way of view and the stored data should be the same that the original one Reproducible: Always User Profile Reset: No Additional Info: Version: 7.4.2.3 (x64) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL
[Libreoffice-bugs] [Bug 152102] PIVOTTABLE: Compatibility is lost between versions of Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=152102 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEEDINFO --- Comment #1 from m.a.riosv --- Please, can you attach a sample file. And copy the info in Menu/Help/About LibreOffice (there is an icon to copy). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103030] [META] Navigator sidebar deck and floating window
https://bugs.documentfoundation.org/show_bug.cgi?id=103030 V Stuart Foote changed: What|Removed |Added Depends on||152116 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152116 [Bug 152116] Navigator: State of outline headings is lost when navigator is closed then reopened -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152116] Navigator: State of outline headings is lost when navigator is closed then reopened
https://bugs.documentfoundation.org/show_bug.cgi?id=152116 V Stuart Foote changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vsfo...@libreoffice.org Blocks||103030 Keywords||needsUXEval --- Comment #2 from V Stuart Foote --- Confirmed, fully closing and reopening SB Navigator resets 'Headings' mode view to all collapsed. Note though that simply collapsing to SB Tab bar and expanding open in current session retains the Headings mode. Of course some folks prefer that behavior--clearing the Navigator with each use. So, not clear there is an issue here. But providing an option to retain state of the SB Navigator might be of use. Version: 7.4.2.3 (x64) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103030 [Bug 103030] [META] Navigator sidebar deck and floating window -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152117] UNO Object Inspector: No suitable title bar in docked state
https://bugs.documentfoundation.org/show_bug.cgi?id=152117 Hossein changed: What|Removed |Added Keywords||topicUI CC||libreoffice-ux-advise@lists ||.freedesktop.org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141420] [META] UNO Object Inspector - Development tools
https://bugs.documentfoundation.org/show_bug.cgi?id=141420 Hossein changed: What|Removed |Added Depends on||152117 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152117 [Bug 152117] UNO Object Inspector: No suitable title bar in docked state -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152117] UNO Object Inspector: No suitable title bar in docked state
https://bugs.documentfoundation.org/show_bug.cgi?id=152117 Hossein changed: What|Removed |Added Blocks||141420 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||3641 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=141420 [Bug 141420] [META] UNO Object Inspector - Development tools -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152117] New: UNO Object Inspector: No suitable title bar in docked state
https://bugs.documentfoundation.org/show_bug.cgi?id=152117 Bug ID: 152117 Summary: UNO Object Inspector: No suitable title bar in docked state Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hoss...@libreoffice.org Description: UNO object inspector does not have a title bar in docked state, and because of that, it also does not have a title in docked mode. In detached state, lacking title was fixed in tdf#143641, but for the docked state the problem persists. Steps to Reproduce: 1. Open LibreOffice 2. Open "UNO Object Inspector" from "Tools > Development Tools" Menu 3. Make sure that the window is docked Actual Results: The docked window does not have any title bar and thus no title Expected Results: The docked window should have a title bar and appropriate title Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 50d73574b6c3d71f9a539c895a15d6fcda22390b CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152114] Dates imported erroneously from Calc to Writer database fields
https://bugs.documentfoundation.org/show_bug.cgi?id=152114 --- Comment #1 from jcs...@libreoffice.org --- Created attachment 183672 --> https://bugs.documentfoundation.org/attachment.cgi?id=183672=edit Calc file with the dates used to test -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149935] Insert Hyperlink: "Target in document" window does not remember last user position and size
https://bugs.documentfoundation.org/show_bug.cgi?id=149935 R. Green changed: What|Removed |Added Summary|Insert Hyperlink: "Target |Insert Hyperlink: "Target |in document" window does|in document" window does |not remmeber last user |not remember last user |position and size |position and size -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149935] Insert Hyperlink: "Target in document" window does not remmeber last user position and size
https://bugs.documentfoundation.org/show_bug.cgi?id=149935 R. Green changed: What|Removed |Added Ever confirmed|1 |0 Summary|Insert Hyperlink: Add |Insert Hyperlink: "Target |"tooltips" to list entries |in document" window does |in "Target in document" |not remmeber last user ||position and size Status|NEEDINFO|UNCONFIRMED --- Comment #2 from R. Green --- The issue is that the the target in document window does not remember the last user-set size. So, if I widen it to see more of the headings, when closed and reopened, it reverts to the default width. So the issue is really, can this be fixed so that the last size and position of the window is remembered when closed? I have changed the title to relect this. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141420] [META] UNO Object Inspector - Development tools
https://bugs.documentfoundation.org/show_bug.cgi?id=141420 Bug 141420 depends on bug 143641, which changed state. Bug 143641 Summary: UNO Object Inspector: No suitable title for the window https://bugs.documentfoundation.org/show_bug.cgi?id=143641 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152116] Navigator: State of outline headings is lost when navigator is closed then reopened
https://bugs.documentfoundation.org/show_bug.cgi?id=152116 --- Comment #1 from R. Green --- Similar type of issue reported in Bug 152115. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152116] New: Navigator: State of outline headings is lost when navigator is closed then reopened
https://bugs.documentfoundation.org/show_bug.cgi?id=152116 Bug ID: 152116 Summary: Navigator: State of outline headings is lost when navigator is closed then reopened Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: greenandpleasant2000-supp...@yahoo.co.uk Created attachment 183671 --> https://bugs.documentfoundation.org/attachment.cgi?id=183671=edit Writer file showing bug involving display of headings in the Navigator. Version: 7.4.2.3 / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 2; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-GB Calc: threaded 1. Open the attached writer doc. 2. Open the navigator. 3. Unfold one or more headings so that the subheadings are visible. 4. Close then reopen the navigator. ACTUAL RESULT: The outline collapses back so that only the top level of headings is visible. EXPECTED RESULT: The navigator should remember the lasts state of headings set by the user. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152115] New: Target in document: The last user setting is not rememberd
https://bugs.documentfoundation.org/show_bug.cgi?id=152115 Bug ID: 152115 Summary: Target in document: The last user setting is not rememberd Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: greenandpleasant2000-supp...@yahoo.co.uk Created attachment 183670 --> https://bugs.documentfoundation.org/attachment.cgi?id=183670=edit Writer file showing bug in Target in document window Version: 7.4.2.3 / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 2; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-GB Calc: threaded This a relatively recent and unwelcome regression. 1. Open the attached document. 2. Select a word or phrase. 3. Select "Insert Hyperlink > Document > Target in document. 4. Unfold one or more headings to reveal the subheadings. 5. Close the "Target in document" window, then reopen it ACTUAL RESULT: The headings have collapsed back so only the top level of headings are visible. EXPECTED RESULT The target in document window should ALWAYS remember the previously-set state of headings when reopened This is a real time-waster of a bug. It means you have to unfold the headings every time you open the dialog. Given that documents may contain scores, even hundreds, of subheadings, you can imagine the extra work involved. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152107] Clicking on a cell shows garbage as the formula
https://bugs.documentfoundation.org/show_bug.cgi?id=152107 --- Comment #4 from Martin Feeney --- Created attachment 183669 --> https://bugs.documentfoundation.org/attachment.cgi?id=183669=edit Example Spreadsheet to recreate the problem Use this spreadsheet to recreate the problem. Steps: 1) Double left-click on cell N33. You should see the cell replaced with the formula =SUM(B33:M33). 2) Move the cursor cell N32 and double left-click. Cell N33 is overwritten with the value =SUM(N32B33:M33). I expected N32 to display =SUM(B32:M32). MS Excel and Softwork Office 2001 display this value. There are two issues: Cell N33 is not restored to it's value (15705) and the formula for cell N32 is partially written into Cell N33. If you repeat the process but hit the ESC key between steps 1 and 2, the program behaves as expected. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152114] New: Dates imported erroneously from Calc to Writer database fields
https://bugs.documentfoundation.org/show_bug.cgi?id=152114 Bug ID: 152114 Summary: Dates imported erroneously from Calc to Writer database fields Product: LibreOffice Version: 7.4.2.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jcs...@libreoffice.org Description: When importing dates from a Calc test table to a Writer database fields, some dates shown in Writer are different from the original dates in Calc Steps to Reproduce: To perform this test, it is used the sample Calc file attached. 1. Open a new Writer document 2. From the menu, select Insert > Field > More Fields (or press Ctrl+F2) 3. In the Fields dialog that appears, select the Database tab 4. In Add Database File, click the Browse button 5. Navigate to select the Calc file with the test data and click on the Open button. 6. In the upper-right list Database selection, a new option will be added with the name Dates 7. Click on the + sign to display the new Dates option and select the name of the sheet containing the data (Sheet1) 8. In the list on the left Data, select, for example, Database Name and click the Insert button. This step is used to register the database, so it does not matter which option you select in Data, whenever a field is inserted. 9. Close the Fields dialog 10. Show data sources with View > Data Sources menu 11. In the tree on the left side of the data sources, display Dates > Tables > Sheet1. On the right side you will see the table with the data coming from the Calc sheet. 12. To see the data better, in the data table on the right, right-click on the header of the DATE column and in the contextual menu select Column Format 13. In the Field Format dialog box, in the Category list, select Date, and in the Format list, select 31/12/1999. Click the OK button. This will display the date in the same format as on the original Calc sheet. 14. Observe the differences with the original data Actual Results: Some dates imported are different from original dates in Calc Expected Results: Same dates after importin Reproducible: Always User Profile Reset: No Additional Info: Version: 7.4.2.3 (x64) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL Version: 7.4.2.3 / LibreOffice Community Build ID: 40(Build:3) CPU threads: 1; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: es-ES (es_ES.UTF-8); UI: es-ES 7.4.2-2 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104597] RTL script text runs are reversed on PDF import, PDFIProcessor::mirrorString misbehaving
https://bugs.documentfoundation.org/show_bug.cgi?id=104597 --- Comment #96 from Commit Notification --- Stephan Bergmann committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/50d73574b6c3d71f9a539c895a15d6fcda22390b Related tdf#104597, tdf#151546: Introduce comphelper::string::reverseCodePoints It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152113] Improve Help Online (source/text/shared/01/01010202.xhp)
https://bugs.documentfoundation.org/show_bug.cgi?id=152113 BogdanB changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 Assignee|libreoffice-b...@lists.free |buzea.bog...@libreoffice.or |desktop.org |g CC||buzea.bog...@libreoffice.or ||g -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152113] New: Improve Help Online (source/text/shared/01/01010202.xhp)
https://bugs.documentfoundation.org/show_bug.cgi?id=152113 Bug ID: 152113 Summary: Improve Help Online (source/text/shared/01/01010202.xhp) Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Documentation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: buzea.bog...@libreoffice.org CC: olivier.hal...@libreoffice.org Description: See https://help.libreoffice.org/7.5/en-US/text/shared/01/01010202.html?DbPAR=WRITER#bm_id3149687 - Under "Vertical pitch" we have the text "Displays the distance between the upper edge of a label or a business card and the upper edge of the label or the business card directly below. If you are defining a custom format, enter a value here." DIRECTLY BELOW should be a mistake in the text. Also upper could be replace with top The text should be: "Displays the distance between the top edge of a label or a business card and the top edge of the label or the business card. If you are defining a custom format, enter a value here." - The option "Upper margin" is in fact "Top margin" - After the Rows menu should be "Page width" and "Page height" menus. Steps to Reproduce: - Actual Results: - Expected Results: - Reproducible: Always User Profile Reset: No Additional Info: - -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152112] Improve Help Online (source/text/shared/01/01010201.xhp)
https://bugs.documentfoundation.org/show_bug.cgi?id=152112 BogdanB changed: What|Removed |Added Ever confirmed|0 |1 CC||buzea.bog...@libreoffice.or ||g Status|UNCONFIRMED |ASSIGNED Assignee|libreoffice-b...@lists.free |buzea.bog...@libreoffice.or |desktop.org |g --- Comment #1 from BogdanB --- Now in gerrit https://gerrit.libreoffice.org/c/help/+/142918 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152112] New: Improve Help Online (source/text/shared/01/01010201.xhp)
https://bugs.documentfoundation.org/show_bug.cgi?id=152112 Bug ID: 152112 Summary: Improve Help Online (source/text/shared/01/01010201.xhp) Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Documentation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: buzea.bog...@libreoffice.org CC: olivier.hal...@libreoffice.org Description: Under the Info option we have the text: "The paper type and the dimensions of the label are displayed at the bottom of the Format area." But, the info is showing also the grid of the labels, so you can see how many labels you will have on a page. This info should be also in description. So, I propose: "The paper type, the dimensions of the label and the labels grid are displayed at the bottom of the Format area." Steps to Reproduce: - Actual Results: - Expected Results: - Reproducible: Always User Profile Reset: No Additional Info: - -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152075] Writer: TOC for chapter should start at current level+1, not current level
https://bugs.documentfoundation.org/show_bug.cgi?id=152075 --- Comment #4 from ajlittoz --- (In reply to Heiko Tietze from comment #3) > (In reply to Roman Kuznetsov from comment #1) > > For: Chapter Start from level [2] Evaluate up to level [10] > > […] I also wonder what users expect > for the start. Is it the level 1,2,3... or the actual number like 3.1 or 4. > Start from level 2 would still return 3 in the example. As we can never guess what a user would like for a specific document, how would the following (nonsensical ?) scenario be handled? Document has structure like: 1 Heading 1 1.1 Heading 2 Some text 2 Heading 1 2.1 Heading 2 Some text 2.2 Heading 2 <<-- "chapter" TOC here with request start from 1 (instead of more common start from 3)-->> 2.2.1 Heading 3 2.2.2 Heading 3 With a request to start from 1, it is clear that user wants to repeat 2 Heading 1 and 2.2 Heading 2 in his chapter TOC (without 1 Heading 1 and its sub-tree, nor 3 Heading 1 with its sub-tree and subsequent. If "Start from level" is allowed to be unconstrained, it complicates entries collection because a distinction must be made between shallower levels (retrieve only from current "context" just like fields would do) and deeper levels (where usual engine can be used). So, the "Start from level" is the first level to include in the chapter TOC, not the designation of the level where the TOC is inserted in the document. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152111] Add a protection-against-deletion checkbox to table/index generation dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=152111 Eyal Rozenberg changed: What|Removed |Added Version|3.5.0 release |Inherited From OOo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152111] Add a protection-against-deletion checkbox to table/index generation dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=152111 Eyal Rozenberg changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152030] Allow regular deletion of selection containing an entire generated index/table
https://bugs.documentfoundation.org/show_bug.cgi?id=152030 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2111 --- Comment #9 from Eyal Rozenberg --- Created a "compromise" suggestion bug report: 152111. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152111] Add a protection-against-deletion checkbox to table/index generation dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=152111 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2030 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152111] New: Add a protection-against-deletion checkbox to table/index generation dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=152111 Bug ID: 152111 Summary: Add a protection-against-deletion checkbox to table/index generation dialog Product: LibreOffice Version: 3.5.0 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com This is a followup, or perhaps a compromise, regarding the now-closed bug 152030. When choosing to insert a generated table/index (GTI for short), the user gets a dialog with various options. One of these is a checkbox labeled: "Protected against manual changes". Now, personally, I believe this checkbox should mean just what it says - protection against changes within the GTI, _not_ against removal/deletion altogether. Unfortunately, it has been decided that this should also protect against deletion. That being the case, I suggest that: 1. The checkbox be split in two: One for changes within the GTI, another for outright deletion. 2. The protection against deletion checkbox be unchecked by default. -- You are receiving this mail because: You are the assignee for the bug.
