[Libreoffice-bugs] [Bug 107658] Display of hidden text when toggling formatting marks should be enabled by default
https://bugs.documentfoundation.org/show_bug.cgi?id=107658 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||3221 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143221] Menu/Toolbar entry to show hidden character
https://bugs.documentfoundation.org/show_bug.cgi?id=143221 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||7658 --- Comment #9 from Justin L --- (In reply to Justin L from comment #5) The topic of whether show hidden text should be enabled by default and/or whether there should be a view-menu option is discussed in bug 107658. Quite frankly, I would consider this to be a duplicate of that. Personally, I think the current status quo is best. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102495] [META] KDE VCL backend bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102495 Bug 102495 depends on bug 144571, which changed state. Bug 144571 Summary: (FILTER) Selection of column constraints in AutoFilter is impossible because popup window disappears https://bugs.documentfoundation.org/show_bug.cgi?id=144571 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144571] (FILTER) Selection of column constraints in AutoFilter is impossible because popup window disappears
https://bugs.documentfoundation.org/show_bug.cgi?id=144571 Eike changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #8 from Eike --- Today I received Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: en-US Ubuntu package version: 1:7.2.1-0ubuntu0.20.04.1~lo1 Calc: CL which was uploaded in the PPA. The bug is now removed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143700] Libreoffice All Modules Bug Reporting
https://bugs.documentfoundation.org/show_bug.cgi?id=143700 --- Comment #2 from Colin --- I'm adding this here because it is an issue impacting bug reporting. Every report requests the status of user profile reset Many reporters are subsequently requested to test with a user profile reset Clearly, the user profile environment is not sufficiently robust. I have no idea which component of LO causes all the profile corruption and I'm assuming a project to identify the root cause and implement procedures to reduce the fragility could be beneficial. Perhaps a permanent log file to identify any changes as they are made to the underlying options could help in both the identification and recovery from profile corruption. I have certainly experienced unauthorised profile amendments by simple version upgrades which include but are not limited to:- Lost Calc Sort Lists New sort lists in foreign languages My entire "view" profile with toolbar choices and styles obliterated Not once, in my recollection, has resetting my user profile, or running in safe mode, ever made any difference to the substance of one of my bug reports. Surely that says more about the profile weaknesses than anything else - especially as the responders are constantly having to suggest resetting profiles to eliminate these acknowledged inherent weaknesses. Imagine the productivity bonus if the responders had more faith in the profiles -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136802] Compare document – review changes sequencially
https://bugs.documentfoundation.org/show_bug.cgi?id=136802 kkivi changed: What|Removed |Added Resolution|--- |FIXED Status|NEEDINFO|RESOLVED --- Comment #3 from kkivi --- In 7.2.1 buttons work as expected. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sal/rtl
sal/rtl/math.cxx | 23 +-- 1 file changed, 9 insertions(+), 14 deletions(-) New commits: commit a4d865e4d82d44cd75f24c5385d44de8f4fcc62f Author: Mike Kaganski AuthorDate: Wed Sep 29 23:22:01 2021 +0200 Commit: Mike Kaganski CommitDate: Thu Sep 30 07:13:50 2021 +0200 Avoid reversing the buffer Fill it in the correct order, starting from the middle Change-Id: Id35475e391d771d6c23252124a92825b24b55e0c Reviewed-on: https://gerrit.libreoffice.org/c/core/+/122853 Tested-by: Jenkins Reviewed-by: Mike Kaganski diff --git a/sal/rtl/math.cxx b/sal/rtl/math.cxx index b36aef117136..0cd53cd3902a 100644 --- a/sal/rtl/math.cxx +++ b/sal/rtl/math.cxx @@ -358,14 +358,13 @@ void doubleToString(typename T::String ** pResult, sal_Int64 nRounding = static_cast< sal_Int64 >(getN10Exp(-nDecPlaces - 1)); const sal_Int64 nTemp = (nInt / nRounding + 5) / 10; nInt = nTemp * 10 * nRounding; -nDecPlaces = 0; } // Max 1 sign, 16 integer digits, 15 group separators, 1 decimal // separator, 15 decimals digits. typename T::Char aBuf[64]; -typename T::Char * pBuf = aBuf; -typename T::Char * p = pBuf; +typename T::Char* pEnd = aBuf + 40; +typename T::Char* pStart = pEnd; // Backward fill. size_t nGrouping = 0; @@ -374,10 +373,10 @@ void doubleToString(typename T::String ** pResult, { typename T::Char nDigit = nInt % 10; nInt /= 10; -*p++ = nDigit + '0'; +*--pStart = nDigit + '0'; if (pGroups && pGroups[nGrouping] == ++nGroupDigits && nInt > 0 && cGroupSeparator) { -*p++ = cGroupSeparator; +*--pStart = cGroupSeparator; if (pGroups[nGrouping+1]) ++nGrouping; nGroupDigits = 0; @@ -385,23 +384,19 @@ void doubleToString(typename T::String ** pResult, } while (nInt > 0); if (bSign) -*p++ = '-'; - -// Reverse buffer content. -std::reverse(pBuf, p); +*--pStart = '-'; // Append decimals. if (nDecPlaces > 0) { -*p++ = cDecSeparator; -while (nDecPlaces--) -*p++ = '0'; +*pEnd++ = cDecSeparator; +pEnd = std::fill_n(pEnd, nDecPlaces, '0'); } if (!pResultCapacity) -T::createString(pResult, pBuf, p - pBuf); +T::createString(pResult, pStart, pEnd - pStart); else -T::appendChars(pResult, pResultCapacity, , pBuf, p - pBuf); +T::appendChars(pResult, pResultCapacity, , pStart, pEnd - pStart); return; }
[Libreoffice-bugs] [Bug 144820] Is The $750 Cash APP Real- make a call to the professional for assistance
https://bugs.documentfoundation.org/show_bug.cgi?id=144820 windikartika changed: What|Removed |Added URL||https://www.cash-appsupport ||.com/blog/how-can-you-reall ||y-claim-750-from-cash-app/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144820] New: Is The $750 Cash APP Real- make a call to the professional for assistance
https://bugs.documentfoundation.org/show_bug.cgi?id=144820 Bug ID: 144820 Summary: Is The $750 Cash APP Real- make a call to the professional for assistance Product: Impress Remote Version: 2.2.0 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: General Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: windikartika...@gmail.com Sometimes, new cash app users get scammed by reward programs and giveaways. So, they ask- Is The $750 Cash APP Real? For any sort of technical help, users must talk to the techies of the cash app support team. You can chat with them online or call them. https://www.cash-appsupport.com/blog/how-can-you-really-claim-750-from-cash-app/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144819] [FILEOPEN] Excel files should be recalculated when recalc flag is set
https://bugs.documentfoundation.org/show_bug.cgi?id=144819 --- Comment #1 from SheetJS --- Created attachment 175385 --> https://bugs.documentfoundation.org/attachment.cgi?id=175385=edit demonstration -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144819] New: [FILEOPEN] Excel files should be recalculated when recalc flag is set
https://bugs.documentfoundation.org/show_bug.cgi?id=144819 Bug ID: 144819 Summary: [FILEOPEN] Excel files should be recalculated when recalc flag is set Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: d...@sheetjs.com Description: XLS and XLSX files have mechanisms for marking that a file is dirty and should be recalculated. LibreOffice is not honoring these flags. Steps to Reproduce: 1. Open attached file Actual Results: Cells C2:C5 are not recalculated Expected Results: C2:C5 are recalculated (verified in Excel 2019) Reproducible: Always User Profile Reset: Yes Additional Info: For XLSX, the workbook calcPr tag has a fullCalcOnLoad attribute. For XLS, the ForceFullCalculation record 0x08A3 should be parsed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144150] Moving LibreOffice between screens shrinks it to the top right x
https://bugs.documentfoundation.org/show_bug.cgi?id=144150 afa...@gmail.com changed: What|Removed |Added CC||afa...@gmail.com --- Comment #1 from afa...@gmail.com --- Created attachment 175384 --> https://bugs.documentfoundation.org/attachment.cgi?id=175384=edit Screenshot This happens to me when using dual monitors. It also happens when dragging on a single monitor. Added screenshot of the resulting minimized window. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144477] The view Master Slide does not allow the use of Page Up/Down to go through the available master slides
https://bugs.documentfoundation.org/show_bug.cgi?id=144477 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 144322] Libreoffice Calc crashes with illegal instruction on launch, invalid opcode logged in dmesg
https://bugs.documentfoundation.org/show_bug.cgi?id=144322 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 144519] EDITING: writer: deleting a formula leaves the cursor at the wrong place
https://bugs.documentfoundation.org/show_bug.cgi?id=144519 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 144392] Current point after "close path" command Z is the initial point of the closed path
https://bugs.documentfoundation.org/show_bug.cgi?id=144392 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 144390] Marker (arrow head) on enhanced-path in custom shape is wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=144390 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 144380] Experimental Features - Forever loop for Deleting all columns
https://bugs.documentfoundation.org/show_bug.cgi?id=144380 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 144387] Numering schema don't work for not headings fonts from second level.
https://bugs.documentfoundation.org/show_bug.cgi?id=144387 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 144403] FILEOPEN libreoffice crashes when opening/creating new document
https://bugs.documentfoundation.org/show_bug.cgi?id=144403 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 144406] Crash when copying/pasting objects in Base report edit
https://bugs.documentfoundation.org/show_bug.cgi?id=144406 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 144194] CALC cell EDIT failure when right Justified formatting forces the exposed formula across the preceding cell
https://bugs.documentfoundation.org/show_bug.cgi?id=144194 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 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Bug 133092 depends on bug 127688, which changed state. Bug 127688 Summary: Dotted chapter numbering crashes Writer under Linux https://bugs.documentfoundation.org/show_bug.cgi?id=127688 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144510] Missing operation - or very hard to find if it exists
https://bugs.documentfoundation.org/show_bug.cgi?id=144510 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 144512] Please make timing of auto-save a per-document action
https://bugs.documentfoundation.org/show_bug.cgi?id=144512 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 127688] Dotted chapter numbering crashes Writer under Linux
https://bugs.documentfoundation.org/show_bug.cgi?id=127688 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103370] [META] Outline/Chapter numbering bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103370 Bug 103370 depends on bug 127688, which changed state. Bug 127688 Summary: Dotted chapter numbering crashes Writer under Linux https://bugs.documentfoundation.org/show_bug.cgi?id=127688 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127688] Dotted chapter numbering crashes Writer under Linux
https://bugs.documentfoundation.org/show_bug.cgi?id=127688 --- Comment #12 from QA Administrators --- Dear Wolfgang Glas, 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 77845] FILEOPEN: MS compatibility pack created DOC - Table incorrectly imported with an additional column (OK for DOCX and MSO created DOC)
https://bugs.documentfoundation.org/show_bug.cgi?id=77845 --- Comment #13 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://kiwiirc.com/nextclient/irc.freenode.net/#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 140903] EDITING: Conditional formatting is lost after deleting rows referenced in a chart
https://bugs.documentfoundation.org/show_bug.cgi?id=140903 --- Comment #4 from QA Administrators --- Dear txcsharppro, 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 49893] FILEOPEN: RTF: Image in header not displayed
https://bugs.documentfoundation.org/show_bug.cgi?id=49893 --- Comment #18 from QA Administrators --- Dear Jesus Corrius, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 50743] FORMATTING: Highlighting scrolls automatically
https://bugs.documentfoundation.org/show_bug.cgi?id=50743 --- Comment #14 from QA Administrators --- Dear tomcb, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 38011] [UI] Object with no left spacing gives wrong behavior when exit
https://bugs.documentfoundation.org/show_bug.cgi?id=38011 --- Comment #14 from QA Administrators --- Dear Laurent BP, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 127340] FORMATTING: Hyperlink should wrap in cell like normal text
https://bugs.documentfoundation.org/show_bug.cgi?id=127340 --- Comment #5 from QA Administrators --- Dear Thomas Lendo, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 112728] FILEOPEN: DOC - Command "INCLUDEPICTURE" shown to the user
https://bugs.documentfoundation.org/show_bug.cgi?id=112728 --- Comment #7 from QA Administrators --- Dear Mike, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 119891] Scanner dialog has no Help button
https://bugs.documentfoundation.org/show_bug.cgi?id=119891 --- Comment #3 from QA Administrators --- Dear Olivier Hallot, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 102196] EDITING Animating multi-line text misbehaves in sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=102196 --- Comment #8 from QA Administrators --- Dear Katarina Behrens (CIB), 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://kiwiirc.com/nextclient/irc.freenode.net/#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 103030] [META] Navigator sidebar deck and floating window
https://bugs.documentfoundation.org/show_bug.cgi?id=103030 Bug 103030 depends on bug 95378, which changed state. Bug 95378 Summary: Navigator does not select/highlight names of images, objects, tables etc that get focus, also not with Content View activated https://bugs.documentfoundation.org/show_bug.cgi?id=95378 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/source
sw/source/uibase/utlui/content.cxx | 41 + 1 file changed, 41 insertions(+) New commits: commit cdc1f41d4530ad3ec553d90dad803bc5b940656c Author: Jim Raykowski AuthorDate: Sat Sep 25 21:56:48 2021 -0800 Commit: Jim Raykowski CommitDate: Thu Sep 30 05:06:00 2021 +0200 tdf#95378 Writer Navigator: Track bookmarks Resolves bookmark tracking part of the enhancement request. Makes the Navigator content tree highlight the corresponding bookmark item of the first bookmark at the currrent cursor position in the document if there is one. Change-Id: Ida9f512eda9630bd6f1e5db1658715823644969d Reviewed-on: https://gerrit.libreoffice.org/c/core/+/122619 Tested-by: Jenkins Reviewed-by: Jim Raykowski diff --git a/sw/source/uibase/utlui/content.cxx b/sw/source/uibase/utlui/content.cxx index ae46fe4272c6..954ac752c22f 100644 --- a/sw/source/uibase/utlui/content.cxx +++ b/sw/source/uibase/utlui/content.cxx @@ -99,6 +99,10 @@ #include +#include +#include +#include + #define CTYPE_CNT 0 #define CTYPE_CTT 1 @@ -3408,6 +3412,43 @@ void SwContentTree::UpdateTracking() return; } +// bookmarks - track first bookmark at cursor +SwDoc* pDoc = m_pActiveShell->GetDoc(); +uno::Reference xBookmarksSupplier(pDoc->GetDocShell()->GetBaseModel(), + uno::UNO_QUERY); +uno::Reference xBookmarks(xBookmarksSupplier->getBookmarks(), + uno::UNO_QUERY); +sal_Int32 nBookmarkCount = xBookmarks->getCount(); +if (nBookmarkCount && !(m_bIsRoot && m_nRootType != ContentTypeId::BOOKMARK)) +{ +SwPaM* pCursor = pDoc->GetEditShell()->GetCursor(); +uno::Reference xRange( +SwXTextRange::CreateXTextRange(*pDoc, *pCursor->GetPoint(), nullptr)); +for (sal_Int32 i = 0; i < nBookmarkCount; ++i) +{ +uno::Reference bookmark; +xBookmarks->getByIndex(i) >>= bookmark; +try +{ +uno::Reference bookmarkRange = bookmark->getAnchor(); +uno::Reference xTextRangeCompare(xRange->getText(), + uno::UNO_QUERY); +if (xTextRangeCompare.is() +&& xTextRangeCompare->compareRegionStarts(bookmarkRange, xRange) != -1 +&& xTextRangeCompare->compareRegionEnds(xRange, bookmarkRange) != -1) +{ +uno::Reference xBookmark(bookmark, uno::UNO_QUERY); +lcl_SelectByContentTypeAndName(this, *m_xTreeView, + SwResId(STR_CONTENT_TYPE_BOOKMARK), + xBookmark->getName()); +return; +} +} +catch (const lang::IllegalArgumentException&) +{ +} +} +} // references if (SwContentAtPos aContentAtPos(IsAttrAtPos::RefMark); m_pActiveShell->GetContentAtPos(m_pActiveShell->GetCursorDocPos(), aContentAtPos) &&
[Libreoffice-bugs] [Bug 144818] New: Attempting to resize Style window (or others) causes hang.
https://bugs.documentfoundation.org/show_bug.cgi?id=144818 Bug ID: 144818 Summary: Attempting to resize Style window (or others) causes hang. Product: LibreOffice Version: 7.2.1.2 release Hardware: x86 (IA32) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rob...@tachez.com Attempting to resize Properties / Styles / ... window on right hand side causes a looping issue that hangs the process. It can only be killed with the Task Manager or ProcExp (SysInternals). Version: 7.2.1.2 (x64) / LibreOffice Community Build ID: 87b77fad49947c1441b67c559c339af8f3517e22 CPU threads: 16; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL Steps to reproduce: Open LibreOffice Writer Click on divider between document and Style Window (on right side). <-> resize icon remains lit and program is hung. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: i18npool/source svl/source
i18npool/source/calendar/calendar_gregorian.cxx | 53 svl/source/numbers/zforlist.cxx | 20 - svl/source/numbers/zformat.cxx | 32 -- 3 files changed, 83 insertions(+), 22 deletions(-) New commits: commit ebc454ad4eb1f4cd4d84a7db367bb71a457c4e5c Author: Eike Rathke AuthorDate: Wed Sep 29 23:14:18 2021 +0200 Commit: Eike Rathke CommitDate: Thu Sep 30 02:04:01 2021 +0200 Resolves: tdf#144697 Format out-of-bounds date(+time) as #FMT error i.e. < -32768-01-01 or > 32767-12-31 They couldn't be input or stored as proleptic Gregorian in file formats anyway. Additionally in i18npool handle the absolute year values casting conversion int32 <-> int16 where era 0 BCE year 32768 is fielded as -32768 but still is a valid year for our proleptic Gregorian, so it isn't displayed as --32768. Change-Id: Ifdd482f07e04c2a4296fd0556bbef7f1d3e15676 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/122835 Reviewed-by: Eike Rathke Tested-by: Jenkins diff --git a/i18npool/source/calendar/calendar_gregorian.cxx b/i18npool/source/calendar/calendar_gregorian.cxx index 6a1dad685309..df998b3c6cf3 100644 --- a/i18npool/source/calendar/calendar_gregorian.cxx +++ b/i18npool/source/calendar/calendar_gregorian.cxx @@ -127,6 +127,22 @@ using namespace ::com::sun::star::lang; namespace i18npool { +// Cast positive int32 values to signed int16, needed for +// fieldValue[CalendarFieldIndex::YEAR] where absolute value of an era year may +// be 32768 that with static_cast becomes -32768, which we also +// do here but indicating places in a controlled way to map back. +static inline sal_Int16 cast32To16( sal_Int32 a ) +{ +// More than uint16 can't be handled, should not occur. +assert(a >= 0 && a < static_cast(SAL_MAX_INT16) - static_cast(SAL_MIN_INT16)); +return static_cast(a); +} +// And back. +static inline sal_Int32 cast16To32( sal_Int16 i ) +{ +return static_cast(static_cast(i)); +} + Calendar_gregorian::Calendar_gregorian() : mxNatNum(new NativeNumberSupplierService) { @@ -409,10 +425,11 @@ void Calendar_gregorian::mapFromGregorian() if (!eraArray) return; -sal_Int16 e, y, m, d; +sal_Int16 e, m, d; +sal_Int32 y; e = fieldValue[CalendarFieldIndex::ERA]; -y = fieldValue[CalendarFieldIndex::YEAR]; +y = cast16To32(fieldValue[CalendarFieldIndex::YEAR]); m = fieldValue[CalendarFieldIndex::MONTH] + 1; d = fieldValue[CalendarFieldIndex::DAY_OF_MONTH]; @@ -427,7 +444,7 @@ void Calendar_gregorian::mapFromGregorian() fieldValue[CalendarFieldIndex::ERA] = e; fieldValue[CalendarFieldIndex::YEAR] = -sal::static_int_cast( (e == 0) ? (eraArray[0].year - y) : (y - eraArray[e-1].year + 1) ); +cast32To16( (e == 0) ? (eraArray[0].year - y) : (y - eraArray[e-1].year + 1) ); } #define FIELDS ((1 << CalendarFieldIndex::ERA) | (1 << CalendarFieldIndex::YEAR)) @@ -436,14 +453,15 @@ void Calendar_gregorian::mapFromGregorian() void Calendar_gregorian::mapToGregorian() { if (eraArray && (fieldSet & FIELDS)) { -sal_Int16 y, e = fieldValue[CalendarFieldIndex::ERA]; +sal_Int16 e = fieldValue[CalendarFieldIndex::ERA]; +sal_Int32 y; if (e == 0) -y = sal::static_int_cast( eraArray[0].year - fieldValue[CalendarFieldIndex::YEAR] ); +y = eraArray[0].year - cast16To32(fieldValue[CalendarFieldIndex::YEAR]); else -y = sal::static_int_cast( eraArray[e-1].year + fieldValue[CalendarFieldIndex::YEAR] - 1 ); +y = eraArray[e-1].year + cast16To32(fieldValue[CalendarFieldIndex::YEAR] - 1); fieldSetValue[CalendarFieldIndex::ERA] = y <= 0 ? 0 : 1; -fieldSetValue[CalendarFieldIndex::YEAR] = (y <= 0 ? 1 - y : y); +fieldSetValue[CalendarFieldIndex::YEAR] = cast32To16(y <= 0 ? 1 - y : y); fieldSet |= FIELDS; } } @@ -664,7 +682,7 @@ Calendar_gregorian::isValid() // NatNum4 NatNum9/9/11/11 static sal_Int16 NatNumForCalendar(const css::lang::Locale& aLocale, -sal_Int32 nCalendarDisplayCode, sal_Int16 nNativeNumberMode, sal_Int16 value ) +sal_Int32 nCalendarDisplayCode, sal_Int16 nNativeNumberMode, sal_Int32 value ) { bool isShort = ((nCalendarDisplayCode == CalendarDisplayCode::SHORT_YEAR || nCalendarDisplayCode == CalendarDisplayCode::LONG_YEAR) && value >= 100) || @@ -883,7 +901,8 @@ Calendar_gregorian::getDisplayString( sal_Int32 nCalendarDisplayCode, sal_Int16 OUString Calendar_gregorian::getDisplayStringImpl( sal_Int32 nCalendarDisplayCode, sal_Int16 nNativeNumberMode, bool bEraMode ) { -sal_Int16 value = getValue(sal::static_int_cast( DisplayCode2FieldIndex(nCalendarDisplayCode) )); +sal_Int32 value = cast16To32( getValue( sal::static_int_cast( +
Reg: Disabling macro in Docx to pdf conversion
Hello Techies, We have a requirement to convert Docx to PDF. And Libreoffice is doing an amazing job in converting doc files to pdf. But we see a challenge in converting macro enabled word documents. The first page of the converted pdf is blank with just the footer information. For example a 3 page docx is converted to 4 page pdf with the first page having only the footer information and dynamic page numbers. I am converting in command mode using the below *soffice.bin --headless --convert-to pdf "abc.docx" --outdir "abc/";* So is there a way we can ignore or disable the macro in the document and convert to pdf in the libre office or at least have the macro pages at the end of the document? Appreciate your help in resolving this issue.Thank you. Regards, Chiru
[Libreoffice-bugs] [Bug 140992] Direct input through copy and paste to table is lost
https://bugs.documentfoundation.org/show_bug.cgi?id=140992 Aron Budea changed: What|Removed |Added Keywords|bibisectRequest |bibisected, bisected --- Comment #7 from Aron Budea --- This can be reproduced in Linux with VCL plugin 'gen', and has started from the following commit, bibisected using repo bibisect-linux-64-7.1. Adding CC: to Caolán McNamara. https://cgit.freedesktop.org/libreoffice/core/commit/?id=a751d9c414fc63f36ae4b54b8adbaba042b31f60 author Caolán McNamara 2020-07-01 17:00:44 +0100 committer Caolán McNamara 2020-07-02 20:22:05 +0200 weld FormattedControl -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129062] [META] Skia library bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=129062 V Stuart Foote changed: What|Removed |Added Depends on||144763 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=144763 [Bug 144763] icons degrade Skia Vulkan rendering on nVidia MX130 with 462.376 driver -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144763] icons degrade Skia Vulkan rendering on nVidia MX130 with 462.376 driver
https://bugs.documentfoundation.org/show_bug.cgi?id=144763 V Stuart Foote changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 Summary|icons degrade |icons degrade Skia Vulkan ||rendering on nVidia MX130 ||with 462.376 driver Blocks||129062 --- Comment #8 from V Stuart Foote --- OK, thanks for posting. Seems your issue is with Skia Vulkan rendering on the nVidia M1X30 GPU. You should also have graphics support from the UHD Graphics 620 on the i7-8565U CPU, but on HP laptops it can a a challenge to assign applications to either the onboard GPU or the discrete GPU. One thing before moving on to a 7.2.2 build might be to update the nVidia graphics driver for the MX130. nVidia lists 472.12 as the current driver, while you look to still be on the 462.xx driver--if your HP laptop allows you to update, the more current Vulkan driver *may* help with the issues here. >From OPs skia.log RenderMethod: vulkan Vendor: 0x10de Device: 0x174d API: 1.2.155 Driver: 462.376.0 DeviceType: discrete DeviceName: GeForce MX130 Denylisted: no Otherwise, if functioning well with Skia Vulkan disabled and just using Skia software rendering as noted--you should be functional. Let us know if there are improvements with updated drivers, and/or a move to the 7.2.2 build. Personally I would pass on the 7.1.6 release build--we know there were build issues requiring an out of schedule 7.1.7 build and release. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=129062 [Bug 129062] [META] Skia library bugs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144669] Tick box surrounded by black background in form displaying data source view
https://bugs.documentfoundation.org/show_bug.cgi?id=144669 Aron Budea changed: What|Removed |Added CC||thorsten.wagne...@gmail.com See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||8122 Keywords||bibisected --- Comment #7 from Aron Budea --- (In reply to psidiumcode from comment #5) > Bisected with bisect repo mac64-7.2: > > 73381f7077e114b39dc2c46344d0366c7254de2e is the first bad commit > commit 73381f7077e114b39dc2c46344d0366c7254de2e > Author: libreoffice > Date: Fri Mar 26 12:32:18 2021 +0100 Thanks for bibisecting, psidiumcode! Adding CC: to Thorsten Wagner. https://cgit.freedesktop.org/libreoffice/core/commit/?id=1a167625314bf36b735176ed488e6ba9b5e9b675 author Thorsten Wagner2021-01-10 23:49:25 +0100 committer Tor Lillqvist2021-01-17 19:21:15 +0100 tdf#138122 Add window scaling for retina displays on macOS -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144542] [DOCUMENTATION] Please describe line spacing in detail
https://bugs.documentfoundation.org/show_bug.cgi?id=144542 --- Comment #3 from Rafael Lima --- @Regina, can this information be found anywhere using a macro? Which property of a Paragraph or TextPortion would store this information? I did my best trying to find it, but was not successful. I was trying to instantiate the Canvas service [1] to get a "XCanvasFont" object [2] and call its getFontMetrics() object. Maybe this would reveal the desired information. This would return a FontMetrics struct [3] which contains information about leading. However, I was not successful instantiating the Canvas service through a macro, so the method was unreachable. [1] https://api.libreoffice.org/docs/idl/ref/servicecom_1_1sun_1_1star_1_1rendering_1_1Canvas.html [2] https://api.libreoffice.org/docs/idl/ref/interfacecom_1_1sun_1_1star_1_1rendering_1_1XCanvasFont.html [3] https://api.libreoffice.org/docs/idl/ref/structcom_1_1sun_1_1star_1_1rendering_1_1FontMetrics.html -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144817] New: Navigator: Disable Sections tracking option
https://bugs.documentfoundation.org/show_bug.cgi?id=144817 Bug ID: 144817 Summary: Navigator: Disable Sections tracking option Product: LibreOffice Version: 7.3.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Keywords: regression Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: genericinet+libreoffice@gmail.com CC: rayk...@gmail.com Created attachment 175383 --> https://bugs.documentfoundation.org/attachment.cgi?id=175383=edit document with multiple sections and embedded headings Sections are not automatically tracked in the latest release candidate version 7.2.2.1. But in the 7.3 alpha, they are being tracked. This will be very helpful in complex documents when wanting to find a particular section so that the properties can be edited. But just as with the Table tracking (bug 144335), an option needs to be available to turn off the automatic tracking when the Content Navigation View is disabled. In a complex document, it is extremely irritating to have the navigator jump away from the Headings outline, even though the section might have its own headings embedded in it. Therefore, even though this feature is very helpful in certain contexts, I'm also marking this as a regression, since it began with 7.3 alpha and is not what is expected in most uses. It would be also helpful if these tracking options could be saved on a per document basis. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144763] icons degrade
https://bugs.documentfoundation.org/show_bug.cgi?id=144763 --- Comment #7 from Marta Woods --- I do not know how to disable the Vulkan rendering; hopefully it was your instructions on forcing Skia. I did go to Tools -> Options -> View and added the check for "Force Skia software rendering" . That appears to have taken care of the problem. I snipped and pasted several times into a document and neither the document nor a spreadsheet had the icon problem. I will download 7.2.2 tomorrow using the link you provided and give it a try. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144763] icons degrade
https://bugs.documentfoundation.org/show_bug.cgi?id=144763 --- Comment #6 from Marta Woods --- Created attachment 175382 --> https://bugs.documentfoundation.org/attachment.cgi?id=175382=edit msinfo32 results the results from msinfo32.exe -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144814] Settings that are stored in the document should be marked as such
https://bugs.documentfoundation.org/show_bug.cgi?id=144814 --- Comment #2 from John --- > this because we aren't going to the document at this moment of time a typo. There should be > this because we aren't going to save the document at this moment of time -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 144814] Settings that are stored in the document should be marked as such
https://bugs.documentfoundation.org/show_bug.cgi?id=144814 --- Comment #2 from John --- > this because we aren't going to the document at this moment of time a typo. There should be > this because we aren't going to save the document at this moment of time -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 144763] icons degrade
https://bugs.documentfoundation.org/show_bug.cgi?id=144763 --- Comment #5 from Marta Woods --- Created attachment 175381 --> https://bugs.documentfoundation.org/attachment.cgi?id=175381=edit skia log the requested skia log -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123419] Scrolling around in a document with lots of comment shown very slow compared to 4.4.7.2
https://bugs.documentfoundation.org/show_bug.cgi?id=123419 --- Comment #6 from Carlo --- confirm in Version: 7.2.2.1 (x64) / LibreOffice Community Build ID: 0e408af0b27894d652a87aa5f21fe17bf058124c CPU threads: 12; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: it-IT (it_IT); UI: it-IT Calc: threaded After View -> Comments it almost impossible to scroll Sheet 1 is completely full of comments and many cells are covered... is it a real problem in real life? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144814] Settings that are stored in the document should be marked as such
https://bugs.documentfoundation.org/show_bug.cgi?id=144814 Telesto changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||tele...@surfxs.nl -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 144814] Settings that are stored in the document should be marked as such
https://bugs.documentfoundation.org/show_bug.cgi?id=144814 Telesto changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||tele...@surfxs.nl -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 121059] Scrolling down in print preview causes memory usage to increase rapidly
https://bugs.documentfoundation.org/show_bug.cgi?id=121059 --- Comment #8 from Telesto --- (In reply to Carlo from comment #7) > Duplicated? > See https://bugs.documentfoundation.org/show_bug.cgi?id=121058#c4 The big question: I reported those intentionally as separate bugs, because I'm not 100% sure. Have seen enough bug looking the same, but being different in the sense of hitting slightly different area of code. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121059] Scrolling down in print preview causes memory usage to increase rapidly
https://bugs.documentfoundation.org/show_bug.cgi?id=121059 --- Comment #7 from Carlo --- Duplicated? See https://bugs.documentfoundation.org/show_bug.cgi?id=121058#c4 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121058] Memory usage increasing from 133 to +/- 255 MB after scrolling down with page down
https://bugs.documentfoundation.org/show_bug.cgi?id=121058 --- Comment #4 from Carlo --- Version: 7.2.2.1 (x64) / LibreOffice Community Build ID: 0e408af0b27894d652a87aa5f21fe17bf058124c CPU threads: 12; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: it-IT (it_IT); UI: it-IT Calc: threaded Actual Results: Scrolling the document down and up, memory usage increase rapidly. In my case I reached 326 MB. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136495] Documentation on how to inset a page with different orientation in between pages without affecting the layout of the previous or next pages
https://bugs.documentfoundation.org/show_bug.cgi?id=136495 Telesto changed: What|Removed |Added Resolution|NOTABUG |--- Summary|Hard to insert a page with |Documentation on how to |different in between pages |inset a page with different |without affecting page |orientation in between |style of other pages|pages without affecting the ||layout of the previous or ||next pages Component|Writer |Documentation CC||olivier.hallot@libreoffice. ||org Status|RESOLVED|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136495] Hard to insert a page with different in between pages without affecting page style of other pages
https://bugs.documentfoundation.org/show_bug.cgi?id=136495 --- Comment #6 from Telesto --- Created attachment 175380 --> https://bugs.documentfoundation.org/attachment.cgi?id=175380=edit Example file (In reply to Dieter from comment #5) > Perhaps it wold be useful to add information to following help page: > https://help.libreoffice.org/7.3/en-GB/text/swriter/guide/page_break. > html?=WRITER=WIN > Some informations are provided here: > https://help.libreoffice.org/7.3/en-GB/text/swriter/01/0401. > html?=WRITER=WIN This probably more productive approach.. After reading you're comment I recall nagged about this from different angels and with success various people (UX/developers). I see inserting or changing an existing page from Portrait to Landscape (and back) as the most common case Topics of most interest (from my perspective) * Changing the first page to 'Landscape' where the next pages should be Portrait * Insert a new page, with different orientation between existing pages * Change orientation of existing page in a document without affecting the reset The issue being that you have multiple tools which look a good candidate at the start, but don't work out as expected. No go * Format -> Page Style -> Page Tab -> Landscape (makes the default Landscape * Format -> Page Style -> Organizer Tab -> Next Style -> Landscape (not intended to be used; Word Model? * Double clicking a page style inside sidebar with cursor some page -> Problem of the scope of the change.. Not limited to single page but some range (if page break has no explicit style, those will be included too) Route A; Insert -> Manual Page break -> and using explicit page style was most productive route. Route B: CTRL+A Enter -> Soft break. Next Format -> Paragraph -> Text flow tab -> Check With page style -> Landscape --- Side-kick Another topic to include is DOCX conversion.. Defining a style for a page explicitly creates pretty unworkable end result. Every page getting a unique Style :-(; so Page Style Portrait applied to different pages becomes "Converted1" for page 1 "Converted2" for page to " Converted 3" for page 3 and so on. [Save attached file to DOCX; and look at Format -> Paragraph -> Text flow tab. Consequence A: The usage of styles being ruined. There is no single page style (Landscape) anymore where can change something which affects all pages with same style (every page gets unique style] Consequence B: The generic name makes really uninformative what so special about the style. [No clue if DOCX being capable to store style names; doesn't look that way] LibO Page Style model isn't MSO approach :-(. And hell for intercompatibility -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144816] Collabora Office: on Android some menus in Czech environment are in English
https://bugs.documentfoundation.org/show_bug.cgi?id=144816 Michael Kůr changed: What|Removed |Added Summary|Collabora Office: some |Collabora Office: on |menus in Czech environment |Android some menus in Czech |are in English |environment are in English -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144816] New: Collabora Office: some menus in Czech environment are in English
https://bugs.documentfoundation.org/show_bug.cgi?id=144816 Bug ID: 144816 Summary: Collabora Office: some menus in Czech environment are in English Product: LibreOffice Version: 6.4 all versions Hardware: ARM OS: Android Status: UNCONFIRMED Severity: normal Priority: medium Component: Android Editor Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: michael.ku...@gmail.com In the Collabora Office there are some of the menus (so far I found that it is in number of words menu and in paragraph settings) in English even if the system environment is Czech and rest of the aplplication is in Czech too. Steps to reproduce (number of words): 1) in Android se Czech as a default language, 2) run CO - it should be in Czech, 3) open any text document 4) navigate to menu in the right upper corner, 5) tap on the menu "word count" 6) you will see that this sreen is in English System information: Model: Lenovo TB-7304F OS: Android System language: Czech App version: 6.4.3. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144589] Down arrow has weird extra lines on right and top
https://bugs.documentfoundation.org/show_bug.cgi?id=144589 medmedin2014 changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #2 from medmedin2014 --- I tried with Breeze Dark, Breeze Light, Breath2, Breath2 Dark, Sweet, Arch KDE and they all show the same problem. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144815] New: Collabora Office on Android does not prevent from entering invalid filename
https://bugs.documentfoundation.org/show_bug.cgi?id=144815 Bug ID: 144815 Summary: Collabora Office on Android does not prevent from entering invalid filename Product: LibreOffice Version: 6.4 all versions Hardware: ARM OS: Android Status: UNCONFIRMED Severity: normal Priority: medium Component: Android Editor Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: michael.ku...@gmail.com Collabora Office allows enter invalid filename. When someone attempts to type file name while creating document, which is too long or contains disallowed characters, the application does not show any warning and tries to create that file. The application get stuck on animation with a small rotating circle. However it does not freeze completely, because, the proces can be interrupted by pressing back button on system tray. The bug is not critical, but it can be annoying, because less experienced users may not know what is wrong and may think that the app does not work. Steps to reproduce: 1) On the right bottom corner click on the + button, 2) select type of documents, 3) select directory, 4) type long or filename with disallowed characers (such as :!), 5) click on save button. System information: OS: Android Device: Lenovo TB-7304F App version: 6.4.3. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143221] Menu/Toolbar entry to show hidden character
https://bugs.documentfoundation.org/show_bug.cgi?id=143221 S.Zosgornik changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||7722 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107722] UNO command to toggle hidden text
https://bugs.documentfoundation.org/show_bug.cgi?id=107722 S.Zosgornik changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||3221 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144697] Dates prior to the program's limit should display #FMT
https://bugs.documentfoundation.org/show_bug.cgi?id=144697 Eike Rathke changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |er...@redhat.com |desktop.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144814] Settings that are stored in the document should be marked as such
https://bugs.documentfoundation.org/show_bug.cgi?id=144814 --- Comment #1 from John --- > The problem is that some of these settings are stored in the > document/template, and some of them are stored in the > application itself. The problem is that there is no hint to the user which of these settings are stored where. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144814] Settings that are stored in the document should be marked as such
https://bugs.documentfoundation.org/show_bug.cgi?id=144814 John changed: What|Removed |Added Severity|normal |enhancement -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144814] New: Settings that are stored in the document should be marked as such
https://bugs.documentfoundation.org/show_bug.cgi?id=144814 Bug ID: 144814 Summary: Settings that are stored in the document should be marked as such Product: LibreOffice Version: 7.1.5.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: johnsmithbeat...@gmail.com Description: There is a very serious UI problem with LO settings. The problem is that some of these settings are stored in the document/template, and some of them are stored in the application itself. **It is assumed you have a new LO user profile and LO uses US measurement units (specifically, inches) by default. We will test the Writer application.** Open "Tools > Options > LibreOffice Writer > General" and notice the following two settings: "Measurement unit" and "Tab stops". a) The value of "Tab stops", if you change it to a custom value and then save the document, will be stored in the document. b) ... While the value of "Measurement unit" is always stored in the application. c) Ah! And if you change the value of "Tab stops" to a custom value **without** saving the document, this custom value will be stored in the application and not in the document. And please notice that there are no hints to the user that these settings are stored so differently. And here is how confusing it can be in the real life: 1. Create an unsaved document. 2. Tools > Options > LibreOffice Writer > General: 1. Measurement unit = Change it from "Inch" to "Centimeter" 2. Tab stops = Change it from "1.25 cm" to "1.00 cm" HERE IS WHAT IS CURRENTLY GOING ON: * "Meas. unit" is stored in the application (as always) * "Tab stops" are stored in the application as well (this because we aren't going to the document at this moment of time, see the next step.) 3. Close the document without saving it. 4. Create another document. Notice the settings are the ones you have set up: "Centimeter" and "1.00 cm". This is fine. 5. Save the document. HERE IS WHAT IS CURRENTLY GOING ON: * "Meas. unit" is stored in the application (as always) * "Tab stops" are stored in the document (since you have saved the document) 6. Change the values to "Millimeter" and "6 mm" HERE IS WHAT IS CURRENTLY GOING ON: * "Meas. unit" is stored in the application (as always) * "Tab stops" are stored in the application as well (this because we aren't going to the document at this moment of time, see the next step.) 7. Close the document without saving it. 8. Open the saved file. Its values will be "Millimeter" and "10 mm" This is really confusing even for many experienced users who already aware of how this works. This is because the are many different settings and users **cannot** remember which of them are stored where. And so they cannot predict how some settings will change if you change the template. Or if you open the document on another computer. And this is much worse for many people who aren't so experienced. It seems to me that settings that are stored in the document and not in the application Solution-1: Should be "marked" as such. For example, instead of "Tab stops" it should be "Tab stops [D]" (where D stands for "document"). or Solution-2: They should be moved to a separate section. Steps to Reproduce: see above Actual Results: see above Expected Results: see above Reproducible: Always User Profile Reset: No Additional Info: see above -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144387] Numering schema don't work for not headings fonts from second level.
https://bugs.documentfoundation.org/show_bug.cgi?id=144387 deepoose2...@gmail.com changed: What|Removed |Added CC||deepoose2...@gmail.com --- Comment #1 from deepoose2...@gmail.com --- I can reproduce this to stable and master build. But not sure if it is by design. Version: 7.2.1.2 (x64) / LibreOffice Community Build ID: 87b77fad49947c1441b67c559c339af8f3517e22 CPU threads: 8; OS: Windows 10.0 Build 17763; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: a78190da867864485b5d0a91238616bd4090b5b5 CPU threads: 8; OS: Windows 10.0 Build 17763; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144806] LibreOffice does not start after installing version 7.1.6 with Dutch help pack 7.1.6.
https://bugs.documentfoundation.org/show_bug.cgi?id=144806 V Stuart Foote changed: What|Removed |Added CC||vstuart.fo...@utsa.edu Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from V Stuart Foote --- likely the build issue of bug 144598 does disabling Skia rendering (safe mode boot, or via profile stanza [1]) launch? if so, patched for a 7.1.7 release, or available now in the 7.2.2 rc1 build =-ref-= add this value to user profile registrymodifications.xcu false found in C:\Users\\AppData\Roaming\LibreOffice\4\user -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144792] installed new version 7.1.6_win_x64.msi and new version 7.1.6.win_x64 helpack_en-gb.msi would not open
https://bugs.documentfoundation.org/show_bug.cgi?id=144792 V Stuart Foote changed: What|Removed |Added Ever confirmed|0 |1 CC||vstuart.fo...@utsa.edu Status|UNCONFIRMED |NEEDINFO --- Comment #1 from V Stuart Foote --- likely the build issue of bug 144598 does disabling Skia rendering (safe mode boot, or via profile stanza [1]) launch? if so, patched for a 7.1.7 release, or available now in the 7.2.2 rc1 build =-ref-= add this value to user profile registrymodifications.xcu false found in C:\Users\\AppData\Roaming\LibreOffice\4\user -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144607] Bibliography database option does not open when selected
https://bugs.documentfoundation.org/show_bug.cgi?id=144607 --- Comment #22 from Ismael Luceno --- Created attachment 175379 --> https://bugs.documentfoundation.org/attachment.cgi?id=175379=edit patch - first try -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144784] UI draws with smaller font size than system default
https://bugs.documentfoundation.org/show_bug.cgi?id=144784 --- Comment #11 from Charles C --- It was actually rendering at 7px tall, not 7 points - I had already verified that. So the text was a little under 2mm high. Now I have installed the libreoffice-gtk3 package (it doesn't replace any other packages, it just gets installed alongside them), and the text is indeed 9px high, so I think it's now respecting the font preferences set. As I say, I have no idea why this wasn't installed along with the rest of the libreoffice-* packages that get installed by Debian. I'm not sure what would have made this issue and the fix more discoverable. Perhaps if libreoffice finds itself running in plain x11 mode when it knows it's running on top of a Gnome/KDE/whatever desktop it could alert the user or something. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144757] In Options - LibreOffice - Fonts - Font Settings for HTML, Basic and SQL Sources, Selecting an other font doesn't function.
https://bugs.documentfoundation.org/show_bug.cgi?id=144757 --- Comment #12 from Mike Kaganski --- (In reply to Alex Thurgood from comment #10) > > *** This bug has been marked as a duplicate of bug 117793 *** Alex, I fail to see how could this be a duplicate of that bug, which is not specific to macOS (is reported on Windows), not related to Basic, and is about missing functionality in Base? Basic IDE definitely follows the "Font Setting for HTML, Basic and SQL Sources" setting (which shows non-proportional fonts fine) on e.g. Version: 7.2.2.1 (x64) / LibreOffice Community Build ID: 0e408af0b27894d652a87aa5f21fe17bf058124c CPU threads: 12; OS: Windows 10.0 Build 19043; UI render: default; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: threaded. -- You are receiving this mail because: You are the assignee for the bug.
Minutes from the UX/design meeting 2021-Sep-29
Present: Bogan (muted), Heiko Comments: Sascha, Adolfo, Roman, Mike, Stuart Tickets/Topics * The Gallery popup option "Insert as Background" should appear only in Writer + https://bugs.documentfoundation.org/show_bug.cgi?id=144201 + fix it for Draw/Impress or remove completely => remove * Horizontal Ruler Comments button issue if in Zoom Factor Optimal or Fit Width + https://bugs.documentfoundation.org/show_bug.cgi?id=144419 + relying on this button makes no sense, eradicate it (Sascha) + requires a solution anyway (Adolfo) + View > Comments toggles the comments pane visibility and adjusts the optimal zoom accordingly (Heiko) + optimal means to hide the pane when collapsed => resolve WF * Writer: No "Settings" or "Advanced" button in a "Insert footnote" dialog window + https://bugs.documentfoundation.org/show_bug.cgi?id=144722 + agree (Roman) + rather introduce resp. refer to different footnote style (Dave) + reasonable argument but too many design variants clutter the list of styles; and more relevant not all foot/endnote options are paragraph style attributes (Heiko) + having a shortcut to the configuration dialog makes sense (Mike) => do it * [ACCESSIBILITY] Copy object caption contents to object name, alt and description + https://bugs.documentfoundation.org/show_bug.cgi?id=144375 + makes sense in particular for a11y request in bug 39558 (Stuart) + name is not random and used in the Navigator, description is meant for sources or similar additional information (Heiko) + for the alternative text it improves a11y but implementation should consider to not change existing text => do it * Paste Special Comments and Text conflict + https://bugs.documentfoundation.org/show_bug.cgi?id=139858 + workaround to add-paste comment only could be to use the add option (Heiko) + not intuitive (John) + paste special /formats and /objects (anchored to cell) only does exactly what is requested and makes the content bold, for example, while numbers and comment remains intact + same happens the other way around and when pasting numbers only into a cell with formatting or attached object those stay alive => treat comments as formula or objects and keep cell content OpenPGP_signature Description: OpenPGP digital signature
[Libreoffice-qa] Minutes from the UX/design meeting 2021-Sep-29
Present: Bogan (muted), Heiko Comments: Sascha, Adolfo, Roman, Mike, Stuart Tickets/Topics * The Gallery popup option "Insert as Background" should appear only in Writer + https://bugs.documentfoundation.org/show_bug.cgi?id=144201 + fix it for Draw/Impress or remove completely => remove * Horizontal Ruler Comments button issue if in Zoom Factor Optimal or Fit Width + https://bugs.documentfoundation.org/show_bug.cgi?id=144419 + relying on this button makes no sense, eradicate it (Sascha) + requires a solution anyway (Adolfo) + View > Comments toggles the comments pane visibility and adjusts the optimal zoom accordingly (Heiko) + optimal means to hide the pane when collapsed => resolve WF * Writer: No "Settings" or "Advanced" button in a "Insert footnote" dialog window + https://bugs.documentfoundation.org/show_bug.cgi?id=144722 + agree (Roman) + rather introduce resp. refer to different footnote style (Dave) + reasonable argument but too many design variants clutter the list of styles; and more relevant not all foot/endnote options are paragraph style attributes (Heiko) + having a shortcut to the configuration dialog makes sense (Mike) => do it * [ACCESSIBILITY] Copy object caption contents to object name, alt and description + https://bugs.documentfoundation.org/show_bug.cgi?id=144375 + makes sense in particular for a11y request in bug 39558 (Stuart) + name is not random and used in the Navigator, description is meant for sources or similar additional information (Heiko) + for the alternative text it improves a11y but implementation should consider to not change existing text => do it * Paste Special Comments and Text conflict + https://bugs.documentfoundation.org/show_bug.cgi?id=139858 + workaround to add-paste comment only could be to use the add option (Heiko) + not intuitive (John) + paste special /formats and /objects (anchored to cell) only does exactly what is requested and makes the content bold, for example, while numbers and comment remains intact + same happens the other way around and when pasting numbers only into a cell with formatting or attached object those stay alive => treat comments as formula or objects and keep cell content OpenPGP_signature Description: OpenPGP digital signature
[Libreoffice-bugs] [Bug 144669] Tick box surrounded by black background in form displaying data source view
https://bugs.documentfoundation.org/show_bug.cgi?id=144669 psidiumcode changed: What|Removed |Added Keywords|bibisectRequest |bisected -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144669] Tick box surrounded by black background in form displaying data source view
https://bugs.documentfoundation.org/show_bug.cgi?id=144669 --- Comment #6 from psidiumcode --- git bisect log: # bad: [20651168152192ab9e0f9d12a94228b24125b0d4] source sha:3d311c6d63eafbe2f76d6f1768dc3f675970a55a # good: [7ae9dc0eb055b3d88573a247cf3f756b06ad5cad] source sha:738bcf5e9a8c443d60c29c3a8068e8c16c72638a git bisect start 'master' 'oldest' # bad: [de3791b1403f4e466497581e5a49f06f94701dbb] source sha:9279dce41152ed692c125edfed4c80a7c28c7a0b git bisect bad de3791b1403f4e466497581e5a49f06f94701dbb # good: [156360b0cc59e95e1deb3f2b63c8572b055ff9a0] source sha:022f61e6bd876fbcbcefd63708bf4c7ee5063f3a git bisect good 156360b0cc59e95e1deb3f2b63c8572b055ff9a0 # bad: [c97f1de0178ec9b8e314df9e5c43ceca2e6fbc1e] source sha:86b192965ee8d625092b723337f6a65bdf34dcb7 git bisect bad c97f1de0178ec9b8e314df9e5c43ceca2e6fbc1e # bad: [d3951b89e6b7f631114b3aa866378788fe7f8877] source sha:167f4edc54bca5f62f098dcff2bff3cce4a51c58 git bisect bad d3951b89e6b7f631114b3aa866378788fe7f8877 # bad: [bf887f5547accfd8513351000cdbd7620a92de2b] source sha:6220d619b42b18cca7280174daed56aad5c82fce git bisect bad bf887f5547accfd8513351000cdbd7620a92de2b # bad: [62add0f516fea5072693b8dcf9dc2e91075d5ee1] source sha:3b3591d3c127c306f4d5f6bbb34118b03c3124c0 git bisect bad 62add0f516fea5072693b8dcf9dc2e91075d5ee1 # good: [ced5ab4d71d13cfe543a164bfc5b0bc3805e13f3] source sha:602a044014b55a5a1b1a5f0e96af603590ee899f git bisect good ced5ab4d71d13cfe543a164bfc5b0bc3805e13f3 # bad: [b00c689af48d3f973d91e7a6c3212cd25e0ebbbf] source sha:b6f574ad86316956cf27efec61af9cbda273e054 git bisect bad b00c689af48d3f973d91e7a6c3212cd25e0ebbbf # good: [8644b62f52c663eaa03691f3868eb56c53fa4600] source sha:ad55d51486264260a135b36c85973a728e006de7 git bisect good 8644b62f52c663eaa03691f3868eb56c53fa4600 # good: [6553109660ff34893fed1fba2a54d2fdfed1faee] source sha:79e471dc116f0b662e48d915d395d398057d137f git bisect good 6553109660ff34893fed1fba2a54d2fdfed1faee # bad: [deab522b3aa90a43f9b3c703894e8a014b08b33f] source sha:058ad4b900b5e0ee902f3e89ed121c2b5f8c58f1 git bisect bad deab522b3aa90a43f9b3c703894e8a014b08b33f # bad: [73381f7077e114b39dc2c46344d0366c7254de2e] source sha:1a167625314bf36b735176ed488e6ba9b5e9b675 git bisect bad 73381f7077e114b39dc2c46344d0366c7254de2e # good: [2538fbd480d71ad492642b8b02792cbdeda42a29] source sha:5bd90f7f5852056342f1a81a1285b474d468eadd git bisect good 2538fbd480d71ad492642b8b02792cbdeda42a29 # first bad commit: [73381f7077e114b39dc2c46344d0366c7254de2e] source sha:1a167625314bf36b735176ed488e6ba9b5e9b675 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144669] Tick box surrounded by black background in form displaying data source view
https://bugs.documentfoundation.org/show_bug.cgi?id=144669 --- Comment #5 from psidiumcode --- Bisected with bisect repo mac64-7.2: 73381f7077e114b39dc2c46344d0366c7254de2e is the first bad commit commit 73381f7077e114b39dc2c46344d0366c7254de2e Author: libreoffice Date: Fri Mar 26 12:32:18 2021 +0100 source sha:1a167625314bf36b735176ed488e6ba9b5e9b675 source sha:1a167625314bf36b735176ed488e6ba9b5e9b675 .../Contents/Frameworks/libvclplug_osxlo.dylib | Bin 792028 -> 801996 bytes .../Contents/Resources/config/images_breeze.zip| Bin 1888042 -> 1888042 bytes .../Resources/config/images_breeze_dark.zip| Bin 1883715 -> 1883715 bytes .../Resources/config/images_breeze_dark_svg.zip| Bin 1566710 -> 1566710 bytes .../Resources/config/images_breeze_svg.zip | Bin 1564232 -> 1564232 bytes .../Contents/Resources/config/images_colibre.zip | Bin 2757318 -> 2757318 bytes .../Resources/config/images_colibre_svg.zip| Bin 2883054 -> 2883054 bytes .../Resources/config/images_elementary.zip | Bin 4174032 -> 4174032 bytes .../Resources/config/images_elementary_svg.zip | Bin 5454875 -> 5454875 bytes .../Resources/config/images_karasa_jaga.zip| Bin 4879773 -> 4879773 bytes .../Resources/config/images_karasa_jaga_svg.zip| Bin 19303300 -> 19303300 bytes .../Contents/Resources/config/images_sifr.zip | Bin 2104813 -> 2104813 bytes .../Contents/Resources/config/images_sifr_dark.zip | Bin 2106689 -> 2106689 bytes .../Resources/config/images_sifr_dark_svg.zip | Bin 1756382 -> 1756382 bytes .../Contents/Resources/config/images_sifr_svg.zip | Bin 1752511 -> 1752511 bytes .../Contents/Resources/config/images_sukapura.zip | Bin 3040207 -> 3040207 bytes .../Resources/config/images_sukapura_svg.zip | Bin 4345422 -> 4345422 bytes LibreOffice.app/Contents/Resources/setuprc | 2 +- LibreOffice.app/Contents/Resources/versionrc | 2 +- 19 files changed, 2 insertions(+), 2 deletions(-) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144684] LibreOffice Calc 7.2.1.2 Linux Regression: Auto Filter Popup Is Without Any Function
https://bugs.documentfoundation.org/show_bug.cgi?id=144684 Gunter Ohrner changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #3 from Gunter Ohrner --- See attachment comment. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144684] LibreOffice Calc 7.2.1.2 Linux Regression: Auto Filter Popup Is Without Any Function
https://bugs.documentfoundation.org/show_bug.cgi?id=144684 Gunter Ohrner changed: What|Removed |Added CC||mails.bugs.documentfoundati ||on@gunter.ohrner.net --- Comment #2 from Gunter Ohrner --- Created attachment 175378 --> https://bugs.documentfoundation.org/attachment.cgi?id=175378=edit Example Document - try the auto filter. Ok, I attached a newly created example document - actually, no specific document is necessary. Every spreadsheet with auto filters exhibits the problem, the autofilters are unsuable. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144341] Unable to set alignment for hyperlinks in text boxes
https://bugs.documentfoundation.org/show_bug.cgi?id=144341 deepoose2...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||deepoose2...@gmail.com --- Comment #5 from deepoose2...@gmail.com --- Thank you for reporting the bug. I can confirm that the bug is reproducible in Version: 7.2.1.2 (x64) / LibreOffice Community Build ID: 87b77fad49947c1441b67c559c339af8f3517e22 CPU threads: 8; OS: Windows 10.0 Build 17763; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: a78190da867864485b5d0a91238616bd4090b5b5 CPU threads: 8; OS: Windows 10.0 Build 17763; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144784] UI draws with smaller font size than system default
https://bugs.documentfoundation.org/show_bug.cgi?id=144784 --- Comment #10 from V Stuart Foote --- (In reply to Charles C from comment #9) > With the libreoffice-gtk3 package installed, the contrast problem is gone - > the text is black-on-white as with other apps. > > However, the menu bar text is now 7px, while other applications appear to > respect the "Default font: Sans Regular 9pt" Gnome setting, as their menu > bars use 9px text. @Charles, we need to correct you here as you seem unclear. A font rendered on any screen at 5px or even 7px--pixels-- would be unreadable. Expect you mean points which are ppi independent. 5px or 7px would be even worse if on a HiDPI display with DPI greater than ~165 ppi that effectively shrinks a pixel--"a pixel 1/72" is a pixel at 72 dpi". But even on a legacy resolution 72 dpi screen a 5px font would be pretty much unreadable. Your ~101 dpi display would be worse, but close to the internal LO 100% UI scaling at 96 ppi. Maybe check with a utility like xruler, kruler, screenruler, etc. (I use MioPlanets Pixel Ruler for Windows) to measure the actual pixel heights of LibreOffice UI fonts--expect they will be above 10px at the ppi of your display with no additional os/DE scaling. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144813] Ribbon (drop down box) and sidebar options - rapid blinking/flashing.
https://bugs.documentfoundation.org/show_bug.cgi?id=144813 Chris D changed: What|Removed |Added CC||c.derm...@blueyonder.co.uk Ever confirmed|0 |1 Status|UNCONFIRMED |NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144813] New: Ribbon (drop down box) and sidebar options - rapid blinking/flashing.
https://bugs.documentfoundation.org/show_bug.cgi?id=144813 Bug ID: 144813 Summary: Ribbon (drop down box) and sidebar options - rapid blinking/flashing. Product: LibreOffice Version: 7.2.1.2 release Hardware: x86 (IA32) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: c.derm...@blueyonder.co.uk Description: Libre Office writer. Within ribbon tabs: [Home] Font and sizes [Layout] Formatting The drop down boxes exhibit continuous rapid blinking/flashing, which get worse when the cursor is moved across the ribbon. Also, this same problem becomes manifest when any of the Sidebar options are selected. In addition, [Layout] Formatting, border appears to be missing for lower two boxes, I.e. shows a dashed line instead - ribbon may have to be widened slightly to show this lower border. Steps to Reproduce: 1. Open LO Writer 2. Initiate ribbon interface 3. Select either [Home] or [Layout]tab 4. Scan cursor anywhere across the ribbon 5. Click on sidebar settings and select any of the 8 available options Actual Results: When [Home] or [Layout] tab selected drop down boxes exhibit continuous rapid blinking/flashing. When any of the Sidebar options are selected (upon opening), the whole of the opened panel blinks/flashes in unison with the above drop down boxes. Expected Results: Stable drop down boxes and sidebar options - no blinking/flashing. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-GB Ubuntu package version: 1:7.2.1-0ubuntu0.18.04.1~lo1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136495] Hard to insert a page with different in between pages without affecting page style of other pages
https://bugs.documentfoundation.org/show_bug.cgi?id=136495 Dieter changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #5 from Dieter --- I confirm the behaviour, but I don't think, that this is a bug: Attached file has a page break, but this is a page break with no style (you can see this, if you edit page break). So it takes always the page style from the previous page. Therefore it changes to portrait, if you enter page break with default page style. If you assign page style landscape to the page break in the document, you'll get the expected result, if you insert page vbreak with default page style => RESOLVED NOTABUG Feel free to change it back with a short reasoning, if you disagree. Perhaps it wold be useful to add information to following help page: https://help.libreoffice.org/7.3/en-GB/text/swriter/guide/page_break.html?=WRITER=WIN Some informations are provided here: https://help.libreoffice.org/7.3/en-GB/text/swriter/01/0401.html?=WRITER=WIN -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127250] [META] Text formatting issues when inserting or overwriting
https://bugs.documentfoundation.org/show_bug.cgi?id=127250 Dieter changed: What|Removed |Added Depends on||144456 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=144456 [Bug 144456] overwriting a word in a clean styled para sets "character direct formatting" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 144456] overwriting a word in a clean styled para sets "character direct formatting"
https://bugs.documentfoundation.org/show_bug.cgi?id=144456 Dieter changed: What|Removed |Added Hardware|x86-64 (AMD64) |All Blocks||127250 Keywords||needsUXEval Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC||libreoffice-ux-advise@lists ||.freedesktop.org OS|Linux (All) |All --- Comment #3 from Dieter --- (In reply to goodgu...@zoho.com from comment #2) > dear Dieter, > > exactly! thank you for testing on 7.3 (i'm on 7.2.2.1 where this still > persists) > > regards. O. K. I set status to "NEW" then. cc: Design-Team for double-check, because I'm not sure for 100%, if this is a bug or expected result. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=127250 [Bug 127250] [META] Text formatting issues when inserting or overwriting -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 144456] overwriting a word in a clean styled para sets "character direct formatting"
https://bugs.documentfoundation.org/show_bug.cgi?id=144456 Dieter changed: What|Removed |Added Hardware|x86-64 (AMD64) |All Blocks||127250 Keywords||needsUXEval Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC||libreoffice-ux-advise@lists ||.freedesktop.org OS|Linux (All) |All --- Comment #3 from Dieter --- (In reply to goodgu...@zoho.com from comment #2) > dear Dieter, > > exactly! thank you for testing on 7.3 (i'm on 7.2.2.1 where this still > persists) > > regards. O. K. I set status to "NEW" then. cc: Design-Team for double-check, because I'm not sure for 100%, if this is a bug or expected result. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=127250 [Bug 127250] [META] Text formatting issues when inserting or overwriting -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144812] New: Textbox in caption frame wrongly positioned after DOCX export
https://bugs.documentfoundation.org/show_bug.cgi?id=144812 Bug ID: 144812 Summary: Textbox in caption frame wrongly positioned after DOCX export Product: LibreOffice Version: 4.4.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tele...@surfxs.nl Description: Textbox in caption frame wrongly positioned after DOCX export Steps to Reproduce: 1. open the attached file 2. Save as DOCX 3. File - reload Actual Results: Notice caption frame & text frame being split Expected Results: Inside the caption frame Reproducible: Always User Profile Reset: No Additional Info: Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: b60b6bfaafa1315e07108dba50f016975b619c59 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: en-US (nl_NL); UI: en-US Calc: CL and in 4.4.7.2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104449] [META] DOCX (OOXML) textbox-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104449 Bug 104449 depends on bug 136623, which changed state. Bug 136623 Summary: FILESAVE DOCX: Textboxes wrongly positioned after on file open (fine with DOC) https://bugs.documentfoundation.org/show_bug.cgi?id=136623 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136623] FILESAVE DOCX: Textboxes wrongly positioned after on file open (fine with DOC)
https://bugs.documentfoundation.org/show_bug.cgi?id=136623 Telesto changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Keywords|bibisectRequest, regression | Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144796] FILEOPEN DOCX Chart objects In Background property not read
https://bugs.documentfoundation.org/show_bug.cgi?id=144796 Telesto changed: What|Removed |Added Ever confirmed|0 |1 CC||tele...@surfxs.nl Status|UNCONFIRMED |NEW --- Comment #2 from Telesto --- Repro Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: b60b6bfaafa1315e07108dba50f016975b619c59 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: en-US (nl_NL); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144798] FILEOPEN DOCX Z-order of shape and chart incorrectly imported
https://bugs.documentfoundation.org/show_bug.cgi?id=144798 Telesto changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144798] FILEOPEN DOCX Z-order of shape and chart incorrectly imported
https://bugs.documentfoundation.org/show_bug.cgi?id=144798 Telesto changed: What|Removed |Added CC||tele...@surfxs.nl --- Comment #2 from Telesto --- Repro Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: b60b6bfaafa1315e07108dba50f016975b619c59 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: en-US (nl_NL); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144799] FILEOPEN DOCX Text of textbox inside chart grows
https://bugs.documentfoundation.org/show_bug.cgi?id=144799 Telesto changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #2 from Telesto --- Repro Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: b60b6bfaafa1315e07108dba50f016975b619c59 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: en-US (nl_NL); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144779] Crash when selecting a table
https://bugs.documentfoundation.org/show_bug.cgi?id=144779 --- Comment #3 from Telesto --- No crash (without extensions) on Windows Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: b60b6bfaafa1315e07108dba50f016975b619c59 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: en-US (nl_NL); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.