core.git: Branch 'distro/collabora/co-23.05' - sw/source
sw/source/core/access/AccessibilityCheck.cxx | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
New commits:
commit 117658b28d3c64cd94747547e118764ef495d959
Author: Caolán McNamara
AuthorDate: Thu Dec 21 16:47:18 2023 +
Commit: Tomaž Vajngerl
CommitDate: Wed Dec 27 08:03:47 2023 +0100
crashreporting: apparent null deref in a11y check
svl/source/items/itemset.cxx:801
svl/source/items/itemset.cxx:796
sw/source/core/access/AccessibilityCheck.cxx:1193
sw/source/core/access/AccessibilityCheck.cxx:1184
sw/source/core/access/AccessibilityCheck.cxx:1562
sw/source/core/access/AccessibilityCheck.cxx:1552
sw/source/core/txtnode/OnlineAccessibilityCheck.cxx:134
cppu/source/uno/copy.hxx:288
cppu/source/uno/any.cxx:72
cppu/source/typelib/typelib.cxx:1328
cppu/source/typelib/typelib.cxx:2169
Change-Id: I91a83ffb9f1912dd9736e3d6a194f63475f63b99
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/161151
Tested-by: Jenkins CollaboraOffice
Reviewed-by: Tomaž Vajngerl
diff --git a/sw/source/core/access/AccessibilityCheck.cxx
b/sw/source/core/access/AccessibilityCheck.cxx
index 2121ed10519b..c8577a4fc036 100644
--- a/sw/source/core/access/AccessibilityCheck.cxx
+++ b/sw/source/core/access/AccessibilityCheck.cxx
@@ -931,10 +931,12 @@ public:
return;
// Check if it's a real caption
-const SwNode* aStartFly = pCurrent->FindFlyStartNode();
-if (aStartFly
-&& aStartFly->GetFlyFormat()->GetAnchor().GetAnchorId() !=
RndStdIds::FLY_AS_CHAR)
-return;
+if (const SwNode* pStartFly = pCurrent->FindFlyStartNode())
+{
+const SwFrameFormat* pFormat = pStartFly->GetFlyFormat();
+if (!pFormat || pFormat->GetAnchor().GetAnchorId() !=
RndStdIds::FLY_AS_CHAR)
+return;
+}
auto aIter = SwIterator(*pTextNode);
auto nCount = 0;
[Bug 158862] LibreOffice crashes when attempting to inspect a UNO object in the Watch Window during debugging after successful initial inspection.
https://bugs.documentfoundation.org/show_bug.cgi?id=158862 Mike Kaganski changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |mikekagan...@hotmail.com |desktop.org | Status|NEW |ASSIGNED --- Comment #10 from Mike Kaganski --- https://gerrit.libreoffice.org/c/core/+/161366 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158866] Pasting 2 pictures into the same cell will cause the picture to display incorrectly in LibreOffice Clac
https://bugs.documentfoundation.org/show_bug.cgi?id=158866 --- Comment #3 from 745629...@qq.com --- Can I post a BILIBILI video link here? I found more details about this bug. It’s too cumbersome and abstract to write with just words. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 116143] [META] Text cursor (caret) bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=116143 Dieter changed: What|Removed |Added Depends on||158875 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158875 [Bug 158875] Text Cursor (Input Caret) too thin in Writer on macOS -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158875] Text Cursor (Input Caret) too thin in Writer on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=158875 Dieter changed: What|Removed |Added OS|All |macOS (All) Blocks||116143 Keywords||accessibility Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=116143 [Bug 116143] [META] Text cursor (caret) bugs -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158880] UX: Let users select multiple toolbars at once to view or hide
https://bugs.documentfoundation.org/show_bug.cgi?id=158880 j.a.sw...@gmail.com changed: What|Removed |Added Summary|Let users select multiple |UX: Let users select |toolbars at once to view or |multiple toolbars at once |hide|to view or hide -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158112] Sidebar pane shortcuts conflict with Alt+NumPad input (comment 5, comment 9)
https://bugs.documentfoundation.org/show_bug.cgi?id=158112 --- Comment #24 from libretist --- (In reply to V Stuart Foote from comment #14) > (In reply to xordevoreaux from comment #13) > > I'm not seeing deprecation for alt codes in Windows. > > […] > > The Wikipedia article gives the history [1]. > Deprecated […] > > [1] https://en.wikipedia.org/wiki/Alt_code I don't see anything about deprecation in this link. I agree with comment #20 > The amount of dupes will keep increasing with time, because the method is > very popular (and certainly not deprecated from the POV of users) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158873] Hyperlinks do not change colour when visited
https://bugs.documentfoundation.org/show_bug.cgi?id=158873 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 --- Comment #1 from m.a.riosv --- Seems a refresh issue. Reproducible: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 8148dd6ed3c61eaf5f9fe3a060ecda9d11611f39 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158879] direct-formatting of INDIVIDUAL list symbols
https://bugs.documentfoundation.org/show_bug.cgi?id=158879 --- Comment #1 from libretist --- related: bug#158835 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158880] New: Let users select multiple toolbars at once to view or hide
https://bugs.documentfoundation.org/show_bug.cgi?id=158880 Bug ID: 158880 Summary: Let users select multiple toolbars at once to view or hide Product: LibreOffice Version: 7.6.4.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: j.a.sw...@gmail.com Now, selecting multiple toolbars to view or hide is an iterative task, with these steps: 1. Select "View." 2. Choose "Toolbars." 3. Tick or untick a toolbar. 4. (Repeat) For multiple toolbars, this task is tedious. The task would become simple if users were shown one "static" menu box allowing them to make multiple choices at once. So: 1. Select "View" 2. Select "Toolbars. . ." 3. Tick or untick desired toolbars. 4. Select "Close" or "OK." 5. (Done) Helpful also to include would be the option "Untick all" (or "Hide all toolbars"). Though generally useful, this option has a particular use case: For Writer a much-requested feature is "split-screen" functionality -- that is, the ability to display and work with the content of one file in two windows, each showing a minimal interface. With Writer as it is now, the best way I know of to achieve this is: 1. Choose the "Sidebar" interface. 2. Hide all toolbars. 3. Choose "Window--> New Window." 4. Manually position the two windows as desired. For this use case, having steps 1, 2, and 3 (and perhaps 4) collapsed into one command would be ideal. But at least having step 2 be close to a one-shot task would help. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 47531] external references in charts
https://bugs.documentfoundation.org/show_bug.cgi?id=47531 m.a.riosv changed: What|Removed |Added CC||dbon...@gmail.com --- Comment #8 from m.a.riosv --- *** Bug 158870 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158870] Deleted/Left Out functionality
https://bugs.documentfoundation.org/show_bug.cgi?id=158870 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from m.a.riosv --- Seems to be an old issue. https://bugs.documentfoundation.org/show_bug.cgi?id=47531 (external references in charts) If you are not agreed, reopen it. *** This bug has been marked as a duplicate of bug 47531 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 61294] FORMATTING, Draw doesn't support different page sizes in the same document.
https://bugs.documentfoundation.org/show_bug.cgi?id=61294 --- Comment #3 from plonkar chivist --- Draw does not accommodate various page sizes within the same document, leading to complications when importing Visio diagrams. Libvisio addresses this by generating pages with the largest height and width, but this is not an ideal solution. https://vampire-survival.com -- You are receiving this mail because: You are the assignee for the bug.
[Bug 61290] EDITING: Text in a cell
https://bugs.documentfoundation.org/show_bug.cgi?id=61290 --- Comment #4 from plonkar chivist --- Your bug report is being marked as INVALID due to a lack of activity and insufficient information necessary for an accurate reproduction and confirmation of the problem. We encourage you to retest your bug using the latest release. https://doodle-baseball.com/ -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158866] Pasting 2 pictures into the same cell will cause the picture to display incorrectly in LibreOffice Clac
https://bugs.documentfoundation.org/show_bug.cgi?id=158866 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #2 from m.a.riosv --- If you select go to another cell, and return to the cell, the it works. In any case, seems a bug. Reproducible with: Version: 7.5.9.2 (X86_64) / LibreOffice Community Build ID: cdeefe45c17511d326101eed8008ac4092f278a9 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: CL threaded and Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 8148dd6ed3c61eaf5f9fe3a060ecda9d11611f39 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158663] LibreOffice 7.6.4.1 hangs on startup after opening initial window and showing splash screen on Arch Linux
https://bugs.documentfoundation.org/show_bug.cgi?id=158663 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158658] FILEOPEN DOCX/DOC/RTF Tabs closing header paragraph are wrapped and not flowing outside the page area
https://bugs.documentfoundation.org/show_bug.cgi?id=158658 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158634] Something is wrong with dates: they are not visible in filter by formatted columns and are almost impossible to edit.
https://bugs.documentfoundation.org/show_bug.cgi?id=158634 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158610] FILEOPEN DOCX Changing font color in numbered list changes font color of numbering
https://bugs.documentfoundation.org/show_bug.cgi?id=158610 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158672] FILEOPEN RTF Drawing canvas imported as a placeholder image
https://bugs.documentfoundation.org/show_bug.cgi?id=158672 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158616] Verankerung von Bildern im Writer funktioniert nicht mehr
https://bugs.documentfoundation.org/show_bug.cgi?id=158616 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158456] FILEOPEN, FILESAVE. Corrupted ODS file opens slowly and increases in size after saving
https://bugs.documentfoundation.org/show_bug.cgi?id=158456 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158841] Numbering of the chapters is wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=158841 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158582] FILEOPEN DOCX Dropdown Content Controls are opened as legacy fields
https://bugs.documentfoundation.org/show_bug.cgi?id=158582 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155539] V7.4 does not read older versions of documents
https://bugs.documentfoundation.org/show_bug.cgi?id=155539 --- Comment #5 from QA Administrators --- Dear Nick, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155538] Bad listing - not dot but something like "q" is listing when I open a pdf file in Libre Office Draw.
https://bugs.documentfoundation.org/show_bug.cgi?id=155538 --- Comment #3 from QA Administrators --- Dear Chris, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 149137] Crash on launching Libreoffice on MacOS 12.3.1 and displaying crash report.
https://bugs.documentfoundation.org/show_bug.cgi?id=149137 --- Comment #10 from QA Administrators --- Dear paulflaherty5, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 93139] The orca Screen Reader is silent when placing focus over a bullet in a bulleted list.
https://bugs.documentfoundation.org/show_bug.cgi?id=93139 --- Comment #14 from QA Administrators --- Dear am_dxer, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107423] Contextual groups variant of the Notebookbar is supposed to work with main menu and sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=107423 --- Comment #9 from QA Administrators --- Dear Heiko Tietze, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Bug 139625] List bullet or number duplicates when list wraps around image
https://bugs.documentfoundation.org/show_bug.cgi?id=139625 --- Comment #9 from QA Administrators --- Dear thatho, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 92592] Save as to OpenDataSpace via CMIS is buggy
https://bugs.documentfoundation.org/show_bug.cgi?id=92592 --- Comment #4 from QA Administrators --- Dear Andras Timar, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 92593] Check out file from OpenDataSpace via CMIS does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=92593 --- Comment #4 from QA Administrators --- Dear Andras Timar, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 92591] Save to OpenDataSpace via CMIS fails
https://bugs.documentfoundation.org/show_bug.cgi?id=92591 --- Comment #4 from QA Administrators --- Dear Andras Timar, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 136718] Highlighting of the heading with numbering changes after deleting bulleted list
https://bugs.documentfoundation.org/show_bug.cgi?id=136718 --- Comment #8 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 133228] Moving a cell with mouse shows only black dot instead of helpful cell highlightning
https://bugs.documentfoundation.org/show_bug.cgi?id=133228 --- Comment #3 from QA Administrators --- Dear eisa01, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 129530] vertical flip, which is contained in draw:transform, does not flip a legacy arc
https://bugs.documentfoundation.org/show_bug.cgi?id=129530 --- Comment #4 from QA Administrators --- Dear Regina Henschel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 106187] Document colors not working with text highlight and shape colors
https://bugs.documentfoundation.org/show_bug.cgi?id=106187 --- Comment #7 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 125750] PIVOTTABLE scatter chart
https://bugs.documentfoundation.org/show_bug.cgi?id=125750 --- Comment #5 from QA Administrators --- Dear David, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 100871] Bullets and numberings not expose to Assistives Technologies
https://bugs.documentfoundation.org/show_bug.cgi?id=100871 --- Comment #9 from QA Administrators --- Dear Alex ARNAUD, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158878] Editable PDF Exported from LibreOffice Writer Unstable and crashes when clicked on
https://bugs.documentfoundation.org/show_bug.cgi?id=158878 --- Comment #2 from Popz --- Created attachment 191602 --> https://bugs.documentfoundation.org/attachment.cgi?id=191602=edit The faulty exported PDF -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158878] Editable PDF Exported from LibreOffice Writer Unstable and crashes when clicked on
https://bugs.documentfoundation.org/show_bug.cgi?id=158878 --- Comment #1 from Popz --- Created attachment 191601 --> https://bugs.documentfoundation.org/attachment.cgi?id=191601=edit The .odt file that exports faulty PDFs -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158878] New: Editable PDF Exported from LibreOffice Writer Unstable and crashes when clicked on
https://bugs.documentfoundation.org/show_bug.cgi?id=158878 Bug ID: 158878 Summary: Editable PDF Exported from LibreOffice Writer Unstable and crashes when clicked on Product: LibreOffice Version: 7.6.4.1 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: nicholaus.popad...@gmail.com Description: I put together a fillable PDF on LibreOffice Writer and exported it to PDF. After exporting it, it briefly opens on my Adobe PDF application before crashing as soon as it is clicked on. My original export was stable but I realized that I had not set the “Tab Order” of the fillable fields correctly, so I went back to reorder them. After reordering them, this issue appeared. I posted my issue to the Libre Office blog and was directed to report the Bug to Bugzilla. Link to original post below... https://ask.libreoffice.org/t/exported-pdf-from-libreoffice-crashes-right-after-opening-file-not-stable/99895 Steps to Reproduce: 1.Create editable PDF 2.Re-order "Tab Order" of fields 3.Export as PDF and click to begin filling. Actual Results: I opened the exported PDF file and clicked on it to begin filling, but as soon as I clicked on it my Adobe PDF application crashed and produced an error report. I re-exported the file multiple times, changing the export settings each time and the error seams to occur anytime I select any boxes under "File > Export As > Export as PDF... > Structure" Expected Results: The PDF should be a stable, editable PDF and not crash when clicked on. Reproducible: Always User Profile Reset: Yes Additional Info: I can provide the .odt file - it is not a private document and does not contain anything I do not mind sharing. I can send it via email or upload it if you provide instructions on how to go about doing so. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 113050] FILEOPEN: PDF freezes Draw, one page, 19 KB file
https://bugs.documentfoundation.org/show_bug.cgi?id=113050 --- Comment #21 from Dave Gilbert --- Great. So as mentioned on irc, it looks like we have to support poppler >=0.14 0.14 does indeed have the same tilingPatternFill and useTilingPatternFill hooks in the outputDev - great.oh, the interface has changed somewhere along the line, so have to deal with that change; sigh OK, got to try a few versions then. (Falling back would be easy, poppler behaviour on this hook is already see if it's supported, try the hook and if the hook doesn't exist refuse). I'll look at implementing it. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 57187] EDITING: Justified text looks wrong as right aligned when breaking line with shift+enter
https://bugs.documentfoundation.org/show_bug.cgi?id=57187 --- Comment #23 from Mike Kaganski --- Note also, that our algorithm violates also the non-tailorable LB6 "Do not break before hard line breaks" rule of UAX #14 [1]: if you have a problematic line with a space followed by a manual line break, and you start adding spaces before the break, at some point the line becomes properly justified, but the break moves to the next line, where it sits alone (so the line gets broken after the last space, *immediately before hard break*). [1] https://www.unicode.org/reports/tr14/#LB6 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 90520] Base crashes with Oracle ODBC driver when sorting/filtering
https://bugs.documentfoundation.org/show_bug.cgi?id=90520 --- Comment #24 from Lionel Elie Mamane --- I'd be happy to review/approve a well-tested patch along the lines of the discussion below. Put me as reviewer on gerrit, and feel free to ping me every week by email if I don't respond. (In reply to grongo2 from comment #3) > OTools::getStringValue tries to read a column with more than 2048 bytes by > iterating over SQLGetData, but uses only pcbValue to detect when stopping, > instead of looking also at the function return value. Good point. Looking also at the function return value would make the code more robust and would be a welcome improvement. > Further, it iterates even with fixed-length column, while ODBC allows > iterating only over variable lenght columns (eg VARCHAR). Not 100% sure what you mean by "fixed-length column", but I note that https://learn.microsoft.com/en-us/sql/odbc/reference/syntax/sqlgetdata-function#retrieving-variable-length-data-in-parts explicitly allows it for SQL_CHAR, SQL_WCHAR and SQL_BINARY. In the context of this bug, you say the data being read is SQL_CHAR so the iteration seems legit. However, there does seem to be a codepath where indeed LibreOffice will try to do that iteration on SQL_DECIMAL and SQL_NUMERIC: in OResultSet.cxx, method OResultSet::fillColumn Plus anytime any code (even user-written LibreOffice Basic, Python or other API binding) calls getString on a non-string column but only on a DatabaseMetadataResultSet, not on a regular ResultSet. > So a workaround would be resetting pcbValue to zero just before calling > SQLGetData. While I'm generally wary of driver-specific work-arounds, something like that could indeed be seen as a general robustification of the code, so I could be tempted to approve it. One could discuss whether one should set it to some other value than zero, such as e.g. a constant not allowed to be written there by the driver (such as a constant chosen to be different than all valid "Length and Indicator Values", or one valid only for SQLPutData and not SQLGetData). > A better fix should be check SQLGetData return value and act accordingly, > but perhaps LO does things this way as a workaround to other driver bugs ? In the absence of a comment in the code that specifically says so, any such putative driver bug is lost to time immemorial, and could have been fixed since then. I wouldn't let that keep us from moving forward with that better fix. (In reply to grongo2 from comment #22) > To tell the truth, the handling of this bug is disheartening: eight year ago > I reported it, carrying out a detailed analysis and suggesting a fix. > After that, no action, only a "please try with the latest release", even if > the source code remains unchanged. > Anyway, the bug is still present. You mean in the same eight years, Oracle has (also) not fixed their bug? > Reproducing is simple: Well, no. It requires an Oracle database, which is not quite an "apt-get install" away, and I expect requires agreeing to a bizarre funky anti-social agreement forbidding use for any purpose on any machine one wants and/or sharing it with one's neighbour and/or improving it and/or sharing one's improvements? The first download page I could find https://www.oracle.com/database/technologies/xe-downloads.html also doesn't have any download for any source code (so I cannot compile/install it), nor for binaries for my main work machine (GNU/Linux on ppc64le). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158776] DOCX import: unnecessary shrinking of spaces
https://bugs.documentfoundation.org/show_bug.cgi?id=158776
--- Comment #5 from Mike Kaganski ---
FTR: https://www.unicode.org/reports/tr14/ is a Unicode Standard Annex that
describes line breaking algorithm; in particular, it discusses differences of
space (SP) and other whitespace characters ("Breaking Spaces" and "Tabs" under
BA) wrt shrinking.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 158877] Non-corrective Autoformat settings can't just be placed under AutoCorrect
https://bugs.documentfoundation.org/show_bug.cgi?id=158877 Eyal Rozenberg changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval Blocks||103341 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103341 [Bug 103341] [META] AutoCorrect and Word Completion bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158877] Non-corrective Autoformat settings can't just be placed under AutoCorrect
https://bugs.documentfoundation.org/show_bug.cgi?id=158877 Eyal Rozenberg changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval Blocks||103341 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103341 [Bug 103341] [META] AutoCorrect and Word Completion bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103341] [META] AutoCorrect and Word Completion bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103341 Eyal Rozenberg changed: What|Removed |Added Depends on||158877 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158877 [Bug 158877] Non-corrective Autoformat settings can't just be placed under AutoCorrect -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158877] New: Non-corrective Autoformat settings can't just be placed under AutoCorrect
https://bugs.documentfoundation.org/show_bug.cgi?id=158877 Bug ID: 158877 Summary: Non-corrective Autoformat settings can't just be placed under AutoCorrect Product: LibreOffice Version: 7.6.4.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: minor Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com Auto-formatting is not a kind of correction. Yet, if I want to change auto-formatting settings, I have to look for them under Tools | AutoCorrect | AutoCorrect options... This is counter-intuitive and should change. Either the naming should change; or there should be some kind of duplicate way to get to the same settings, named differently; or the settings should be separated. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158876] Autocorrect options are very confusing and difficult to use
https://bugs.documentfoundation.org/show_bug.cgi?id=158876 Eyal Rozenberg changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org Blocks||103341 Keywords||needsUXEval Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103341 [Bug 103341] [META] AutoCorrect and Word Completion bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103341] [META] AutoCorrect and Word Completion bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103341 Eyal Rozenberg changed: What|Removed |Added Depends on||158876 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158876 [Bug 158876] Autocorrect options are very confusing and difficult to use -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158876] Autocorrect options are very confusing and difficult to use
https://bugs.documentfoundation.org/show_bug.cgi?id=158876 Eyal Rozenberg changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org Blocks||103341 Keywords||needsUXEval Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103341 [Bug 103341] [META] AutoCorrect and Word Completion bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158876] New: Autocorrect options are very confusing and difficult to use
https://bugs.documentfoundation.org/show_bug.cgi?id=158876 Bug ID: 158876 Summary: Autocorrect options are very confusing and difficult to use Product: LibreOffice Version: 7.6.4.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: minor Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com The AutoCorrect options, accessible on the menus through Tools > AutoCorrect > AutoCorrect Options... , and then choosing the Options tab - are IMHO a jumbled mess that is very difficult to understand: * There is no sub-categorization of the ~20 items, while * Some are corrections, some change content between two valid choices, some don't change content at all * Some apply new formatting, some alter formatting, some don't format at all. * Some changes are paragraph-level, some are character-level, some are multi-paragraph * For most items, it is not indicated what replaces what. Examples: * "Create Table" - when? Out of what? ; * "Replace dashes" - which dashes get replaced? What are they replaced with? * "Use replacement table" - to replace what? And what's in the table? * Many items are just generally confusing * "Ignore double spaces" - how is that different from not ignoring them? * "Apply border" - Border of what? Apply it to what? When? * "DOI citation recognition" - Writer doesn't even have citation management; what's this even supposed to do? (Hint: it doesn't actually recognize DOI numbers...) I believe we should both reorgnize this pane somewhat, and do some careful renaming. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 140353] UI: Caret merely visible in Writer, LibreOffice (Ubuntu Snap) does not use system settings
https://bugs.documentfoundation.org/show_bug.cgi?id=140353 --- Comment #6 from Detlef Girke --- Hi Dieter, ok thanks. I understand. I filed a new bug with the number 158875 on https://bugs.documentfoundation.org/show_bug.cgi?id=158875. Best Regards Detlef -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158875] New: Text Cursor (Input Caret) too thin in Writer on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=158875
Bug ID: 158875
Summary: Text Cursor (Input Caret) too thin in Writer on macOS
Product: LibreOffice
Version: 7.0.0.3 release
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Writer
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: m...@dgirke.de
Description:
Linux and Windows provide solutions to make the text cursor in writer thicker.
This feature is essential for people with vision impairment.
In Linux, you can edit the file ~/.config/gtk-3.0/gtk.css and insert the
following line:
* { -GtkWidget-cursor-aspect-ratio: 0.2; }
For me, a value like 0.2 works fine. You can play around with it until it fits
your needs.
In Windows, you can go to
Start > Settings > Ease of Access > Text cursor > Change text cursor thickness
This setting works system wide.
In macOS, there is absolutely no way to change the text cursor thickness system
wide unless it is provided by the app itself. Some apps do, some don´t.
LibreOffice unfortunately doesn´t and never did.
For me, as a parially sighted person and most of the time working with macOS,
every version of LO starting with 7.x isn´t accessible at all just because of
the much too thin input caret in writer. I just had a look at the first beta of
LO 24.2. The text cursor even went thinner! So disappointing that people with
low vision seem to be more ignored with everey new version of LO. Accessibility
isn´t just something for people using screenreaders, folks ;-)
This task could be seen as a feature request either. But in my opinion, as the
input caret sometimes was thicker, sometimes narrower, it is a bug.
A feature I really would appreciate would be a way to individually adjust the
input caret thickness in the accessibility settings of LO.
Steps to Reproduce:
1. Open Writer in LO 7.x or (much thinner) in 24.x and open it in LO 6.x.
2. Compare the thickness in 6.x to 24.x
3. 6.x has a much thicker input caret which can still be seen by people with
visual impairment or elderly people. In 7.0 or higher it´s getting thinner and
thinner
Actual Results:
Text cursor too thin
Expected Results:
Text cursor always sufficiently thick even for people with vision impairment. A
thickness like in 6.x would be ok. A way to adjust it individually would be
much better.
Reproducible: Always
User Profile Reset: Yes
Additional Info:
I am using Version 6.4.7.2 (intel x64 version on M1 Macbook Pro, much more
stable than recent versions for Apple Silicon btw) although it is missing some
great features from the recent versions.
Version: 6.4.7.2
Build-ID: 639b8ac485750d5696d7590a72ef1b496725cfb5
CPU-Threads: 10; BS: Mac OS X 10.16; UI-Render: Standard; VCL: osx;
Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE
Calc: threaded
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 144124] trying to paste older entries from clipboard manager (e.g. LaunchBar, Alfred, Raycast, iClip) pastes latest clipboard content on macOS (repro: comment 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=144124
--- Comment #9 from Patrick Luby ---
I can reproduce this with LaunchBar. What is interesting is that LibreOffice
never receives a "lost ownership" notification when I select an older entry in
LaunchBar's history list. But if I quit LaunchBar, then LibreOffice properly
receives a "lost ownership" notification.
Note: the following debug patch that I used in my local LibreOffice build:
diff --git a/vcl/osx/clipboard.cxx b/vcl/osx/clipboard.cxx
index 5d925b3b1954..c37453d0d073 100644
--- a/vcl/osx/clipboard.cxx
+++ b/vcl/osx/clipboard.cxx
@@ -46,6 +46,11 @@ using namespace css;
pAquaClipboard->provideDataForType(sender, type);
}
+-(void)pasteboardChangedOwner:(NSPasteboard *)sender
+{
+fprintf(stderr, "Lost ownership!\n");
+}
+
-(void)applicationDidBecomeActive:(NSNotification*)aNotification
{
if( pAquaClipboard )
diff --git a/vcl/osx/clipboard.hxx b/vcl/osx/clipboard.hxx
index 6213ce692106..360a83cd81d0 100644
--- a/vcl/osx/clipboard.hxx
+++ b/vcl/osx/clipboard.hxx
@@ -55,6 +55,8 @@ class AquaClipboard;
// Promise resolver function
- (void)pasteboard:(NSPasteboard*)sender provideDataForType:(const NSString
*)type;
+-(void)pasteboardChangedOwner:(NSPasteboard *)sender;
+
-(void)applicationDidBecomeActive:(NSNotification*)aNotification;
-(void)disposing;
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 158874] Want MS-Word like auto-formatting of beginning of list item
https://bugs.documentfoundation.org/show_bug.cgi?id=158874 Eyal Rozenberg changed: What|Removed |Added Blocks||103341 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103341 [Bug 103341] [META] AutoCorrect and Word Completion bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103341] [META] AutoCorrect and Word Completion bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103341 Eyal Rozenberg changed: What|Removed |Added Depends on||158874 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158874 [Bug 158874] Want MS-Word like auto-formatting of beginning of list item -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158874] Want MS-Word like auto-formatting of beginning of list item
https://bugs.documentfoundation.org/show_bug.cgi?id=158874 --- Comment #1 from Eyal Rozenberg --- Note that the MS Word feature works both for DF and for character styles. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158874] New: Want MS-Word like auto-formatting of beginning of list item
https://bugs.documentfoundation.org/show_bug.cgi?id=158874 Bug ID: 158874 Summary: Want MS-Word like auto-formatting of beginning of list item Product: LibreOffice Version: 7.6.4.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com Created attachment 191600 --> https://bugs.documentfoundation.org/attachment.cgi?id=191600=edit MS Word AutoCorrect options, Autoformat As You Type pane; see third-from-last checkbox In MS Word, one of the Auto-format "as-you-type" capabilities is: "Format beginning of list item like the one before it". To be honest, I'm not too thrilled about this feature - since one has to change format after the beginning-part to the non-beginning-part format - but apparently some users like it. Perhaps we should also offer it, for feature parity? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158864] Many/most dark mode UI elements have too strong a contrast
https://bugs.documentfoundation.org/show_bug.cgi?id=158864 --- Comment #7 from V Stuart Foote --- (In reply to John Mills from comment #6) > Created attachment 191599 [details] > Windows 11 dark mode LibreOffice > > LibreOffice under Windows 11, note the panel colour compared to Linux GTK. Sorry John, not seeing an issue with panels in the LibreOffice UI. Could you do a side-by-side with comments. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158864] Many/most dark mode UI elements have too strong a contrast
https://bugs.documentfoundation.org/show_bug.cgi?id=158864 --- Comment #7 from V Stuart Foote --- (In reply to John Mills from comment #6) > Created attachment 191599 [details] > Windows 11 dark mode LibreOffice > > LibreOffice under Windows 11, note the panel colour compared to Linux GTK. Sorry John, not seeing an issue with panels in the LibreOffice UI. Could you do a side-by-side with comments. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158871] Stepped chart type can't change its properties
https://bugs.documentfoundation.org/show_bug.cgi?id=158871 Julien Nabet changed: What|Removed |Added Resolution|--- |DUPLICATE CC||serval2...@yahoo.fr Status|UNCONFIRMED |RESOLVED --- Comment #1 from Julien Nabet --- Fix from next release 24.2. For 7.6, review is here: https://gerrit.libreoffice.org/c/core/+/160700 *** This bug has been marked as a duplicate of bug 158684 *** -- You are receiving this mail because: You are the assignee for the bug.
core.git: 2 commits - sw/qa vcl/osx
vcl/osx/DataFlavorMapping.cxx |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 40617d867346956588ac023511f31210107217f4 Author: Andrea Gelmini AuthorDate: Thu Dec 21 00:56:02 2023 +0100 Commit: Julien Nabet CommitDate: Tue Dec 26 21:34:54 2023 +0100 Remove executable bits on data file Change-Id: Id6d8ccc82f892b098d96e28a7222c58e08e22b09 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/161086 Tested-by: Jenkins Reviewed-by: Julien Nabet diff --git a/sw/qa/extras/rtfexport/data/tdf158762.rtf b/sw/qa/extras/rtfexport/data/tdf158762.rtf old mode 100755 new mode 100644 commit 66805f57f2770ea0e73eef4781ca218dbf60b1a9 Author: Andrea Gelmini AuthorDate: Tue Dec 26 19:22:54 2023 +0100 Commit: Julien Nabet CommitDate: Tue Dec 26 21:34:40 2023 +0100 Fix typo Change-Id: I325079efc51bbefb7612403e4800ca5320b49cec Reviewed-on: https://gerrit.libreoffice.org/c/core/+/161334 Tested-by: Jenkins Reviewed-by: Julien Nabet diff --git a/vcl/osx/DataFlavorMapping.cxx b/vcl/osx/DataFlavorMapping.cxx index 361e268bcd6d..96dd5501e355 100644 --- a/vcl/osx/DataFlavorMapping.cxx +++ b/vcl/osx/DataFlavorMapping.cxx @@ -561,7 +561,7 @@ const NSString* DataFlavorMapper::openOfficeToSystemFlavor( const DataFlavor& oO // The problem is that many macOS clipboard managers fetch *all* // available flavors that are available in the macOS general // pasteboard instead of just one flavor and this triggers the -// FLAVOR_LINK flavor's unusual editing behavor in Writer every +// FLAVOR_LINK flavor's unusual editing behavior in Writer every // time the user copies Writer text. // Users have reported in tdf#1515679 that on macOS, Microsoft // Writer, Excel, and PowerPoint do not recognize this flavor
core.git: extensions/source
extensions/source/propctrlr/formgeometryhandler.cxx | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
New commits:
commit a5fd75485f9ab6bc22f12d4a6ca907dd6a33c278
Author: Julien Nabet
AuthorDate: Tue Dec 26 17:38:43 2023 +0100
Commit: Julien Nabet
CommitDate: Tue Dec 26 21:31:20 2023 +0100
Use emplace_back instead of push_back (extensions part2)
Change-Id: Ib86f85e6162639d229443cb3026c355c6a659932
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/161306
Tested-by: Jenkins
Reviewed-by: Julien Nabet
diff --git a/extensions/source/propctrlr/formgeometryhandler.cxx
b/extensions/source/propctrlr/formgeometryhandler.cxx
index da31294d1b5c..b07cd7eb145e 100644
--- a/extensions/source/propctrlr/formgeometryhandler.cxx
+++ b/extensions/source/propctrlr/formgeometryhandler.cxx
@@ -739,22 +739,22 @@ namespace pcr
if ( _event.PropertyName == "Position" )
{
css::awt::Point aPos = m_xShape->getPosition();
-aEventTranslations.push_back( EventTranslation(
PROPERTY_POSITIONX, Any( aPos.X ) ) );
-aEventTranslations.push_back( EventTranslation(
PROPERTY_POSITIONY, Any( aPos.Y ) ) );
+aEventTranslations.emplace_back(PROPERTY_POSITIONX, Any( aPos.X ));
+aEventTranslations.emplace_back(PROPERTY_POSITIONY, Any( aPos.Y ));
}
else if ( _event.PropertyName == "Size" )
{
css::awt::Size aSize = m_xShape->getSize();
-aEventTranslations.push_back( EventTranslation( PROPERTY_WIDTH,
Any( aSize.Width ) ) );
-aEventTranslations.push_back( EventTranslation( PROPERTY_HEIGHT,
Any( aSize.Height ) ) );
+aEventTranslations.emplace_back(PROPERTY_WIDTH, Any( aSize.Width
));
+aEventTranslations.emplace_back(PROPERTY_HEIGHT, Any( aSize.Height
));
}
else if ( _event.PropertyName == PROPERTY_ANCHOR_TYPE )
{
-aEventTranslations.push_back( EventTranslation(
PROPERTY_TEXT_ANCHOR_TYPE, _event.NewValue ) );
+aEventTranslations.emplace_back(PROPERTY_TEXT_ANCHOR_TYPE,
_event.NewValue);
}
else if ( _event.PropertyName == PROPERTY_ANCHOR )
{
-aEventTranslations.push_back( EventTranslation(
PROPERTY_SHEET_ANCHOR_TYPE, _event.NewValue ) );
+aEventTranslations.emplace_back(PROPERTY_SHEET_ANCHOR_TYPE,
_event.NewValue);
}
PropertyChangeEvent aTranslatedEvent( _event );
core.git: 2 commits - scaddins/source sd/source
scaddins/source/analysis/analysishelper.cxx |2 +-
scaddins/source/datefunc/datefunc.cxx |2 +-
scaddins/source/pricing/pricing.cxx |2 +-
sd/source/ui/view/drviews2.cxx | 18 +-
4 files changed, 12 insertions(+), 12 deletions(-)
New commits:
commit a1b7ae437c9e37cb1fe3063906609b60dc7e7f13
Author: Julien Nabet
AuthorDate: Tue Dec 26 18:42:03 2023 +0100
Commit: Julien Nabet
CommitDate: Tue Dec 26 21:31:11 2023 +0100
Use emplace_back instead of push_back (sd)
Change-Id: I5641a98f26a19efabb3a5eee25e48282d44faca4
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/161332
Tested-by: Jenkins
Reviewed-by: Julien Nabet
diff --git a/sd/source/ui/view/drviews2.cxx b/sd/source/ui/view/drviews2.cxx
index 54b16db4b1e7..8358e95cf8a9 100644
--- a/sd/source/ui/view/drviews2.cxx
+++ b/sd/source/ui/view/drviews2.cxx
@@ -277,7 +277,7 @@ private:
// Get Weight of current paragraph
OUString sWeightProperty =
getWeightString(rEditText.GetParaAttribs(nCurrentParagraph));
// Insert new paragraph into collection
-m_aResults.push_back({ svx::ClassificationType::PARAGRAPH,
sWeightProperty, sBlank, sBlank });
+m_aResults.emplace_back(svx::ClassificationType::PARAGRAPH,
sWeightProperty, sBlank, sBlank);
}
const SvxFieldItem* pFieldItem = findField(rSection);
@@ -289,27 +289,27 @@ private:
const OUString& aKey = pCustomPropertyField->GetName();
if (m_aKeyCreator.isMarkingTextKey(aKey))
{
-m_aResults.push_back({ svx::ClassificationType::TEXT,
+m_aResults.emplace_back(svx::ClassificationType::TEXT,
svx::classification::getProperty(m_xPropertyContainer, aKey),
- sBlank, sBlank });
+ sBlank, sBlank);
}
else if (m_aKeyCreator.isCategoryNameKey(aKey) ||
m_aKeyCreator.isCategoryIdentifierKey(aKey))
{
-m_aResults.push_back({ svx::ClassificationType::CATEGORY,
+m_aResults.emplace_back(svx::ClassificationType::CATEGORY,
svx::classification::getProperty(m_xPropertyContainer, aKey),
- sBlank, sBlank });
+ sBlank, sBlank);
}
else if (m_aKeyCreator.isMarkingKey(aKey))
{
-m_aResults.push_back({ svx::ClassificationType::MARKING,
+m_aResults.emplace_back(svx::ClassificationType::MARKING,
svx::classification::getProperty(m_xPropertyContainer, aKey),
- sBlank, sBlank });
+ sBlank, sBlank);
}
else if (m_aKeyCreator.isIntellectualPropertyPartKey(aKey))
{
-m_aResults.push_back({
svx::ClassificationType::INTELLECTUAL_PROPERTY_PART,
+
m_aResults.emplace_back(svx::ClassificationType::INTELLECTUAL_PROPERTY_PART,
svx::classification::getProperty(m_xPropertyContainer, aKey),
- sBlank, sBlank });
+ sBlank, sBlank);
}
}
}
commit 79a26ca7e5cb8ae3b78915b1389f03293b71
Author: Julien Nabet
AuthorDate: Tue Dec 26 18:46:44 2023 +0100
Commit: Julien Nabet
CommitDate: Tue Dec 26 21:31:01 2023 +0100
Use emplace_back instead of push_back (scaddins)
Change-Id: I08b22351a3e75d5accbb3e59890f5e04b8fbb6d7
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/161333
Tested-by: Jenkins
Reviewed-by: Julien Nabet
diff --git a/scaddins/source/analysis/analysishelper.cxx
b/scaddins/source/analysis/analysishelper.cxx
index dfd41f953d29..974dcadc7c98 100644
--- a/scaddins/source/analysis/analysishelper.cxx
+++ b/scaddins/source/analysis/analysishelper.cxx
@@ -1368,7 +1368,7 @@ sal_uInt16 FuncData::GetStrIndex( sal_uInt16 nParamNum )
const
void InitFuncDataList(FuncDataList& rList)
{
for(const auto & rFuncData : pFuncDatas)
-rList.push_back(FuncData(rFuncData));
+rList.emplace_back(rFuncData);
}
SortedIndividualInt32List::SortedIndividualInt32List()
diff --git a/scaddins/source/datefunc/datefunc.cxx
b/scaddins/source/datefunc/datefunc.cxx
index 9b59adcb5dde..c8839662d04e 100644
--- a/scaddins/source/datefunc/datefunc.cxx
+++ b/scaddins/source/datefunc/datefunc.cxx
@@ -82,7 +82,7 @@ sal_uInt16 ScaFuncData::GetStrIndex( sal_uInt16 nParam ) const
static void InitScaFuncDataList(ScaFuncDataList& rList)
{
[Bug 113960] [Tables] Adapting table width by default
https://bugs.documentfoundation.org/show_bug.cgi?id=113960 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org --- Comment #14 from Buovjaga --- (In reply to Frank Brütting from comment #13) > I started this issue more than 6 years ago. And I am certainly tired of this > stupid bot closing all issues after a while. I try things, report them, > answer months and years later with everytime getting into an issue again and > spending a lot of time (mostly superfluous because not seeing any results in > most cases). I’m tired of this, please test for yourself. I wanted to help, > but not this way. The stupid bot will not close any issue that is in NEW status. However, with methodical testing we have found that 25% of pinged NEW reports could be closed as the bug was gone. Surely you admit such a nice result is worth the effort and annoyance. A clean bug tracker helps developers work more efficiently. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 64011] RTL sheets: you can't draw shapes from left to right, also the start position are wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=64011 Buovjaga changed: What|Removed |Added Status|VERIFIED|CLOSED URL|https://bestessaywriter.co. | |uk/universities/university- | |of-birmingham | -- You are receiving this mail because: You are the assignee for the bug.
[Bug 113960] [Tables] Adapting table width by default
https://bugs.documentfoundation.org/show_bug.cgi?id=113960 --- Comment #13 from Frank Brütting --- I started this issue more than 6 years ago. And I am certainly tired of this stupid bot closing all issues after a while. I try things, report them, answer months and years later with everytime getting into an issue again and spending a lot of time (mostly superfluous because not seeing any results in most cases). I’m tired of this, please test for yourself. I wanted to help, but not this way. -- You are receiving this mail because: You are the assignee for the bug.
Request for testing: trackpad changes in Calc
Hi everyone, For a few years now, a recurring complaint for macOS users has been swiping vertically on the trackpad on a macOS laptop is overly sensitive in Calc. Unless you are really careful to swipe precisely vertical, the slight horizontal movements in the macOS swipe events would cause Calc to veer left or right by many columns with a big swipe. So, I have made some changes to Calc to make horizontal swipes less sensitive to horizontal swipe and mouse wheel movements. With the following change, a native swipe events move roughly the same amount of "visual distance": https://gerrit.libreoffice.org/c/core/+/161278 What worries me is if this change will negatively affect swiping in Calc on Windows and Linux. My fix will be in tomorrow's (27 December 2023) nightly master build at the following webpage: https://dev-builds.libreoffice.org/daily/master/current.html Can anyone using Windows and/or Linux with trackpad test this fix out? If it causes any unexpected behavior on those platforms, please let me know and I can restrict my fix to only macOS. Regards, Patrick
[Bug 135478] Calc changes columns when scrolling down macOS or touchpad related
https://bugs.documentfoundation.org/show_bug.cgi?id=135478 Patrick Luby changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |plub...@libreoffice.org |desktop.org | Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #9 from Patrick Luby --- I have committed my fix for this bug and it will be included in tomorrow's (27 December 2023) nightly master build: https://dev-builds.libreoffice.org/daily/master/current.html Note: my fix still allows a little horizontal movement through when you are swiping at a slight angle from vertical, but with the fix what should happen is that each unit of horizontal movement in a native swipe event now only moves 1/8 of the default cell width instead of a full default cell width. For me this reduces the horizontal movement to only a single column left or right and that doesn't occur until I start swiping at more than a 10 degree or so angle left or right from vertical. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108075] [META] Scrolling and Page up/down issues
https://bugs.documentfoundation.org/show_bug.cgi?id=108075 Bug 108075 depends on bug 135478, which changed state. Bug 135478 Summary: Calc changes columns when scrolling down macOS or touchpad related https://bugs.documentfoundation.org/show_bug.cgi?id=135478 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158873] New: Hyperlinks do not change colour when visited
https://bugs.documentfoundation.org/show_bug.cgi?id=158873 Bug ID: 158873 Summary: Hyperlinks do not change colour when visited Product: LibreOffice Version: 7.5.9.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: babelfish0...@hotmail.com Description: If I have a hyperlink in a Writer document and click Ctrl+Click on it the page opens in my web-browser. However, the hyperlink in the document does not change colour (as it should). I have found that after 'visiting' a link to get the hyperlink to change colour one of the following actions need to be performed: (1) Type a character in the same paragraph as the hyperlink. (2) Scroll the document window. (3) If the Styles Deck is open, close the Deck. (4) If the Styles Deck is closed, open the Deck. There may be other actions that might cause the hyperlink to change colour to the 'visited colour'. In any case, it seems to me that when a hyperlink is Ctrl+Clicked on that Writer isn't scanning/parsing the paragraph and noting the change until the user takes some other action (as indicated above). Steps to Reproduce: See above. Actual Results: See above. Expected Results: The hyperlink should change colour immediately upon Ctrl+Click. Reproducible: Always User Profile Reset: No Additional Info: I do not know what version of LibreOffice was the earliest in which this bug arose. My current version of LibreOffice is: Version: 7.5.9.2 (X86_64) / LibreOffice Community Build ID: cdeefe45c17511d326101eed8008ac4092f278a9 CPU threads: 2; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 135478] Calc changes columns when scrolling down macOS or touchpad related
https://bugs.documentfoundation.org/show_bug.cgi?id=135478 --- Comment #8 from Commit Notification --- Patrick Luby committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/7af5df1d9fc472dc3a770fbff736eafa99d46bde tdf#135478 Reduce sensitivity of horizontal scrollwheel It will be available in 24.8.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 135478] Calc changes columns when scrolling down macOS or touchpad related
https://bugs.documentfoundation.org/show_bug.cgi?id=135478 Commit Notification changed: What|Removed |Added Whiteboard||target:24.8.0 -- You are receiving this mail because: You are the assignee for the bug.
core.git: sc/source vcl/osx
sc/source/ui/inc/tabview.hxx |2 +
sc/source/ui/view/tabview.cxx | 46 ++
vcl/osx/salframeview.mm |8 +++
3 files changed, 52 insertions(+), 4 deletions(-)
New commits:
commit 7af5df1d9fc472dc3a770fbff736eafa99d46bde
Author: Patrick Luby
AuthorDate: Mon Dec 25 09:19:48 2023 -0500
Commit: Patrick Luby
CommitDate: Tue Dec 26 20:02:42 2023 +0100
tdf#135478 Reduce sensitivity of horizontal scrollwheel
Problem: at least on macOS, swipe events are very
precise. So, when swiping at a slight angle off of
vertical, swipe events will include a small amount
of horizontal movement. Since horizontal swipe units
are measured in cell widths, these small amounts of
horizontal movement results in shifting many columns
to the right or left while swiping almost vertically.
So my hacky fix is to reduce the amount of horizontal
swipe events to roughly match the "visual distance"
of vertical swipe events.
The reduction factor is arbitrary but is set to
roughly the ratio of default cell width divided by
default cell height. This hacky fix isn't a perfect
fix, but hopefully it reduces the amount of
unexpected horizontal shifting while swiping
vertically to a tolerable amount for most users.
Note: the potential downside of doing this is that
some users might find horizontal swiping to be
slower than they are used to. If that becomes an
issue for enough users, the reduction factor may
need to be lowered to find a good balance point.
Lastly, fix the unbalanced rounding of delta X and Y
values due to using floor() for macOS native swipe
and scroll wheel events.
Change-Id: I8c0c9a3aa688e411c47ebb5e7500f3a50f6f673b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/161278
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
Reviewed-by: Patrick Luby
diff --git a/sc/source/ui/inc/tabview.hxx b/sc/source/ui/inc/tabview.hxx
index 23419f463923..66bbc010eae1 100644
--- a/sc/source/ui/inc/tabview.hxx
+++ b/sc/source/ui/inc/tabview.hxx
@@ -217,6 +217,8 @@ private:
double mfLastZoomScale = 0;
double mfAccumulatedZoom = 0;
+tools::Long mnPendingaHScrollLeftDelta = 0;
+tools::Long mnPendingaHScrollRightDelta = 0;
voidInit();
diff --git a/sc/source/ui/view/tabview.cxx b/sc/source/ui/view/tabview.cxx
index fd9e88d18f31..9eff50195e84 100644
--- a/sc/source/ui/view/tabview.cxx
+++ b/sc/source/ui/view/tabview.cxx
@@ -1217,6 +1217,52 @@ void ScTabView::ScrollHdl(ScrollAdaptor* pScroll)
else
nDelta = 0;
}
+else if ( bHoriz )
+{
+// tdf#135478 Reduce sensitivity of horizontal scrollwheel
+// Problem: at least on macOS, swipe events are very
+// precise. So, when swiping at a slight angle off of
+// vertical, swipe events will include a small amount
+// of horizontal movement. Since horizontal swipe units
+// are measured in cell widths, these small amounts of
+// horizontal movement results in shifting many columns
+// to the right or left while swiping almost vertically.
+// So my hacky fix is to reduce the amount of horizontal
+// swipe events to roughly match the "visual distance"
+// of vertical swipe events.
+// The reduction factor is arbitrary but is set to
+// roughly the ratio of default cell width divided by
+// default cell height. This hacky fix isn't a perfect
+// fix, but hopefully it reduces the amount of
+// unexpected horizontal shifting while swiping
+// vertically to a tolerable amount for most users.
+// Note: the potential downside of doing this is that
+// some users might find horizontal swiping to be
+// slower than they are used to. If that becomes an
+// issue for enough users, the reduction factor may
+// need to be lowered to find a good balance point.
+static const sal_uInt16 nHScrollReductionFactor = 8;
+if ( pScroll == aHScrollLeft.get() )
+{
+mnPendingaHScrollLeftDelta += nDelta;
+nDelta = 0;
+if ( abs(mnPendingaHScrollLeftDelta) >
nHScrollReductionFactor )
+{
+nDelta = mnPendingaHScrollLeftDelta /
nHScrollReductionFactor;
+mnPendingaHScrollLeftDelta =
mnPendingaHScrollLeftDelta %
core.git: framework/source
framework/source/uielement/statusbarmanager.cxx | 42 ++--
1 file changed, 12 insertions(+), 30 deletions(-)
New commits:
commit 0b194702002af52d1e0034d41e497052675eb84a
Author: Julien Nabet
AuthorDate: Tue Dec 26 17:53:48 2023 +0100
Commit: Julien Nabet
CommitDate: Tue Dec 26 19:56:36 2023 +0100
Simplify aPropVector construction in framework/statusbarmanager
Change-Id: I14dfe9f156109c9c098e27fcf88ca9a273e7722c
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/161308
Tested-by: Jenkins
Reviewed-by: Julien Nabet
diff --git a/framework/source/uielement/statusbarmanager.cxx
b/framework/source/uielement/statusbarmanager.cxx
index dbc305c696fa..3efb64c44bfd 100644
--- a/framework/source/uielement/statusbarmanager.cxx
+++ b/framework/source/uielement/statusbarmanager.cxx
@@ -34,6 +34,7 @@
#include
#include
#include
+#include
#include
#include
#include
@@ -299,38 +300,19 @@ void StatusBarManager::CreateControllers()
AddonStatusbarItemData *pItemData = static_cast<
AddonStatusbarItemData *>( m_pStatusBar->GetItemData( nId ) );
uno::Reference< ui::XStatusbarItem > xStatusbarItem = new
StatusbarItem( m_pStatusBar, nId, aCommandURL );
-beans::PropertyValue aPropValue;
-std::vector< uno::Any > aPropVector;
-
-aPropValue.Name = "CommandURL";
-aPropValue.Value<<= aCommandURL;
-aPropVector.push_back( uno::Any( aPropValue ) );
-
-aPropValue.Name = "ModuleIdentifier";
-aPropValue.Value<<= OUString();
-aPropVector.push_back( uno::Any( aPropValue ) );
-
-aPropValue.Name = "Frame";
-aPropValue.Value<<= m_xFrame;
-aPropVector.push_back( uno::Any( aPropValue ) );
-
-// TODO remove this
-aPropValue.Name = "ServiceManager";
-aPropValue.Value<<=
uno::Reference(m_xContext->getServiceManager(),
uno::UNO_QUERY_THROW);
-aPropVector.push_back( uno::Any( aPropValue ) );
-
-aPropValue.Name = "ParentWindow";
-aPropValue.Value<<= xStatusbarWindow;
-aPropVector.push_back( uno::Any( aPropValue ) );
+std::vector< uno::Any > aPropVector
+{
+uno::Any(comphelper::makePropertyValue("CommandURL", aCommandURL)),
+uno::Any(comphelper::makePropertyValue("ModuleIdentifier",
u""_ustr)),
+uno::Any(comphelper::makePropertyValue("Frame", m_xFrame)),
-// TODO still needing with the css::ui::XStatusbarItem?
-aPropValue.Name = "Identifier";
-aPropValue.Value<<= nId;
-aPropVector.push_back( uno::Any( aPropValue ) );
+// TODO remove this
+uno::Any(comphelper::makePropertyValue("ServiceManager",
uno::Reference(m_xContext->getServiceManager(),
uno::UNO_QUERY_THROW))),
-aPropValue.Name = "StatusbarItem";
-aPropValue.Value<<= xStatusbarItem;
-aPropVector.push_back( uno::Any( aPropValue ) );
+uno::Any(comphelper::makePropertyValue("ParentWindow",
xStatusbarWindow)),
+uno::Any(comphelper::makePropertyValue("Identifier", nId)),
+uno::Any(comphelper::makePropertyValue("StatusbarItem",
xStatusbarItem))
+};
uno::Sequence< uno::Any > aArgs( comphelper::containerToSequence(
aPropVector ) );
[Bug 158864] Many/most dark mode UI elements have too strong a contrast
https://bugs.documentfoundation.org/show_bug.cgi?id=158864 John Mills changed: What|Removed |Added CC||jmill...@yahoo.com --- Comment #6 from John Mills --- Created attachment 191599 --> https://bugs.documentfoundation.org/attachment.cgi?id=191599=edit Windows 11 dark mode LibreOffice LibreOffice under Windows 11, note the panel colour compared to Linux GTK. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158864] Many/most dark mode UI elements have too strong a contrast
https://bugs.documentfoundation.org/show_bug.cgi?id=158864 John Mills changed: What|Removed |Added CC||jmill...@yahoo.com --- Comment #6 from John Mills --- Created attachment 191599 --> https://bugs.documentfoundation.org/attachment.cgi?id=191599=edit Windows 11 dark mode LibreOffice LibreOffice under Windows 11, note the panel colour compared to Linux GTK. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158864] Many/most dark mode UI elements have too strong a contrast
https://bugs.documentfoundation.org/show_bug.cgi?id=158864 --- Comment #5 from John Mills --- I should say that the poster is using Microsoft Windows, where again the UI is inferior to the Linux Version. See screenshot. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158864] Many/most dark mode UI elements have too strong a contrast
https://bugs.documentfoundation.org/show_bug.cgi?id=158864 --- Comment #5 from John Mills --- I should say that the poster is using Microsoft Windows, where again the UI is inferior to the Linux Version. See screenshot. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158872] New: EDITING - Crash in: cppu::icopyConstructSequence(_sal_Sequence *,_typelib_TypeDescriptionReference *,void (*)(void *),_uno_Mapping *)
https://bugs.documentfoundation.org/show_bug.cgi?id=158872 Bug ID: 158872 Summary: EDITING - Crash in: cppu::icopyConstructSequence(_sal_Sequence *,_typelib_TypeDescriptionReference *,void (*)(void *),_uno_Mapping *) Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: vabel...@ptd.net This bug was filed from the crash reporting server and is br-0cbede84-f031-43f6-abc8-eadfb6d3f87c. = I had six documents open and minimized. I restored one and was attempting to change a cell when LibreOffice crashed. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158864] Many/most dark mode UI elements have too strong a contrast
https://bugs.documentfoundation.org/show_bug.cgi?id=158864 --- Comment #4 from John Mills --- There are too many black panels, you should compare this to the dark mode in OnlyOffice and MSO365 to understand what the original poster is saying. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158864] Many/most dark mode UI elements have too strong a contrast
https://bugs.documentfoundation.org/show_bug.cgi?id=158864 --- Comment #4 from John Mills --- There are too many black panels, you should compare this to the dark mode in OnlyOffice and MSO365 to understand what the original poster is saying. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 36310] [EDITING]"Insert cross-reference" drag-n-drop mode for navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=36310 --- Comment #11 from Christian Lehmann --- In my work, the types of info associated with a reference - i.e., page number, chapter number, chapter title or what not - are generally kept constant throughout a document. I.o.w., if I refer to another chapter, I do this always in the same format, rather than mentioning its number in one reference and mentioning its title in another reference. The Insert- Cross-reference window with its subwindows stores the user's choice and reapplies it in the next reference unless he changes it. Excellent. For the new feature requested (insert a cross-reference upon right-click on a Navigator item), the above choices could simply be applied in the same way. I.o.w., they need not be offered during this action. If the user wants to change them, he can always do so in the Insert - Cross-reference dialog. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158871] New: Stepped chart type can't change its properties
https://bugs.documentfoundation.org/show_bug.cgi?id=158871 Bug ID: 158871 Summary: Stepped chart type can't change its properties Product: LibreOffice Version: 7.6.4.1 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: simplelogin-newsletter.sibling...@simplelogin.com Description: When using a XY (Scatter) > Points and Lines > Line Type: Stepped type of chart, if I want to change the default property of "Start with horizontal line" to "End with horizontal line", after touching "OK" it doesn't apply the change to the property. Tried selecting a different property and the result is the same one (no change over the default property). Steps to Reproduce: 1. Create a XY (Scatter) chart 2. After creating it, go to Chart Type, "Properties", and select "End with horizontal line" 3. Select "OK" and "OK" 4. Chart didn't change Actual Results: No change over the property Expected Results: To change the property of the chart Reproducible: Always User Profile Reset: No Additional Info: Using Arch, Kernel 6.6.7 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 144733] Introduce new interaction to open cross-references in a second window
https://bugs.documentfoundation.org/show_bug.cgi?id=144733 --- Comment #16 from Christian Lehmann --- In version 7.6.2.1 (and for some versions back), the Recency tab in the Navigator has been working very well if you want to navigate back to where you came from. I still consider the suggestion of comment 14 an excellent idea. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 141790] VIEW: Keep position of document in second LO window still (1)
https://bugs.documentfoundation.org/show_bug.cgi?id=141790 --- Comment #9 from Christian Lehmann --- Version 7.6.2.1 on OpenSuse Linux: Bug has been rectified. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158870] Deleted/Left Out functionality
https://bugs.documentfoundation.org/show_bug.cgi?id=158870 Julien Nabet changed: What|Removed |Added Summary|Deleted/Left Out|Deleted/Left Out |Functioality|functionality -- You are receiving this mail because: You are the assignee for the bug.
[Bug 113605] TABLES: Column/row properties of cells should be preserved on copy into an existing table (Paste Special should insert the source unformatted)
https://bugs.documentfoundation.org/show_bug.cgi?id=113605 --- Comment #10 from Christian Lehmann --- Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 60(Build:1) CPU threads: 12; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: en-US Calc: threaded Behavior is now as follows: 1) Select and copy an _entire_ cell to a different cell of the same table or to a cell of another table: Content with paragraph properties is transferred: okay. Cell attributes (e.g. background color) are not transferred: wrong. 2) Copy a _substring_ from a formated paragraph (no matter whether from running text or from a table cell) into a table cell: Source paragraph format overrides table cell format: wrong. Behavior #2 is a more general defect of LO Writer: If I copy a _substring_ of a paragraph formated with style A into a paragraph formated with style B, style A must not be transferred; style B must be preserved. Style A ought not, in fact, be included in the copy in the first place; it is of no concern to the copy operation. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158861] 保存的ODF格式不能被word2007打开
https://bugs.documentfoundation.org/show_bug.cgi?id=158861 V Stuart Foote changed: What|Removed |Added Resolution|--- |NOTOURBUG CC||vsfo...@libreoffice.org Status|UNCONFIRMED |RESOLVED --- Comment #1 from V Stuart Foote --- gloss from Google translate: The saved ODF format file cannot be opened by word2007. It prompts that the file is damaged. Do you want to repair it? Click Repair to open the text. Actual Results: Pop-up prompt: The file is damaged. Do you want to repair it? Expected Results: After clicking Repair, the text can be opened. So, attempting to open an ODF in Word 2007, this error is not our bug but rather MS Office 2007 Word support. Please retest with more recent version of MS Word (2010, 2013, 2016, 2019, or 2021). Alternatively, you could work with a MS Binary (.DOC) or MS OOXML (.DOCX) format file. You might have better results. Google translate gloss: 因此，尝试在 Word 2007 中打开 ODF 时，此错误不是我们的错误，而是 MS Office 2007 Word 支持的错误。 请使用更新版本的 MS Word（2010、2013、2016、2019 或 2021）重新测试。 或者，您可以使用 MS Binary (.DOC) 或 MS OOXML (.DOCX) 格式文件。 你可能会有更好的结果。 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158862] LibreOffice crashes when attempting to inspect a UNO object in the Watch Window during debugging after successful initial inspection.
https://bugs.documentfoundation.org/show_bug.cgi?id=158862 --- Comment #9 from Mike Kaganski --- FTR: an example how this works is in SfxFrameLoader_Impl::load [1], which employs the Frame-Controller-Model Paradigm [2] [3]. In line 707, it creates an instance of the class (e.g., "com.sun.star.text.TextDocument"); then it either calls its attachResource (ln 713), or load (ln 720), to actually create/load the document. Before calling these, the object is not properly initialized. Possibly the most correct is to have a check in the beginning of the UNO methods implementations, that would check if the doc is, and throw NotInitializedException [4] if it is not. [1] https://opengrok.libreoffice.org/xref/core/sfx2/source/view/frmload.cxx?r=789a737a#706 [2] https://wiki.documentfoundation.org/Documentation/DevGuide/Office_Development#Frame-Controller-Model_Paradigm_in_LibreOffice [3] https://wiki.documentfoundation.org/Documentation/DevGuide/Office_Development#Getting_Frames%2C_Controllers_and_Models_from_Each_Other [4] https://api.libreoffice.org/docs/idl/ref/exceptioncom_1_1sun_1_1star_1_1lang_1_1NotInitializedException.html -- You are receiving this mail because: You are the assignee for the bug.
[Bug 140353] UI: Caret merely visible in Writer, LibreOffice (Ubuntu Snap) does not use system settings
https://bugs.documentfoundation.org/show_bug.cgi?id=140353 Dieter changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |WORKSFORME CC||m...@dgirke.de --- Comment #5 from Dieter --- (In reply to Detlef Girke from comment #4) > > In macOS, there is absolutely no way to change the text cursor thickness > unless it is provided by the app itself. Some apps do, some don´t. > LibreOffice doesn´t and never did. > > For me, as a parially sighted person and most of the time working with > macOS, every version of LO starting with 7.x isn´t accessible at all just > because of the much too thin input caret in writer. I just had a look at the > first beta of LO 24.2. The text cursor even went thinner! So disappointing > that people with low vision seem to be more ignored with everey new version > of LO. Accessibility isn´t just something for people using screenreaders, > folks! Detlef, thank you for your comment. Since this bug report is related to Linux, it would be better to open a new report. Thank you. => Back to RESOLVED WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Bug 116143] [META] Text cursor (caret) bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=116143 Bug 116143 depends on bug 140353, which changed state. Bug 140353 Summary: UI: Caret merely visible in Writer, LibreOffice (Ubuntu Snap) does not use system settings https://bugs.documentfoundation.org/show_bug.cgi?id=140353 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Bug 90520] Base crashes with Oracle ODBC driver when sorting/filtering
https://bugs.documentfoundation.org/show_bug.cgi?id=90520 --- Comment #23 from Noel Grandin --- (In reply to grongo2 from comment #22) > To tell the truth, the handling of this bug is disheartening: eight year ago Welcome to how open-source works. This is a 10 million line codebase with only a handful of maintainers. Identifying the problem is great, but often only the first step in a much larger process. Feel free to get involved and submit a code fix. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 113050] FILEOPEN: PDF freezes Draw, one page, 19 KB file
https://bugs.documentfoundation.org/show_bug.cgi?id=113050 --- Comment #20 from Noel Grandin --- (In reply to Dave Gilbert from comment #19) > > it looks like poppler has a hook to tell the output device about the whole > pattern in one go (useTilingPatternFill and tilingPatternFill), so > implementing that would do it. > Sounds like a good idea to me - just make sure that callback is available in our oldest supported version of poppler - if it is not you will need to scatter some #ifdef around and have some fallback code. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158870] New: Deleted/Left Out Functioality
https://bugs.documentfoundation.org/show_bug.cgi?id=158870 Bug ID: 158870 Summary: Deleted/Left Out Functioality Product: LibreOffice Version: unspecified Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Chart Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dbon...@gmail.com The problem is not in formatting. It was meant to be an example without actully providing any personal information. I have a great number of individual spreadsheets for finanancial indicies and entities that I follow. Rather than scroll through numerous spreadsheets I I have used the URL method to have one composite spreadsheet that has a chart for each individual spreadsheet. I started doing that back with Sun’s Star 8 or 9. This has worked up until sometime in 2022/23, with various versions of Star, Apache, and LibreOffice. I am now using LibO 7.6.4.1. The problem is that now you can neither Copy nor Create a chart that uses data from another spread sheet. by using either URL paths or by selecting the data from another spreadsheet. Here are generic examples o fURL paths that have worked in the past: Data Range ‘file:///C:/Users/User Name/Cloud Service/File Folder/DJIAHistory.ods’#$Sheet2.$A$41:$C$79,$Sheet2.$B$1:$C$1 Data Series: Wks Avg Name ‘file:///C:/Users/User Name/Cloud Service/File Folder/DJIA History.ods’#$Sheet2.$B$1:$B$1 x values ‘file:///C:/Users/User Name/Cloud Service/File Folder/DJIA History.ods’#$Sheet2.$A$41:$A$79 y values ‘file:///C:/Users/User Name/Cloud Service/File Folder/DJIA History.ods’#$Sheet2.$B$41:$B$79 Moving Avg Name ‘file:///C:/Users/User Name/Cloud Service/File Folder/DJIA History.ods’#$Sheet2.$C$1:$C$1 x values ‘file:///C:/Users/User Name/Cloud Service/File Folder/DJIA History.ods’#$Sheet2.$A$41:$A$79 y values ‘file:///C:/Users/User Name/Cloud Service/File Folder/DJIA History.ods’#$Sheet2.$C$41:$C$79 Data Series: Data Range ‘file:///C:/Users/User Name/Cloud Service/File Folder/NASDAQ History.ods’#$Sheet2.$A$41:$C$79,$Sheet2.$B$1:$C$1 Wks Avg Name ‘file:///C:/Users/User Name/Cloud Service/File Folder/NASDAQ History.ods’#$Sheet2.$B$1:$B$1 x values ‘file:///C:/Users/User Name/Cloud Service/File Folder/NASDAQ History.ods’#$Sheet2.$A$41:$A$79 y values ‘file:///C:/Users/User Name/Cloud Service/File Folder/NASDAQ History.ods’#$Sheet2.$B$41:$B$79 Moving Avg Name ‘file:///C:/Users/User Name/Cloud Service/File Folder/NASDAQ History.ods’#$Sheet2.$C$1:$C$1 x values ‘file:///C:/Users/User Name/Cloud Service/File Folder/NASDAQ History.ods’#$Sheet2.$A$41:$A$79 y values ‘file:///C:/Users/User Name/Cloud Service/File Folder/NASDAQ History.ods’#$Sheet2.$C$41:$C$79 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 151679] Clipboard contents on Mac cause trouble with clipboard recorders
https://bugs.documentfoundation.org/show_bug.cgi?id=151679 Patrick Luby changed: What|Removed |Added Status|NEW |RESOLVED Assignee|libreoffice-b...@lists.free |plub...@libreoffice.org |desktop.org | Resolution|--- |FIXED --- Comment #17 from Patrick Luby --- I have committed my fix for this bug and it will be included in tomorrow's (27 December 2023) nightly master build: https://dev-builds.libreoffice.org/daily/master/current.html LibreOffice already has its own internal, private clipboard so all I needed to do was filter out the unwanted data flavor when declaring available types on the macOS system clipboard. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158862] LibreOffice crashes when attempting to inspect a UNO object in the Watch Window during debugging after successful initial inspection.
https://bugs.documentfoundation.org/show_bug.cgi?id=158862 --- Comment #8 from Mike Kaganski --- (In reply to Julien Nabet from comment #7) > The pb is m_pDocShell->GetDoc() returns null whereas macro just created > ""com.sun.star.text.TextDocument" object. Synchro pb? No, it is correct: there is no document in the "com.sun.star.text.TextDocument" UNO object created like this (see Writer_SwTextDocument_get_implementation). The code in sw/source/uibase/uno/unotxdoc.cxx wrongly expects m_pDocShell->GetDoc() to return a non-null value. In line 2085, there should be a check for this (and I bet, that there will be lots of similar things over the file). -- You are receiving this mail because: You are the assignee for the bug.
