[Bug 139112] Accessibility options dialog should adapt its width to long labels
https://bugs.documentfoundation.org/show_bug.cgi?id=139112 Łukasz changed: What|Removed |Added Version|7.0.4.2 release |24.2.0.3 release -- You are receiving this mail because: You are the assignee for the bug.
[Bug 139112] Accessibility options dialog should adapt its width to long labels
https://bugs.documentfoundation.org/show_bug.cgi?id=139112 --- Comment #45 from Łukasz --- Created attachment 192365 --> https://bugs.documentfoundation.org/attachment.cgi?id=192365=edit base1 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 139112] Accessibility options dialog should adapt its width to long labels
https://bugs.documentfoundation.org/show_bug.cgi?id=139112 --- Comment #44 from Łukasz --- Created attachment 192364 --> https://bugs.documentfoundation.org/attachment.cgi?id=192364=edit setting1 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 139112] Accessibility options dialog should adapt its width to long labels
https://bugs.documentfoundation.org/show_bug.cgi?id=139112 --- Comment #43 from Łukasz --- Created attachment 192363 --> https://bugs.documentfoundation.org/attachment.cgi?id=192363=edit setting -- You are receiving this mail because: You are the assignee for the bug.
[Bug 139112] Accessibility options dialog should adapt its width to long labels
https://bugs.documentfoundation.org/show_bug.cgi?id=139112 --- Comment #42 from Łukasz --- please correct it, just expand the window. libreoffice 24.2.0 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159537] New: Bootstrap in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=159537 Bug ID: 159537 Summary: Bootstrap in Writer Product: LibreOffice Version: 24.2.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Web Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: bo...@clocked.eu Description: It would be nice to have the ability to link a bootstrap file to a document. And to have the option "Web Page" under File and in the Startcenter. And automatic use ".html" as default if working in Web Mode in Writer (not .odt). In short, more real single web-page edit features to edit single responsive webpages. Steps to Reproduce: There is a need to make single web pages. I know (and use) there are other tools for this. But this would be really nice for making LO the goto tool for all offline working. Actual Results: Produce better looking web pages with a consistency among the pages. Expected Results: More use off LO to make small static websites. Reproducible: Always User Profile Reset: No Additional Info: == -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159509] Libre Math --> dark fonts in editor in dark background (dark theme)
https://bugs.documentfoundation.org/show_bug.cgi?id=159509 --- Comment #8 from george --- Mint-Y Dark theme (among the standards Mint's dark themes) was the culprit. Once I used adwaita-dark (among the standards also), problem was solved. Thanks for the info, you helped me find the culprit. This was very strange... -- You are receiving this mail because: You are the assignee for the bug.
New Defects reported by Coverity Scan for LibreOffice
Hi,
Please find the latest report on new defect(s) introduced to LibreOffice found
with Coverity Scan.
16 new defect(s) introduced to LibreOffice found with Coverity Scan.
5 defect(s), reported by Coverity Scan earlier, were marked fixed in the recent
build analyzed by Coverity Scan.
New defect(s) Reported-by: Coverity Scan
Showing 16 of 16 defect(s)
** CID 1591496: Null pointer dereferences (NULL_RETURNS)
*** CID 1591496: Null pointer dereferences (NULL_RETURNS)
/sw/source/core/layout/atrfrm.cxx: 2637 in SwFrameFormat::SetFormatName(const
rtl::OUString &, bool)()
2631 if (!aHint.m_sOld.isEmpty() && aHint.m_sOld != aHint.m_sNew)
2632 {
2633 if (SwFlyFrame* pSFly = SwIterator(*this).First())
2634 {
2635 if (pSFly->Lower() && !pSFly->Lower()->IsNoTextFrame())
2636 {
>>> CID 1591496: Null pointer dereferences (NULL_RETURNS)
>>> Dereferencing a pointer that might be "nullptr"
>>> "static_cast(pSFly->ContainsContent())" when calling
>>> "GetTextNodeFirst".
2637 if (SwTextNode* pSwTxtNode =
static_cast(pSFly->ContainsContent())->GetTextNodeFirst())
2638
pSwTxtNode->resetAndQueueAccessibilityCheck(true);
2639 }
2640 else
2641 {
2642 if (SwNode* pSwNode =
static_cast(pSFly->Lower())->GetNode())
** CID 1591495: Resource leaks (RESOURCE_LEAK)
/test/source/xmltesttools.cxx: 306 in XmlTestTools::assertXPathNodeName(const
std::unique_ptr<_xmlDoc, xmlDocDeleter> &, const rtl::OString &, const
rtl::OString &)()
*** CID 1591495: Resource leaks (RESOURCE_LEAK)
/test/source/xmltesttools.cxx: 306 in XmlTestTools::assertXPathNodeName(const
std::unique_ptr<_xmlDoc, xmlDocDeleter> &, const rtl::OString &, const
rtl::OString &)()
300 CPPUNIT_ASSERT_EQUAL_MESSAGE(OString(OString::Concat("In <") +
pXmlDoc->name + ">, XPath '" + rXPath + "' number of nodes is
incorrect").getStr(),
301 1,
302 xmlXPathNodeSetGetLength(pXmlNodes));
303 xmlNodePtr pXmlNode = pXmlNodes->nodeTab[0];
304 CPPUNIT_ASSERT_EQUAL_MESSAGE(OString(OString::Concat("In XPath '" +
rXPath + "' name of node is incorrect")).getStr(),
305 rExpectedName,
oconvert(pXmlNode->name));
>>> CID 1591495: Resource leaks (RESOURCE_LEAK)
>>> Variable "pXmlObj" going out of scope leaks the storage it points to.
306 }
307
308 void XmlTestTools::registerODFNamespaces(xmlXPathContextPtr&
pXmlXpathCtx)
309 {
310 xmlXPathRegisterNs(pXmlXpathCtx, BAD_CAST("manifest"),
311
BAD_CAST("urn:oasis:names:tc:opendocument:xmlns:manifest:1.0"));
** CID 1591494: Null pointer dereferences (NULL_RETURNS)
*** CID 1591494: Null pointer dereferences (NULL_RETURNS)
/sw/source/core/layout/trvlfrm.cxx: 1533 in
SwRootFrame::GetNextPrevContentPos(const Point &, bool) const()
1527 while ( !pCnt )
1528 {
1529 pPage = static_cast(pPage->GetPrev());
1530 if ( pPage )
1531 pCnt = pPage->ContainsContent();
1532 else
>>> CID 1591494: Null pointer dereferences (NULL_RETURNS)
>>> Dereferencing a pointer that might be "nullptr"
>>> "this->ContainsContent()" when calling "UnionFrame".
1533 return ContainsContent()->UnionFrame().Pos();
1534 }
1535 pCnt->Calc(pRenderContext);
1536 }
1537 }
1538
** CID 1591493: Error handling issues (CHECKED_RETURN)
/comphelper/source/xml/xmltools.cxx: 79 in comphelper::xml::makeXMLChaff()()
*** CID 1591493: Error handling issues (CHECKED_RETURN)
/comphelper/source/xml/xmltools.cxx: 79 in comphelper::xml::makeXMLChaff()()
73 {
74 OString makeXMLChaff()
75 {
76 rtlRandomPool pool = rtl_random_createPool();
77
78 sal_Int8 n;
>>> CID 1591493: Error handling issues (CHECKED_RETURN)
>>> Calling "rtl_random_getBytes" without checking return value (as is done
>>> elsewhere 13 out of 16 times).
79 rtl_random_getBytes(pool, , 1);
80
81 sal_Int32 nLength = 1024+n;
82 // coverity[tainted_data] - 1024 deliberate random minus max
-127/plus max 128
83
[Bug 148044] Register view looks strange
https://bugs.documentfoundation.org/show_bug.cgi?id=148044 Dieter changed: What|Removed |Added CC||dgp-m...@gmx.de --- Comment #13 from Dieter --- (In reply to Buovjaga from comment #12) > Ok, an exotic Budgie-related theme. Can you change it to the default Ubuntu > theme and see what happens? Matthias, any results of tre test? Please test with actual version LO 24.2. Thank you => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Bug 141265] Random characters appear as black boxes at certain zoom levels in windows 10.
https://bugs.documentfoundation.org/show_bug.cgi?id=141265 Dieter changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #13 from Dieter --- (In reply to Buovjaga from comment #12) > Works fine for me > Allan, does the problem still appear in LO actual version 24.2? => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159509] Libre Math --> dark fonts in editor in dark background (dark theme)
https://bugs.documentfoundation.org/show_bug.cgi?id=159509 --- Comment #7 from george --- (In reply to Rafael Lima from comment #5) > I tried with LO 7.6 and 24.2 both on Ubuntu (gtk3) and Kubuntu (kf5) and I > could not reproduce the problem. > > Do you have any theme installed on your machine? can you post here a screenshot with libre math open and dark theme? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159509] Libre Math --> dark fonts in editor in dark background (dark theme)
https://bugs.documentfoundation.org/show_bug.cgi?id=159509 --- Comment #6 from george --- (In reply to Rafael Lima from comment #5) > I tried with LO 7.6 and 24.2 both on Ubuntu (gtk3) and Kubuntu (kf5) and I > could not reproduce the problem. > > Do you have any theme installed on your machine? No extra themes are installed. I use the default Linux Mint's dark theme. So, if you can't reproduce the problem must be something with linux mint's settings... Strange. I have no similar problems with other applications... Only libre math... -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159286] Single click inside text field should select full field if it has the placeholder text
https://bugs.documentfoundation.org/show_bug.cgi?id=159286 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159291] libwpd - WPD2HTML doesn't handle legal pleading styling in WPD files
https://bugs.documentfoundation.org/show_bug.cgi?id=159291 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159287] Strip whitespace from .ui files, or compress them
https://bugs.documentfoundation.org/show_bug.cgi?id=159287 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159290] libwpd - WPD2HTML fails to handle WPD text columns properly
https://bugs.documentfoundation.org/show_bug.cgi?id=159290 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159276] Enhancement: Pop-up menu "Replace ..." add "from clipboard"
https://bugs.documentfoundation.org/show_bug.cgi?id=159276 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159129] Cross Reference not working in LO 7.6
https://bugs.documentfoundation.org/show_bug.cgi?id=159129 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159129] Cross Reference not working in LO 7.6
https://bugs.documentfoundation.org/show_bug.cgi?id=159129 --- Comment #15 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 87351] [META] Conditional formatting bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=87351 Bug 87351 depends on bug 84763, which changed state. Bug 84763 Summary: Poor performance entering data with conditional formatting https://bugs.documentfoundation.org/show_bug.cgi?id=84763 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 84763] Poor performance entering data with conditional formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=84763 --- Comment #16 from QA Administrators --- Dear rlk, 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 156519] Dates for the year 2000 do not format correctly when entered as xx/xx/2000
https://bugs.documentfoundation.org/show_bug.cgi?id=156519 --- Comment #5 from QA Administrators --- Dear Bob Steen, 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 84763] Poor performance entering data with conditional formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=84763 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 49171] FORMATTING: Header background color not changed correctly when Same content left/right unset
https://bugs.documentfoundation.org/show_bug.cgi?id=49171 --- Comment #9 from QA Administrators --- Dear Angelo Locritani, 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 72203] EDITING: in a table: moving upwards should go to the last line of the cell, not to the first
https://bugs.documentfoundation.org/show_bug.cgi?id=72203 --- Comment #13 from QA Administrators --- Dear Jérôme Borme, 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 139930] Objects anchored to frame don't move when frame moves (Linux-only)
https://bugs.documentfoundation.org/show_bug.cgi?id=139930 --- Comment #9 from QA Administrators --- Dear Steve Edmonds, 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 145889] Autofilter result is wrong if the column contains the number "1000" and the text "'1000"
https://bugs.documentfoundation.org/show_bug.cgi?id=145889 --- Comment #6 from QA Administrators --- Dear Kevin Suo, 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 119519] Basic: insert graphicobject via ThisComponent.createInstance("com.sun.star.text.GraphicObject") not working in 6.1.0.3
https://bugs.documentfoundation.org/show_bug.cgi?id=119519 --- Comment #14 from QA Administrators --- Dear Kai Struck, 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.
core.git: solenv/vs
solenv/vs/LibreOffice.natstepfilter |6 +- 1 file changed, 5 insertions(+), 1 deletion(-) New commits: commit de1d9d8302e600e6cc3964f55790d954fd493df9 Author: Mike Kaganski AuthorDate: Fri Feb 2 22:55:33 2024 +0600 Commit: Mike Kaganski CommitDate: Sat Feb 3 03:54:56 2024 +0100 natstepfilter: skip std::vector::operator[] Change-Id: I6605b4bc74ba186e06693ef5346e7b7fd0c0b9df Reviewed-on: https://gerrit.libreoffice.org/c/core/+/162938 Tested-by: Jenkins Reviewed-by: Mike Kaganski diff --git a/solenv/vs/LibreOffice.natstepfilter b/solenv/vs/LibreOffice.natstepfilter index 601c98121054..6098ef9fb980 100644 --- a/solenv/vs/LibreOffice.natstepfilter +++ b/solenv/vs/LibreOffice.natstepfilter @@ -8,6 +8,10 @@ std::shared_ptr.*::operator- NoStepInto + +>std::vector.*::operator[] +NoStepInto + tools::SvRef.*::operator- NoStepInto @@ -20,4 +24,4 @@ rtl::Reference.*::operator- NoStepInto - \ No newline at end of file +
[Bug 159532] Deleting first or last row from a table referenced in a table function makes it invalid
https://bugs.documentfoundation.org/show_bug.cgi?id=159532 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #2 from m_a_riosv --- It works the same as it does in Calc. Deleting the first or last row (cell) of a range broke the range. But deleting some row (cell) inside the range doesn't, the range is reduced, to adapt the last row (cell) to the new range. In the second case, the new range is B1:B2 instead B1:B3. I think there is not a bug. Tested with Version: 24.2.1.0.0+ (X86_64) / LibreOffice Community Build ID: cafcc50570f9edaaebe74d2152bae5df1cc2edfe CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded + Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1647493e5cbb9cf4f06b7d0387d6763a2f30fdae CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159523] Impress crashes when "filling" an ellipsis with no color
https://bugs.documentfoundation.org/show_bug.cgi?id=159523 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #4 from m_a_riosv --- Not reproducible Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Please test in safe mode, Menu/Help/Restart in Safe Mode -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159512] LibreOffice Calc ODS files saved with passwords under 7.6.4 (X86_64) cannot be opened in 24.2.0.3 (X86_64).
https://bugs.documentfoundation.org/show_bug.cgi?id=159512 --- Comment #15 from m_a_riosv --- Not reproducible: Version: 24.2.1.0.0+ (X86_64) / LibreOffice Community Build ID: cafcc50570f9edaaebe74d2152bae5df1cc2edfe CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159536] New: FILEOPEN PPTX setting 'Keep text flat' is ignored
https://bugs.documentfoundation.org/show_bug.cgi?id=159536 Bug ID: 159536 Summary: FILEOPEN PPTX setting 'Keep text flat' is ignored Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de Created attachment 192362 --> https://bugs.documentfoundation.org/attachment.cgi?id=192362=edit Example to reproduce the problem Open attached document. It contains 'heart' shapes, which were rotated by using the z-Rotation of a 3D camera. In that settings the option "Keep text flat" was checked. That excludes the text from the z-Rotation, so that it stays horizontal. Error: The text is rotated in LibreOffice. This option is the element in OOXML. There exists already the property TextCameraZRotateAngle in CustomShapeGeometry. It could be used to compensate the shape rotation. But the element is not even read, see https://opengrok.libreoffice.org/xref/core/oox/source/drawingml/textbodypropertiescontext.cxx?r=60bce1af#273 [When Skia is disabled, the text area inside the shapes is wrong in addition, so that the text is cut. But that is a different problem and already reported in bug 157986.] -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159129] Cross Reference not working in LO 7.6
https://bugs.documentfoundation.org/show_bug.cgi?id=159129 --- Comment #14 from Paddy --- (In reply to Heiko Tietze from comment #13) > Does toggling the field highlighting per Ctrl+F8 or via the View menu what > you want? > > (In reply to Paddy from comment #8) > > Created attachment 192049 [details] > 1000+ pages is a hardware challenge. The example could have been just the > first page. > > (In reply to Paddy from comment #5) > > Created attachment 191926 [details] > > Screen print of page where links are not highlighted > You can click the button next to Version Information to copy the data into > your clipboard. Thanks, yes, Ctrl F8 does solve the highlighting problem. I can manage with using Cntrl-Click to activate the link but I still think this is a retrogressive step as a single click worked previously. I was asked to send the entire document so this is what I did, but I take your point -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159535] Writer comments have a shadow that is hardcoded onto a white background even in dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=159535 --- Comment #1 from Jeff Fortin Tam --- Created attachment 192361 --> https://bugs.documentfoundation.org/attachment.cgi?id=192361=edit Annotated screenshot at 2x scale -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157158] [UI] Comment arrow drop down is white/light grey when in dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=157158 Jeff Fortin Tam changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||9535 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 153293] [META] Dark Mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=153293 Jeff Fortin Tam changed: What|Removed |Added Depends on||159535 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=159535 [Bug 159535] Writer comments have a shadow that is hardcoded onto a white background even in dark mode -- You are receiving this mail because: You are the assignee for the bug.
[Bug 106179] [META] Writer comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=106179 Jeff Fortin Tam changed: What|Removed |Added Depends on||159535 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=159535 [Bug 159535] Writer comments have a shadow that is hardcoded onto a white background even in dark mode -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159535] Writer comments have a shadow that is hardcoded onto a white background even in dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=159535 Jeff Fortin Tam changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||7158 Blocks||153293, 106179 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=106179 [Bug 106179] [META] Writer comment bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=153293 [Bug 153293] [META] Dark Mode bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159535] New: Writer comments have a shadow that is hardcoded onto a white background even in dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=159535 Bug ID: 159535 Summary: Writer comments have a shadow that is hardcoded onto a white background even in dark mode Product: LibreOffice Version: 24.2.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: nekoh...@gmail.com Description: The shadow under Writer's comments does not adapt to dark mode on Linux, whether toggled live or before starting the app. Please see the attached screenshot. Steps to Reproduce: 1. Switch your OS to dark theme mode 2. Insert a comment in Writer, type something in it 3. Press "Esc" to exit the comment 4. Optional: hover with the mouse over/outside the comment Actual Results: The shadow is brighter than the backdrop behind the comments. It seems its gradient was hardcoded to a previously lighter backdrop color stop. It is more obvious in dark mode because the margin's backdrop color is darker; if looking closely however, this might even be noticed with the light color scheme. The shadow's behavior changes depending on hover status, too. Expected Results: The shadow gradient should use the backdrop color from the comments margin. In dark mode, maybe there should be no shadow at all; otherwise you'll need a darker shadow. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 CPU threads: 8; OS: Linux 6.6; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Flatpak Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159531] Comments in Writer's margins should have some padding spacing to avoid text being flush to the edge
https://bugs.documentfoundation.org/show_bug.cgi?id=159531 --- Comment #3 from Jeff Fortin Tam --- Slight clarification: while, in the case of this screenshot, my padding simulation was roughly 6 pixels from the left edge, I realize now that from an implementation standpoint this probably needs to be defined as a percentage of the comment widget's width, rather than a hardcoded pixel size, because the comment widget's width scales with the document's based on the view's Zoom Factor; that said, my point overall remains :) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159531] Comments in Writer's margins should have some padding spacing to avoid text being flush to the edge
https://bugs.documentfoundation.org/show_bug.cgi?id=159531 --- Comment #3 from Jeff Fortin Tam --- Slight clarification: while, in the case of this screenshot, my padding simulation was roughly 6 pixels from the left edge, I realize now that from an implementation standpoint this probably needs to be defined as a percentage of the comment widget's width, rather than a hardcoded pixel size, because the comment widget's width scales with the document's based on the view's Zoom Factor; that said, my point overall remains :) -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159453] Importing DOCX: Position of frame has gone
https://bugs.documentfoundation.org/show_bug.cgi?id=159453 Miklos Vajna changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |vmik...@collabora.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159531] Comments in Writer's margins should have some padding spacing to avoid text being flush to the edge
https://bugs.documentfoundation.org/show_bug.cgi?id=159531 Rafael Lima changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||rafael.palma.l...@gmail.com --- Comment #2 from Rafael Lima --- Some padding would be nice indeed. +1 from my side. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159531] Comments in Writer's margins should have some padding spacing to avoid text being flush to the edge
https://bugs.documentfoundation.org/show_bug.cgi?id=159531 Rafael Lima changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||rafael.palma.l...@gmail.com --- Comment #2 from Rafael Lima --- Some padding would be nice indeed. +1 from my side. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159523] Impress crashes when "filling" an ellipsis with no color
https://bugs.documentfoundation.org/show_bug.cgi?id=159523 --- Comment #3 from Rafael Lima --- I can't reproduce this issue with Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: 60(Build:1) CPU threads: 16; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Ubuntu package version: 4:7.6.4-0ubuntu0.23.10.1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
core.git: Branch 'distro/collabora/co-24.04' - desktop/source
desktop/source/lib/init.cxx | 17 +
1 file changed, 17 insertions(+)
New commits:
commit d85cb3832286ae1fdcf4a8494abb8212f21e4e9a
Author: Michael Meeks
AuthorDate: Fri Feb 2 18:16:40 2024 +
Commit: Caolán McNamara
CommitDate: Fri Feb 2 22:47:28 2024 +0100
preload: open and close empty documents of main types in preinit.
Some quick testing suggest this saves ~800k for writer, ~3Mb for
impress each loading an ~empty hello-world document.
Change-Id: I9a7bc25d38d82b5556dfb04a99d5c145dd71ffec
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/162939
Tested-by: Jenkins CollaboraOffice
Reviewed-by: Caolán McNamara
diff --git a/desktop/source/lib/init.cxx b/desktop/source/lib/init.cxx
index 80442dc5ffa2..c76e7a014725 100644
--- a/desktop/source/lib/init.cxx
+++ b/desktop/source/lib/init.cxx
@@ -7553,6 +7553,23 @@ static void preloadData()
#pragma GCC diagnostic pop
#endif
+static const OUString preloadComponents[] = {
+"private:factory/swriter",
+"private:factory/scalc",
+"private:factory/simpress",
+"private:factory/sdraw"
+};
+// getting the remote LibreOffice service manager
+uno::Reference
xCompLoader(frame::Desktop::create(xContext), uno::UNO_QUERY);
+
+// Preload and close each of the main components once to initialize global
state
+uno::Sequence szEmptyArgs(0);
+for (auto component : preloadComponents)
+{
+auto xComp = xCompLoader->loadComponentFromURL(component, "_blank", 0,
szEmptyArgs);
+xComp->dispose();
+}
+
// Set user profile's path back to the original one
rtl::Bootstrap::set(u"UserInstallation"_ustr, sUserPath);
}
[Bug 147291] macOS: Digital Signatures > Start Certificate Manager (OpenPGP) results in error instead of opening GPG Keychain
https://bugs.documentfoundation.org/show_bug.cgi?id=147291 --- Comment #22 from Patrick Luby --- (In reply to Alex Thurgood from comment #21) > I actually have no idea, but would hasard a guess that scManager isn't the > most commonly used app out there, and the TKM whilst apparently specific to > CertEurope is fairly widely used by the French barrister profession for > court submissions, and, so I'm led to believe, by other organisations within > the EU (although I have no actual evidence of that). OK. Let's put TKM first and scManager second and see how that goes. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159527] [RFE] Show splash screen when files are opened from double click
https://bugs.documentfoundation.org/show_bug.cgi?id=159527 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org --- Comment #1 from V Stuart Foote --- You sure? We do get a splash screen on Windows 10 os/DE on file open launch from Windows Explorer file manager. This is without Quickstart. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159461] Dialog "XML Filter Settings" is broken
https://bugs.documentfoundation.org/show_bug.cgi?id=159461 Julien Nabet changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #7 from Julien Nabet --- On pc Debian x86-64 with master sources updated today (including Noel's patch), I confirm I don't reproduce the hang anymore. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 147291] macOS: Digital Signatures > Start Certificate Manager (OpenPGP) results in error instead of opening GPG Keychain
https://bugs.documentfoundation.org/show_bug.cgi?id=147291 --- Comment #21 from Alex Thurgood --- (In reply to Patrick Luby from comment #20) > So which application is used by more people? My guess is that GPGTools is > the most common and macOS' Keychain Access application is the least common > so these two would go in the middle. I just don't have any sense which is > more common. I actually have no idea, but would hasard a guess that scManager isn't the most commonly used app out there, and the TKM whilst apparently specific to CertEurope is fairly widely used by the French barrister profession for court submissions, and, so I'm led to believe, by other organisations within the EU (although I have no actual evidence of that). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159523] Impress crashes when "filling" an ellipsis with no color
https://bugs.documentfoundation.org/show_bug.cgi?id=159523 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org --- Comment #2 from V Stuart Foote --- Can not confirm with these STR Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159528] officehelper.py doesn't function in the context of macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=159528 --- Comment #1 from Rafael Lima --- I do not have a macOS machine to test it. However I got the same error running it on Kubuntu with the PPA installation of LO 7.6. I got: uno.com.sun.star.connection.NoConnectException It works on Windows... a pyuno object is returned. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159534] New: Allow to scroll past the end of the module (Basic IDE)
https://bugs.documentfoundation.org/show_bug.cgi?id=159534 Bug ID: 159534 Summary: Allow to scroll past the end of the module (Basic IDE) Product: LibreOffice Version: 7.6.4.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: BASIC Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rafael.palma.l...@gmail.com When editing the very end of a Basic module, one cannot scroll past the last line, which is inconvenient while programming and makes the user have to enter dummy empty lines to move up the code. Modern code editors allow to scroll past the last line in the code. I suggest we do the same in the Basic IDE. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159461] Dialog "XML Filter Settings" is broken
https://bugs.documentfoundation.org/show_bug.cgi?id=159461 Noel Grandin changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
core.git: 2 commits - compilerplugins/clang filter/source
compilerplugins/clang/test/unnecessarygetstr.cxx |7
compilerplugins/clang/unnecessarygetstr.cxx | 18 +
filter/source/config/cache/filtercache.cxx | 224 ---
filter/source/config/cache/filtercache.hxx | 41 +---
4 files changed, 161 insertions(+), 129 deletions(-)
New commits:
commit 3d5c0a94539d2196c7d0dd9f52660ba9e58d31b8
Author: Noel Grandin
AuthorDate: Fri Feb 2 10:49:14 2024 +0200
Commit: Noel Grandin
CommitDate: Fri Feb 2 20:40:58 2024 +0100
loplugin:unnecessarygetstr fix false +
spotted in https://gerrit.libreoffice.org/c/core/+/162869
Change-Id: I87d9fdcfed5282f0e94fc8aa95a46054883fdd79
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/162929
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/compilerplugins/clang/test/unnecessarygetstr.cxx
b/compilerplugins/clang/test/unnecessarygetstr.cxx
index c0960557a89b..bdb58cde2ef7 100644
--- a/compilerplugins/clang/test/unnecessarygetstr.cxx
+++ b/compilerplugins/clang/test/unnecessarygetstr.cxx
@@ -10,6 +10,7 @@
#include
#include
+#include
#include
#include
@@ -128,4 +129,10 @@ void foo(const OString&);
void test(std::string v) { foo(v.c_str()); }
}
+// no warning expected
+namespace test7
+{
+void test(const OString& v) { std::stringstream aStream(v.getStr()); }
+}
+
/* vim:set shiftwidth=4 softtabstop=4 expandtab cinoptions=b1,g0,N-s
cinkeys+=0=break: */
diff --git a/compilerplugins/clang/unnecessarygetstr.cxx
b/compilerplugins/clang/unnecessarygetstr.cxx
index c80877a78554..589ab405f786 100644
--- a/compilerplugins/clang/unnecessarygetstr.cxx
+++ b/compilerplugins/clang/unnecessarygetstr.cxx
@@ -11,6 +11,7 @@
#include
#include
+#include
#include "check.hxx"
#include "plugin.hxx"
@@ -60,11 +61,20 @@ public:
if (ignoreLocation(constructExpr))
return true;
auto tc = loplugin::TypeCheck(constructExpr->getType());
-if (tc.ClassOrStruct("basic_string").StdNamespace())
+if (tc.ClassOrStruct("basic_stringstream").StdNamespace())
+{
+// ignore the implicit-conversion nodes that are added here
+if (constructExpr->getNumArgs() > 0)
+
nodesToIgnore.insert(constructExpr->getArg(0)->IgnoreImplicit());
+}
+else if (tc.ClassOrStruct("basic_string").StdNamespace())
{
if (constructExpr->getNumArgs() == 1 ||
constructExpr->getNumArgs() == 2)
-checkForGetStr(constructExpr->getArg(0), "string constructor",
- /*isOStringConstructor*/ false);
+{
+if (nodesToIgnore.find(constructExpr) == nodesToIgnore.end())
+checkForGetStr(constructExpr->getArg(0), "string
constructor",
+ /*isOStringConstructor*/ false);
+}
}
else if (tc.ClassOrStruct("basic_string_view").StdNamespace())
{
@@ -138,6 +148,8 @@ private:
TraverseDecl(compiler.getASTContext().getTranslationUnitDecl());
}
}
+
+std::unordered_set nodesToIgnore;
};
loplugin::Plugin::Registration
unnecessarygetstr("unnecessarygetstr");
commit b23aec2266da4cc2b3f4a34037d3a073a36d3d83
Author: Noel Grandin
AuthorDate: Fri Feb 2 18:51:59 2024 +0200
Commit: Noel Grandin
CommitDate: Fri Feb 2 20:40:45 2024 +0100
tdf#159461 deadlock in Dialog "XML Filter Settings"
revert
commit 15405dc68b2e88b53585578567da13e3e99962db
Author: Noel Grandin
Date: Mon Feb 20 15:43:41 2023 +0200
osl::Mutex->std::mutex in FilterCache
There is much recursive behaviour going on here,
via the configmgr and the listeners that FilterCache
has.
Change-Id: Ice003404dffad9e5e63bcff30c2ceede4f52cab8
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/162930
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/filter/source/config/cache/filtercache.cxx
b/filter/source/config/cache/filtercache.cxx
index 70c18a841bb4..2abf11a5ada9 100644
--- a/filter/source/config/cache/filtercache.cxx
+++ b/filter/source/config/cache/filtercache.cxx
@@ -119,7 +119,7 @@ FilterCache::~FilterCache()
std::unique_ptr FilterCache::clone() const
{
// SAFE -> --
-std::unique_lock aGuard(m_aMutex);
+osl::MutexGuard aLock(m_aMutex);
auto pClone = std::make_unique();
@@ -151,7 +151,7 @@ std::unique_ptr FilterCache::clone() const
void FilterCache::takeOver(const FilterCache& rClone)
{
// SAFE -> --
-std::unique_lock aGuard(m_aMutex);
+osl::MutexGuard aLock(m_aMutex);
// a)
// Don't copy the configuration access points here!
@@ -192,14 +192,14 @@ void FilterCache::takeOver(const FilterCache& rClone)
// Because we can't be sure, that changed filters on one clone
// and changed types of another clone work
[Bug 159461] Dialog "XML Filter Settings" is broken
https://bugs.documentfoundation.org/show_bug.cgi?id=159461 Commit Notification changed: What|Removed |Added Whiteboard||target:24.8.0 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159277] It would be nice to have an exclude file type option from Recent Files.
https://bugs.documentfoundation.org/show_bug.cgi?id=159277 --- Comment #11 from Rafael Lima --- Created attachment 192360 --> https://bugs.documentfoundation.org/attachment.cgi?id=192360=edit Macro that removes CSV entries from "Recent Documents" This document contains a macro that removes CSV entries from the "Recent Documents" list. The macro is named RemoveFromRecentList and is embedded in this document. You can tinker with it to remove any extensions as you like (see my comments in the code). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159533] New: Add custom separators to all field variables
https://bugs.documentfoundation.org/show_bug.cgi?id=159533 Bug ID: 159533 Summary: Add custom separators to all field variables 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: will.fried...@gmail.com Description: I am requesting the ability to add a custom separator to the insertion of field variables. Here is my use case. I write in my text: "There are ten examples: 1) blah, 2) blah blah, 3) blah blah blah" etc. Each of the numbers is the field variable, but I have to manually enter the parentheses as the separator. I would like to be able to set up the field variable to have a separator, just like one can do with ordinary lists (but since multiple list entries can't go on a single line, number range fields must be used instead). The current option to insert a separator "with heading number" does not do what I want. Ideally the separator could be configurable to allow an arbitrary number of characters *before and after* the number, so that one could automatically insert, e.g. [1]). Thank you for considering this enhancement. Steps to Reproduce: 1. Go to Fields | Variables. 2. See that there is no option for adding a separator. Actual Results: No option for adding a separator. Expected Results: Option for adding a separator. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159532] Deleting first or last row from a table referenced in a table function makes it invalid
https://bugs.documentfoundation.org/show_bug.cgi?id=159532 --- Comment #1 from Gabor Kelemen (allotropia) --- Created attachment 192359 --> https://bugs.documentfoundation.org/attachment.cgi?id=192359=edit Screenshot of the broken formula -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159529] Excessive memory consumption in v24.2
https://bugs.documentfoundation.org/show_bug.cgi?id=159529 Telesto changed: What|Removed |Added Keywords||bibisectRequest, regression Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from Telesto --- I have noticed couple of reports about this in bug tracker, however the cause was a mystery until now.. Confirm Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ba8f4bff6015013013df652efbfaf4d9ae10c881 CPU threads: 8; OS: macOS 14.3; UI render: Skia/Metal; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159532] New: Deleting first or last row from a table referenced in a table function makes it invalid
https://bugs.documentfoundation.org/show_bug.cgi?id=159532 Bug ID: 159532 Summary: Deleting first or last row from a table referenced in a table function makes it invalid Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kelem...@ubuntu.com Blocks: 122755 Created attachment 192358 --> https://bugs.documentfoundation.org/attachment.cgi?id=192358=edit Example file from Writer When a table row that is referenced in a table function is deleted, the function is updated in an invalid way. 1. Open attached document 2. From the first table delete the first or second row -> the SUM formula in the third row becomes invalid, such as SUM 3. From the third table delete the second row -> the SUM formula in the fourth row is still valid, changes from SUM to SUM Deleting one more row would make this invalid as well. Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: dfcdef6d94993131b5f150d00d08cc81a987eebb CPU threads: 15; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: threaded already in LO 3.3. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=122755 [Bug 122755] [META] Formulae in Writer tables bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 122755] [META] Formulae in Writer tables bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=122755 Gabor Kelemen (allotropia) changed: What|Removed |Added Depends on||159532 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=159532 [Bug 159532] Deleting first or last row from a table referenced in a table function makes it invalid -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159531] Comments in Writer's margins should have some padding spacing to avoid text being flush to the edge
https://bugs.documentfoundation.org/show_bug.cgi?id=159531 --- Comment #1 from Jeff Fortin Tam --- Created attachment 192357 --> https://bugs.documentfoundation.org/attachment.cgi?id=192357=edit Screenshot and mockup (current vs proposed UX) 6 pixels to the edge (as shown in this mockup) would not be intrusive, yet would make for a noticeable improvement in UX. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159531] Comments in Writer's margins should have some padding spacing to avoid text being flush to the edge
https://bugs.documentfoundation.org/show_bug.cgi?id=159531 Jeff Fortin Tam changed: What|Removed |Added Blocks||106179 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=106179 [Bug 106179] [META] Writer comment bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 106179] [META] Writer comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=106179 Jeff Fortin Tam changed: What|Removed |Added Depends on||159531 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=159531 [Bug 159531] Comments in Writer's margins should have some padding spacing to avoid text being flush to the edge -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159531] New: Comments in Writer's margins should have some padding spacing to avoid text being flush to the edge
https://bugs.documentfoundation.org/show_bug.cgi?id=159531 Bug ID: 159531 Summary: Comments in Writer's margins should have some padding spacing to avoid text being flush to the edge Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: nekoh...@gmail.com Description: Please see the attached screenshot+mockup combo. Steps to Reproduce: 1. Insert a comment in Writer Actual Results: Text is flush against the left edge (presumably against the right edge in RTL languages) Expected Results: There should be a small amount of spacing to let it breathe and let the eye distinguish the text from the edge, otherwise you can't benefit from the background color (especially in dark mode). Reproducible: Always User Profile Reset: Yes Additional Info: Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 CPU threads: 8; OS: Linux 6.6; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Flatpak Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 105112] Support aggregate functions EVERY, ANY, SOME, COLLECT, FUSION, INTERSECTION
https://bugs.documentfoundation.org/show_bug.cgi?id=105112 Robert Großkopf changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||9319 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159319] Functions in Query-GUI: Delete functions, which won't work with internal databases
https://bugs.documentfoundation.org/show_bug.cgi?id=159319 Robert Großkopf changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||5112 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159319] Functions in Query-GUI: Delete functions, which won't work with internal databases
https://bugs.documentfoundation.org/show_bug.cgi?id=159319 Robert Großkopf changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||5140 --- Comment #5 from Robert Großkopf --- (In reply to Alex Thurgood from comment #4) > Hi Robert, > > Isn't this a DUP of either bug 105112 or bug 105140 ? The bugs I reported there are about support for this functions. But support of such function couldn't work, because the HSQLDB and Firebird won't support it - also no other database I'm using here and could test. I would prefer: Solve this bug and I will set the other 2 bugs as Worksforma. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 105140] HSQLDB: Aggregate functions don't work - COLLECT, FUSION, INTERSECTION
https://bugs.documentfoundation.org/show_bug.cgi?id=105140 Robert Großkopf changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||9319 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 105605] [META] Digital signatures bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=105605 Bug 105605 depends on bug 156344, which changed state. Bug 156344 Summary: macOS: Settings > Security > Certificate Manager should preselect Applications folder when clicking Browse… button https://bugs.documentfoundation.org/show_bug.cgi?id=156344 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Bug 156344] macOS: Settings > Security > Certificate Manager should preselect Applications folder when clicking Browse… button
https://bugs.documentfoundation.org/show_bug.cgi?id=156344 Patrick Luby changed: What|Removed |Added Resolution|--- |DUPLICATE CC||guibomac...@gmail.com Status|NEW |RESOLVED --- Comment #12 from Patrick Luby --- (In reply to Alex Thurgood from comment #11) > Testing with my eiDAS compliant signature provided through > > /Applications/Trusted Key Manager.app/Contents/MacOS/Trusted Key Manager > > shows that it doesn't yet recognize or start the binary for managing the > certificates provided through that tool. After the fix for tdf#159307, I can set the Certificate Manager in the Options dialog to each of the following and all launch successfully when the Start Certificate Managere button is presssed in the Digital Signatures dialog: /Applications/GPG Keychain.app /Applications/GPG Keychain.app/ /Applications/GPG Keychain.app/Contents/MacOS/GPG Keychain So I think we can close this as a duplicate of tdf#159307? Feel free to reopen if there are still problems. *** This bug has been marked as a duplicate of bug 159307 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159530] In dark mode, Calc's page breaks' light-gray watermarks and dark-blue borders don't fit the theme
https://bugs.documentfoundation.org/show_bug.cgi?id=159530 --- Comment #3 from Jeff Fortin Tam --- Created attachment 192354 --> https://bugs.documentfoundation.org/attachment.cgi?id=192354=edit Screenshot in dark mode -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159530] In dark mode, Calc's page breaks' light-gray watermarks and dark-blue borders don't fit the theme
https://bugs.documentfoundation.org/show_bug.cgi?id=159530 --- Comment #2 from Jeff Fortin Tam --- Created attachment 192353 --> https://bugs.documentfoundation.org/attachment.cgi?id=192353=edit Screenshot in light mode -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159513] Image settings are not saved
https://bugs.documentfoundation.org/show_bug.cgi?id=159513 ady changed: What|Removed |Added OS|macOS (All) |All Hardware|ARM |All CC||luigigorgo...@gmail.com --- Comment #3 from ady --- CC'ing "Luigi Gorgone" from tdf#159183 comment 6, who apparently has the same problem, but with older version and under Linux. I am changing fields accordingly. In the middle of the versions mentioned, there was some crash (tdf#159183) that was somehow resolved before 24.2.0.3, so I'm not changing the Version field for now. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159530] In dark mode, Calc's page breaks' light-gray watermarks and dark-blue borders don't fit the theme
https://bugs.documentfoundation.org/show_bug.cgi?id=159530 --- Comment #1 from Jeff Fortin Tam --- Created attachment 192352 --> https://bugs.documentfoundation.org/attachment.cgi?id=192352=edit Sample for testing -- You are receiving this mail because: You are the assignee for the bug.
[Bug 147291] macOS: Digital Signatures > Start Certificate Manager (OpenPGP) results in error instead of opening GPG Keychain
https://bugs.documentfoundation.org/show_bug.cgi?id=147291 --- Comment #20 from Patrick Luby --- (In reply to Alex Thurgood from comment #19) > After adding the scManager.app, I see the following path in the Certificate > Manager path field: > > /Applications/SCinterface/scManager.app/ > > With an open test document in Writer, calling the digital signature dialog > and clicking on the Certificate Manager button successfully opens the > scManager app. > > > Similarly, after adding the 'Trusted Key Manager.app', I see the following > path: > > /Applications/Trusted Key Manager.app/ > > and the app duly opens when clicking on the Certificate Manager button. So which application is used by more people? My guess is that GPGTools is the most common and macOS' Keychain Access application is the least common so these two would go in the middle. I just don't have any sense which is more common. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159530] In dark mode, Calc's page breaks' light-gray watermarks and dark-blue borders don't fit the theme
https://bugs.documentfoundation.org/show_bug.cgi?id=159530 Jeff Fortin Tam changed: What|Removed |Added Blocks||153293 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153293 [Bug 153293] [META] Dark Mode bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 153293] [META] Dark Mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=153293 Jeff Fortin Tam changed: What|Removed |Added Depends on||159530 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=159530 [Bug 159530] In dark mode, Calc's page breaks' light-gray watermarks and dark-blue borders don't fit the theme -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159530] New: In dark mode, Calc's page breaks' light-gray watermarks and dark-blue borders don't fit the theme
https://bugs.documentfoundation.org/show_bug.cgi?id=159530 Bug ID: 159530 Summary: In dark mode, Calc's page breaks' light-gray watermarks and dark-blue borders don't fit the theme Product: LibreOffice Version: 24.2.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: nekoh...@gmail.com Description: See attached files and info below. Steps to Reproduce: 1. In the options, set "LibreOffice > Applications Colors > Automatic" to "System theme" 2. Open the attached spreadsheet in Calc (which is set to "Page break" view mode, and has textual data in the cells to simulate real-world situations) 3. Switch your operating system to dark mode Actual Results: - "Page 1" and "Page 2" watermark texts remain light-gray, which is too bright (too noticeable) and also interferes with the cells' foreground text color - The dark blue page break delimiter lines are too dark to work well on a dark background Expected Results: - Page break watermarks should use a darker shade of gray while in dark mode - Page break delimiters should probably use a light blue while in dark mode Reproducible: Always User Profile Reset: Yes Additional Info: Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 CPU threads: 8; OS: Linux 6.6; UI render: default; VCL: gtk3 Locale: en-CA (en_CA.UTF-8); UI: en-US Flatpak Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159340] black background in working area in dialog Base after displaying a calendar
https://bugs.documentfoundation.org/show_bug.cgi?id=159340 --- Comment #6 from Alex Thurgood --- This sounds very much like a Skia bug. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159319] Functions in Query-GUI: Delete functions, which won't work with internal databases
https://bugs.documentfoundation.org/show_bug.cgi?id=159319 --- Comment #4 from Alex Thurgood --- Hi Robert, Isn't this a DUP of either bug 105112 or bug 105140 ? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159529] New: Excessive memory consumption in v24.2
https://bugs.documentfoundation.org/show_bug.cgi?id=159529 Bug ID: 159529 Summary: Excessive memory consumption in v24.2 Product: LibreOffice Version: 24.2.0.3 release Hardware: x86-64 (AMD64) OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ka...@goodtimes.fi Up until v7.6, I haven’t had noticeable issues with memory use. The typical memory consumption with my usage habits has been on the order of a few hundred MBs. Even at the extreme, it can’t have been much more than 1 GB, or I would have started paying attention. With v24.2, after a few hours of light use, I noticed LO occupying 4.5 GB of memory, so I investigated a bit. 1. Simply launching LO and creating an empty Writer document brings memory usage up to 570 MB. 2. Interacting with modal dialogs (e.g., Edit Paragraph Style) continually increases memory consumption as I cycle through the tabs in the dialog. The memory is never released, even when I close the dialog. Very quickly I get at 1 GB. 3. Opening the font selector dropdown in the toolbar and scrolling down through the entire list causes memory usage to balloon from 1 GB to 2.25 GB. I performed the same steps with Skia disabled. Steps 1 & 3 had the same outcome as before, but in step 2 the memory leak was no longer there. I downgraded back to v7.6.4 and could no longer reproduce any of the three. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159509] Libre Math --> dark fonts in editor in dark background (dark theme)
https://bugs.documentfoundation.org/show_bug.cgi?id=159509 Rafael Lima changed: What|Removed |Added CC||rafael.palma.l...@gmail.com --- Comment #5 from Rafael Lima --- I tried with LO 7.6 and 24.2 both on Ubuntu (gtk3) and Kubuntu (kf5) and I could not reproduce the problem. Do you have any theme installed on your machine? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159513] Image settings are not saved
https://bugs.documentfoundation.org/show_bug.cgi?id=159513 Michael Weghorn changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #2 from Michael Weghorn --- (In reply to ady from comment #1) > Based on tdf#159183 comment7, I am CC'ing Michael Weghorn. Maybe this just > needs bibisecting and/or backporting some fix. I don't have any special insights for the issue here, but it's the same on master, so not just a matter of backporting. (That's the case for tdf#159183, which is a different issue.) (In reply to himatech from comment #0) > Actual Results: > No effect > > Expected Results: > The image should be anchored to the top-right side of the cell, I guess. Repeating steps 3-4, the previously set base points for position and size are top-left again, also confirming that the previous selection was not applied. Previously made setting should be applied and remain. (Or if there's a particular reason why that particular choice should not supported, it should not be possible to select that in the first place.) Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: df0c602aa6579604bc734bbfb5956261eb026b23 CPU threads: 12; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
core.git: Branch 'distro/collabora/co-23.05' - editeng/qa editeng/source
editeng/qa/unit/core-test.cxx | 35 +--
editeng/source/editeng/impedit2.cxx |9 +
2 files changed, 34 insertions(+), 10 deletions(-)
New commits:
commit ad6ed50bb669996fc85b6ec25e3babf93351bcf8
Author: Miklos Vajna
AuthorDate: Fri Feb 2 08:08:54 2024 +0100
Commit: Caolán McNamara
CommitDate: Fri Feb 2 18:20:57 2024 +0100
tdf#159507 editeng: support pasting HTML fragments
Commit ce53519f025158f8f64a4e8603c8c6e0dc35473a (cool#8023 editeng:
support HTML paste, 2024-01-24) added support for pasting HTML files
into Calc cells while editing, but this doesn't work when only a HTML
fragment is provided, without headers and footers.
The HTML code in ImpEditEngine::PasteText() was modeled after the
HTML_SIMPLE case, which is some custom format from MSIE and that
rejected the data in case the header didn't match, so the HTML case also
required a HTML header in the above commit, but this doesn't work for
HTML fragments.
Fix the problem by just dropping the header check in
ImpEditEngine::PasteText(), because that data already comes from the
text/html slot of the clipboard, so there is already indication about
the file format, even without the header. And without headers, it's
almost impossible to recognize if the HTML fragment is a HTML one or
not.
Note that this is the HTML paste when a cell edit is active, the normal
Calc HTML paste is a different codepath, in sc/.
(cherry picked from commit 0503f6718f7686f3e2c93fc13af23e9fbfdace42)
Conflicts:
editeng/source/editeng/impedit2.cxx
Change-Id: I4d37d80f947880fe22051c5fe84dc6bbc257e108
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/162928
Tested-by: Jenkins CollaboraOffice
Reviewed-by: Caolán McNamara
diff --git a/editeng/qa/unit/core-test.cxx b/editeng/qa/unit/core-test.cxx
index 79a0673770d1..6a00c5b13078 100644
--- a/editeng/qa/unit/core-test.cxx
+++ b/editeng/qa/unit/core-test.cxx
@@ -72,6 +72,9 @@ public:
/// Test Paste using HTML
void testHTMLPaste();
+/// Test Paste using an HTML fragment
+void testHTMLFragmentPaste();
+
/// Test Copy/Paste with selective selection over multiple paragraphs
void testMultiParaSelCopyPaste();
@@ -119,6 +122,7 @@ public:
CPPUNIT_TEST(testHyperlinkCopyPaste);
CPPUNIT_TEST(testCopyPaste);
CPPUNIT_TEST(testHTMLPaste);
+CPPUNIT_TEST(testHTMLFragmentPaste);
CPPUNIT_TEST(testMultiParaSelCopyPaste);
CPPUNIT_TEST(testTabsCopyPaste);
CPPUNIT_TEST(testHyperlinkSearch);
@@ -722,12 +726,19 @@ void Test::testCopyPaste()
/// XTransferable implementation that provides simple HTML content.
class TestHTMLTransferable : public
cppu::WeakImplHelper
{
+OString m_aHTML;
public:
+TestHTMLTransferable(const OString& rHTML);
uno::Any SAL_CALL getTransferData(const datatransfer::DataFlavor& rFlavor)
override;
uno::Sequence SAL_CALL getTransferDataFlavors()
override;
sal_Bool SAL_CALL isDataFlavorSupported(const datatransfer::DataFlavor&
rFlavor) override;
};
+TestHTMLTransferable::TestHTMLTransferable(const OString& rHTML)
+: m_aHTML(rHTML)
+{
+}
+
uno::Any TestHTMLTransferable::getTransferData(const datatransfer::DataFlavor&
rFlavor)
{
if (rFlavor.MimeType != "text/html")
@@ -737,7 +748,7 @@ uno::Any TestHTMLTransferable::getTransferData(const
datatransfer::DataFlavor& r
uno::Any aRet;
SvMemoryStream aStream;
-aStream.WriteOString("
test");
+aStream.WriteOString(m_aHTML);
aRet <<= uno::Sequence(static_cast(aStream.GetData()), aStream.GetSize());
return aRet;
}
@@ -762,7 +773,8 @@ void Test::testHTMLPaste()
// Given an empty editeng document:
EditEngine aEditEngine(mpItemPool.get());
EditDoc = aEditEngine.GetEditDoc();
-uno::Reference< datatransfer::XTransferable > xData(new
TestHTMLTransferable);
+OString aHTML("
test");
+uno::Reference< datatransfer::XTransferable > xData(new
TestHTMLTransferable(aHTML));
// When trying to paste HTML:
aEditEngine.InsertText(xData, OUString(), rDoc.GetEndPaM(), true);
@@ -775,6 +787,25 @@ void Test::testHTMLPaste()
CPPUNIT_ASSERT_EQUAL(OUString("test"),
rDoc.GetParaAsString(static_cast(0)));
}
+void Test::testHTMLFragmentPaste()
+{
+// Given an empty editeng document:
+EditEngine aEditEngine(mpItemPool.get());
+EditDoc = aEditEngine.GetEditDoc();
+OString aHTML("abc");
+uno::Reference< datatransfer::XTransferable > xData(new
TestHTMLTransferable(aHTML));
+
+// When trying to paste an HTML fragment:
+aEditEngine.InsertText(xData, OUString(), rDoc.GetEndPaM(), true);
+
+// Then make sure the text gets pasted:
+// Without the accompanying fix in place, this test would have failed with:
+// - Expected: abc
+// - Actual :
+// i.e. a HTML fragment without a proper header was
core.git: Branch 'distro/collabora/co-23.05' - include/svtools sc/CppunitTest_sc_filter_html.mk sc/Module_sc.mk sc/qa sc/source svtools/source
include/svtools/htmlkywd.hxx |1 include/svtools/htmltokn.h |1 sc/CppunitTest_sc_filter_html.mk | 82 + sc/Module_sc.mk|1 sc/qa/filter/html/data/text.html |8 +++ sc/qa/filter/html/html.cxx | 62 +++ sc/source/filter/html/htmlpars.cxx | 22 + svtools/source/svhtml/htmlkywd.cxx |1 8 files changed, 178 insertions(+) New commits: commit c378582f965874dbe858fd1a64d6a7f90cf083a2 Author: Miklos Vajna AuthorDate: Thu Feb 1 13:10:26 2024 +0100 Commit: Caolán McNamara CommitDate: Fri Feb 2 18:19:08 2024 +0100 tdf#159483 sc HTML import: handle data-sheets-value attribute for the text case The A2 cell in the bugdoc has 01 in it, which was auto-converted to 1 (float) value on import, even if it was text originally. This is hard to solve for HTML in general, which is not typed, but this input is coming from google sheets, which has an additional data-sheets-value attribute on that does tell us about the type of the cell. Fix the problem by handling that attribute, and in case it explicitly says it's text, then apply the matching number format. Other types are not yet handled. (cherry picked from commit e6e5660b726ecf3b0c39b277568568973b43c9f0) Change-Id: I2986ef864e97d9c46d191aba25ca5740a1151a71 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/162886 Tested-by: Jenkins CollaboraOffice Reviewed-by: Caolán McNamara diff --git a/include/svtools/htmlkywd.hxx b/include/svtools/htmlkywd.hxx index cdcee168acba..1c0360404ced 100644 --- a/include/svtools/htmlkywd.hxx +++ b/include/svtools/htmlkywd.hxx @@ -445,6 +445,7 @@ #define OOO_STRING_SVTOOLS_HTML_O_title "title" #define OOO_STRING_SVTOOLS_HTML_O_value "value" #define OOO_STRING_SVTOOLS_HTML_O_SDval "sdval" +#define OOO_STRING_SVTOOLS_HTML_O_DSval "data-sheets-value" #define OOO_STRING_SVTOOLS_HTML_O_SDnum "sdnum" #define OOO_STRING_SVTOOLS_HTML_O_sdlibrary "sdlibrary" #define OOO_STRING_SVTOOLS_HTML_O_sdmodule "sdmodule" diff --git a/include/svtools/htmltokn.h b/include/svtools/htmltokn.h index 9dca8a8f3ea7..b18acd6dcb87 100644 --- a/include/svtools/htmltokn.h +++ b/include/svtools/htmltokn.h @@ -344,6 +344,7 @@ STRING_START= BOOL_END, TITLE, VALUE, SDVAL, // StarDiv NumberValue +DSVAL, SDNUM, // StarDiv NumberFormat SDLIBRARY, SDMODULE, diff --git a/sc/CppunitTest_sc_filter_html.mk b/sc/CppunitTest_sc_filter_html.mk new file mode 100644 index ..b78349d64703 --- /dev/null +++ b/sc/CppunitTest_sc_filter_html.mk @@ -0,0 +1,82 @@ +# -*- Mode: makefile-gmake; tab-width: 4; indent-tabs-mode: t -*- +# +# This file is part of the LibreOffice project. +# +# This Source Code Form is subject to the terms of the Mozilla Public +# License, v. 2.0. If a copy of the MPL was not distributed with this +# file, You can obtain one at http://mozilla.org/MPL/2.0/. +# + +$(eval $(call gb_CppunitTest_CppunitTest,sc_filter_html)) + +$(eval $(call gb_CppunitTest_use_common_precompiled_header,sc_filter_html)) + +$(eval $(call gb_CppunitTest_add_exception_objects,sc_filter_html, \ +sc/qa/filter/html/html \ +)) + +$(eval $(call gb_CppunitTest_use_externals,sc_filter_html, \ + boost_headers \ + libxml2 \ +)) + +$(eval $(call gb_CppunitTest_use_libraries,sc_filter_html, \ +basegfx \ +comphelper \ +cppu \ +cppuhelper \ +drawinglayer \ +drawinglayercore \ +editeng \ +for \ +forui \ +i18nlangtag \ +msfilter \ +oox \ +sal \ +salhelper \ +sax \ +sc \ +scqahelper \ +sfx \ +sot \ +subsequenttest \ +svl \ +svt \ +svx \ +svxcore \ + test \ +tk \ +tl \ +ucbhelper \ + unotest \ +utl \ +vcl \ +xo \ +)) + +$(eval $(call gb_CppunitTest_set_include,sc_filter_html,\ +-I$(SRCDIR)/sc/source/ui/inc \ +-I$(SRCDIR)/sc/inc \ +$$(INCLUDE) \ +)) + +$(eval $(call gb_CppunitTest_use_api,sc_filter_html,\ + udkapi \ + offapi \ + oovbaapi \ +)) + +$(eval $(call gb_CppunitTest_use_packages,sc_filter_html, \ +filter_xhtml \ +filter_xslt \ +)) + +$(eval $(call gb_CppunitTest_use_ure,sc_filter_html)) +$(eval $(call gb_CppunitTest_use_vcl,sc_filter_html)) + +$(eval $(call gb_CppunitTest_use_rdb,sc_filter_html,services)) + +$(eval $(call gb_CppunitTest_use_configuration,sc_filter_html)) + +# vim: set noet sw=4 ts=4: diff --git a/sc/Module_sc.mk b/sc/Module_sc.mk index d8017dd6f48a..cce6ad096980 100644 --- a/sc/Module_sc.mk +++ b/sc/Module_sc.mk @@ -90,6 +90,7 @@ $(eval $(call gb_Module_add_slowcheck_targets,sc, \ CppunitTest_sc_uicalc \ CppunitTest_sc_vba_macro_test \ CppunitTest_sc_a11y \ + CppunitTest_sc_filter_html \ )) ifneq ($(ENABLE_JUMBO_SHEETS),) diff --git a/sc/qa/filter/html/data/text.html
[Bug 158977] FILEOPEN: DOCX: footer has text when it shouldn't
https://bugs.documentfoundation.org/show_bug.cgi?id=158977 Xisco Faulí changed: What|Removed |Added CC||vmik...@collabora.com --- Comment #3 from Xisco Faulí --- (In reply to Xisco Faulí from comment #1) > Regression introduced by: > > authorTomaž Vajngerl 2023-11-28 > 13:46:21 > +0900 > committer Tomaž Vajngerl2023-12-01 08:26:38 > +0100 > commit 4b0fa253a4540f5461397815d290586f9ddabe61 (patch) > tree c58c59871244dc75e538caeea40658303da00b8b > parent 93357349ff1998b41ea1ebedf09dc1cc5da316f7 (diff) > tdf#136472 adjust ooxml import to handle first header/footer > > Bisected with: bibisect-linux64-24.2 Hi Tomaz, Miklos, Looking at the above commit, I see at least 10 tests that were commented out with the comment TODO to make Jenkins happy and be able to submit the patch, which looks like a quite bad practice to me. Is there any plan from your side to fix those existing tests that were commented out ? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 145539] Convert string literals defined as const char[] in header files to constexpr OUStringLiteral
https://bugs.documentfoundation.org/show_bug.cgi?id=145539 --- Comment #12 from Buovjaga --- (In reply to Devansh Varshney from comment #10) > One more thing does the below file also needs the same changes? > > https://github.com/LibreOffice/core/blob/ > c3d00f4ca0ec5a53d694ab9924fd79d0e536aec4/sc/source/core/opencl/ > op_math_helpers.hxx#L4 > > This is what I did to the first const char[] - > > inline constexpr OUStringLiteral Math_IntgDecl =u"double Intg(double n);\n"; > > I am asking for this as in the comment 9 it's written that- can be safely > ignored. Comment 9 says to ignore it, so don't change it. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159528] officehelper.py doesn't function in the context of macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=159528 Alain Romedenne changed: What|Removed |Added Summary|officehelper doesn't|officehelper.py doesn't |function in the context of |function in the context of |macOS |macOS -- You are receiving this mail because: You are the assignee for the bug.
[Bug 47596] FILEOPEN: rotated and cropped or scaled PNG/JPG/WMF image in MSO .DOC not rotated and wrongly scaled
https://bugs.documentfoundation.org/show_bug.cgi?id=47596 --- Comment #35 from Xavier R --- Same as your pic (attachment 58770), with - LibreOffice Version: 7.5.9.2 (X86_64) / LibreOffice Community - Microsoft Office 2019. both on Windows 11. As there are a lot of other image management problems with LO, it could be interesting to see if we could reproduce the same thing in Impress/Powerpoint. I'll try next week. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159528] New: officehelper doesn't function in the context of macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=159528 Bug ID: 159528 Summary: officehelper doesn't function in the context of macOS Product: LibreOffice Version: 24.2.0.3 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: alain.romede...@libreoffice.org Description: officehelper.bootstrap() method seeks for UNO_PATH environment variable which is not defined. This leads to invoke 'soffice' command in place of fully qualified 'Applications/LibreOffice.app/Contents/MacOS/soffice' command Steps to Reproduce: Run embedded Python interpreter or: 1. Install APSO extension 2. Run Python interpreter using APSO In above Python REPL console: 3. type 'import officehelper as oh' 4. type 'oh.bootstrap()' 5. wait a few seconds Actual Results: bootstrap() method raises a NoConnectException: - as this method does not detect the faulty command it spawns - as this method fails to connect to a missing process Expected Results: bootstrap() connects successfully to '.../soffice' process Reproducible: Always User Profile Reset: No Additional Info: In order to construct a fully qualified 'soffice' command bootstrap() method seeks for UNO_PATH environment variable that's missing in the context of macOS. - LO macOS build process may include an alias for 'soffice' that is mapped to its fully qualified name 'Applications/LibreOffice.app/Contents/MacOS/soffice' -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103369] [META] Bullet, numbered, and outline list bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103369 Bug 103369 depends on bug 100454, which changed state. Bug 100454 Summary: UI: some bullet lists don't have their bullets displayed in print preview https://bugs.documentfoundation.org/show_bug.cgi?id=100454 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Bug 85644] Some bullet lists don't have their bullets displayed in Read-Only mode
https://bugs.documentfoundation.org/show_bug.cgi?id=85644 Buovjaga changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=10 | |0454| CC||pietro.pangallo@studiostort ||i.com --- Comment #12 from Buovjaga --- *** Bug 100454 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 100454] UI: some bullet lists don't have their bullets displayed in print preview
https://bugs.documentfoundation.org/show_bug.cgi?id=100454 Buovjaga changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=85 | |644 | Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #11 from Buovjaga --- *** This bug has been marked as a duplicate of bug 85644 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108882] [META] Read-only bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108882 Bug 108882 depends on bug 85644, which changed state. Bug 85644 Summary: Some bullet lists don't have their bullets displayed in Read-Only mode https://bugs.documentfoundation.org/show_bug.cgi?id=85644 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103369] [META] Bullet, numbered, and outline list bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103369 Bug 103369 depends on bug 85644, which changed state. Bug 85644 Summary: Some bullet lists don't have their bullets displayed in Read-Only mode https://bugs.documentfoundation.org/show_bug.cgi?id=85644 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Bug 85644] Some bullet lists don't have their bullets displayed in Read-Only mode
https://bugs.documentfoundation.org/show_bug.cgi?id=85644 Buovjaga changed: What|Removed |Added Resolution|--- |NOTABUG Status|NEW |RESOLVED --- Comment #11 from Buovjaga --- Good catch - closing. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 47596] FILEOPEN: rotated and cropped or scaled PNG/JPG/WMF image in MSO .DOC not rotated and wrongly scaled
https://bugs.documentfoundation.org/show_bug.cgi?id=47596 --- Comment #34 from grofaty --- Retested after 12-years of reporting an issue. Still an issue in LibreOffice Writer 24.2, but it works fine in Microsoft Office Word 365. Attachment in previous post: - left site LibreOffice (incorrectly displayed image) - Microsoft Office (correctly displayed image) -- You are receiving this mail because: You are the assignee for the bug.
