[Libreoffice-bugs] [Bug 146019] Always insert rotated image if it has EXIF rotation
https://bugs.documentfoundation.org/show_bug.cgi?id=146019 Heiko Tietze changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||ke...@collabora.com, ||qui...@gmail.com, ||samuel.mehrbrodt@allotropia ||.de Keywords||skillCpp, topicCleanup -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90132] Refresh problem of linked cells
https://bugs.documentfoundation.org/show_bug.cgi?id=90132 SI Albertville changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #7 from SI Albertville --- Version: 7.1.7.2 (x64) / LibreOffice Community Build ID: c6a4e3954236145e2acb0b65f68614365aeee33f CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: threaded Thank you -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145958] LibreOffice start menu opens, but won't open any document, new or existing
https://bugs.documentfoundation.org/show_bug.cgi?id=145958 --- Comment #1 from onlyshi...@gmail.com --- Thank you for reporting the bug. I can not reproduce the bug in Version: 7.4.0.0.alpha0+ (x86) / LibreOffice Community Build ID: 4ac9032163cf55c160145373e7c41741c9c339ca CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106179] [META] Writer comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=106179 Bug 106179 depends on bug 98442, which changed state. Bug 98442 Summary: Redo of editing incomplete in comment editing https://bugs.documentfoundation.org/show_bug.cgi?id=98442 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98442] Redo of editing incomplete in comment editing
https://bugs.documentfoundation.org/show_bug.cgi?id=98442 Luke Kendall changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #10 from Luke Kendall --- Thanks, bug is now fixed. Version: 7.2.3.2 / LibreOffice Community Build ID: d166454616c1632304285822f9c83ce2e660fd92 CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96416] Symbol for UTF-8 FFF9 character (Interlinear Annotation Anchor) not visible on Linux
https://bugs.documentfoundation.org/show_bug.cgi?id=96416 Luke Kendall changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #7 from Luke Kendall --- They're visible in the Linux version of LO now, thanks. Version: 7.2.3.2 / LibreOffice Community Build ID: d166454616c1632304285822f9c83ce2e660fd92 CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: include/svx svx/source
include/svx/sdr/contact/viewobjectcontact.hxx |2
svx/source/sdr/contact/viewobjectcontact.cxx |7 ---
svx/source/sdr/contact/viewobjectcontactofgroup.cxx | 23 --
svx/source/sdr/contact/viewobjectcontactofsdrpage.cxx | 38 +-
4 files changed, 8 insertions(+), 62 deletions(-)
New commits:
commit 085f15acfdb96155011d60b6127ea6f6e4a9a263
Author: Noel Grandin
AuthorDate: Thu Dec 2 11:28:27 2021 +0200
Commit: Noel Grandin
CommitDate: Fri Dec 3 08:40:23 2021 +0100
no need to create Primitive2DContainer here
we can just use the visitor API and skip a whole bunch of object
creation
Change-Id: If3dfa2fc1811e708963b8e6ecf4af6508b9f2a23
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/126216
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/include/svx/sdr/contact/viewobjectcontact.hxx
b/include/svx/sdr/contact/viewobjectcontact.hxx
index dd949cf075c7..453cfb2d90ea 100644
--- a/include/svx/sdr/contact/viewobjectcontact.hxx
+++ b/include/svx/sdr/contact/viewobjectcontact.hxx
@@ -124,7 +124,7 @@ public:
virtual void getPrimitive2DSequenceHierarchy(DisplayInfo& rDisplayInfo,
drawinglayer::primitive2d::Primitive2DDecompositionVisitor& rVisitor) const;
// just process the sub-hierarchy, used as tooling from
getPrimitive2DSequenceHierarchy
-drawinglayer::primitive2d::Primitive2DContainer
getPrimitive2DSequenceSubHierarchy(DisplayInfo& rDisplayInfo) const;
+void getPrimitive2DSequenceSubHierarchy(DisplayInfo& rDisplayInfo,
drawinglayer::primitive2d::Primitive2DDecompositionVisitor& rVisitor) const;
// interface to support GridOffset for non-linear ViewToDevice
transformation (calc)
const basegfx::B2DVector& getGridOffset() const;
diff --git a/svx/source/sdr/contact/viewobjectcontact.cxx
b/svx/source/sdr/contact/viewobjectcontact.cxx
index 22eb52a99af4..5da24f86a54d 100644
--- a/svx/source/sdr/contact/viewobjectcontact.cxx
+++ b/svx/source/sdr/contact/viewobjectcontact.cxx
@@ -425,19 +425,16 @@ void
ViewObjectContact::getPrimitive2DSequenceHierarchy(DisplayInfo& rDisplayInf
rVisitor.append(xRetval);
}
-drawinglayer::primitive2d::Primitive2DContainer
ViewObjectContact::getPrimitive2DSequenceSubHierarchy(DisplayInfo&
rDisplayInfo) const
+void ViewObjectContact::getPrimitive2DSequenceSubHierarchy(DisplayInfo&
rDisplayInfo, drawinglayer::primitive2d::Primitive2DDecompositionVisitor&
rVisitor) const
{
const sal_uInt32 nSubHierarchyCount(GetViewContact().GetObjectCount());
-drawinglayer::primitive2d::Primitive2DContainer xSeqRetval;
for(sal_uInt32 a(0); a < nSubHierarchyCount; a++)
{
const ViewObjectContact&
rCandidate(GetViewContact().GetViewContact(a).GetViewObjectContact(GetObjectContact()));
-rCandidate.getPrimitive2DSequenceHierarchy(rDisplayInfo, xSeqRetval);
+rCandidate.getPrimitive2DSequenceHierarchy(rDisplayInfo, rVisitor);
}
-
-return xSeqRetval;
}
// Support getting a GridOffset per object and view for non-linear ViewToDevice
diff --git a/svx/source/sdr/contact/viewobjectcontactofgroup.cxx
b/svx/source/sdr/contact/viewobjectcontactofgroup.cxx
index a8465df9d587..8469a00c1e45 100644
--- a/svx/source/sdr/contact/viewobjectcontactofgroup.cxx
+++ b/svx/source/sdr/contact/viewobjectcontactofgroup.cxx
@@ -41,8 +41,6 @@ namespace sdr::contact
void
ViewObjectContactOfGroup::getPrimitive2DSequenceHierarchy(DisplayInfo&
rDisplayInfo, drawinglayer::primitive2d::Primitive2DDecompositionVisitor&
rVisitor) const
{
-drawinglayer::primitive2d::Primitive2DContainer xRetval;
-
// check model-view visibility
if(!isPrimitiveVisible(rDisplayInfo))
return;
@@ -60,30 +58,13 @@ namespace sdr::contact
rDisplayInfo.ClearGhostedDrawMode();
}
-// create object hierarchy
-xRetval = getPrimitive2DSequenceSubHierarchy(rDisplayInfo);
-
-if(!xRetval.empty())
-{
-// get ranges
-const drawinglayer::geometry::ViewInformation2D&
rViewInformation2D(GetObjectContact().getViewInformation2D());
-const ::basegfx::B2DRange
aObjectRange(xRetval.getB2DRange(rViewInformation2D));
-const basegfx::B2DRange&
aViewRange(rViewInformation2D.getViewport());
-
-// check geometrical visibility
-if(!aViewRange.isEmpty() &&
!aViewRange.overlaps(aObjectRange))
-{
-// not visible, release
-xRetval.clear();
-}
-}
+// visit object hierarchy
+getPrimitive2DSequenceSubHierarchy(rDisplayInfo, rVisitor);
if(bDoGhostedDisplaying)
{
[Libreoffice-commits] core.git: framework/inc framework/source
framework/inc/stdtypes.h |9 -
framework/source/services/autorecovery.cxx |9 +
framework/source/services/frame.cxx| 23 +--
3 files changed, 14 insertions(+), 27 deletions(-)
New commits:
commit 95266ea93458644c89f1ac7bf924c5323ed64544
Author: Noel Grandin
AuthorDate: Wed Dec 1 20:28:29 2021 +0200
Commit: Noel Grandin
CommitDate: Fri Dec 3 08:40:02 2021 +0100
use OMultiTypeInterfaceContainerHelperVar3 in framework
Change-Id: Ia2f59322511ed85492708262f90de26b33275105
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/126197
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/framework/inc/stdtypes.h b/framework/inc/stdtypes.h
index feec3ef92ceb..0ccc056cf605 100644
--- a/framework/inc/stdtypes.h
+++ b/framework/inc/stdtypes.h
@@ -21,7 +21,6 @@
#include
-#include
#include
namespace framework{
@@ -55,14 +54,6 @@ struct KeyEventEqualsFunc
}
};
-/**
-It can be used to map names (e.g. of properties) to her corresponding
handles.
-Our helper class OPropertySetHelper works optimized with handles but
sometimes we have only a property name.
-Mapping between these two parts of a property should be done in the
fastest way :-)
-*/
-
-typedef comphelper::OMultiTypeInterfaceContainerHelperVar2
ListenerHash;
-
} // namespace framework
/* vim:set shiftwidth=4 softtabstop=4 expandtab: */
diff --git a/framework/source/services/autorecovery.cxx
b/framework/source/services/autorecovery.cxx
index ebcae2a0862b..724d09204f68 100644
--- a/framework/source/services/autorecovery.cxx
+++ b/framework/source/services/autorecovery.cxx
@@ -75,6 +75,7 @@
#include
#include
#include
+#include
#include
#include
#include
@@ -419,7 +420,7 @@ private:
/** @short contains all status listener registered at this instance.
*/
-ListenerHash m_lListener;
+
comphelper::OMultiTypeInterfaceContainerHelperVar3 m_lListener;
/** @descr This member is used to prevent us against re-entrance problems.
A mutex can't help to prevent us from concurrent using of
members
@@ -3477,7 +3478,7 @@ void AutoRecovery::implts_informListener( Job
eJob ,
const css::frame::FeatureStateEvent&
aEvent)
{
// Helper shares mutex with us -> threadsafe!
-::comphelper::OInterfaceContainerHelper2* pListenerForURL = nullptr;
+::comphelper::OInterfaceContainerHelper3*
pListenerForURL = nullptr;
OUString sJob=
AutoRecovery::implst_getJobDescription(eJob);
// inform listener, which are registered for any URLs(!)
@@ -3485,12 +3486,12 @@ void AutoRecovery::implts_informListener( Job
eJob ,
if(pListenerForURL == nullptr)
return;
-::comphelper::OInterfaceIteratorHelper2 pIt(*pListenerForURL);
+::comphelper::OInterfaceIteratorHelper3 pIt(*pListenerForURL);
while(pIt.hasMoreElements())
{
try
{
-
static_cast(pIt.next())->statusChanged(aEvent);
+pIt.next()->statusChanged(aEvent);
}
catch(const css::uno::RuntimeException&)
{
diff --git a/framework/source/services/frame.cxx
b/framework/source/services/frame.cxx
index 991a7b58131b..fde9da72234a 100644
--- a/framework/source/services/frame.cxx
+++ b/framework/source/services/frame.cxx
@@ -68,6 +68,7 @@
#include
#include
+#include
#include
#include
#include
@@ -418,8 +419,8 @@ private:
typedef std::unordered_map TPropInfoHash;
TPropInfoHash m_lProps;
-ListenerHash m_lSimpleChangeListener;
-ListenerHash m_lVetoChangeListener;
+
comphelper::OMultiTypeInterfaceContainerHelperVar3 m_lSimpleChangeListener;
+
comphelper::OMultiTypeInterfaceContainerHelperVar3 m_lVetoChangeListener;
// hold it weak ... otherwise this helper has to be "killed" explicitly .-)
css::uno::WeakReference< css::uno::XInterface > m_xBroadcaster;
@@ -2860,19 +2861,16 @@ bool XFrameImpl::impl_existsVeto(const
css::beans::PropertyChangeEvent& aEvent)
The used helper is threadsafe and it lives for the whole lifetime of
our own object.
*/
-::comphelper::OInterfaceContainerHelper2* pVetoListener =
m_lVetoChangeListener.getContainer(aEvent.PropertyName);
+
::comphelper::OInterfaceContainerHelper3*
pVetoListener = m_lVetoChangeListener.getContainer(aEvent.PropertyName);
if (! pVetoListener)
return false;
-::comphelper::OInterfaceIteratorHelper2 pListener(*pVetoListener);
+::comphelper::OInterfaceIteratorHelper3 pListener(*pVetoListener);
while (pListener.hasMoreElements())
{
try
{
-css::uno::Reference< css::beans::XVetoableChangeListener >
xListener(
-
static_cast(pListener.next()),
-css::uno::UNO_QUERY_THROW);
-
[Libreoffice-commits] core.git: 2 commits - dbaccess/source
dbaccess/source/ui/browser/formadapter.cxx |4 ++--
dbaccess/source/ui/browser/sbamultiplex.cxx | 28 ++--
dbaccess/source/ui/inc/sbamultiplex.hxx | 21 +++--
3 files changed, 27 insertions(+), 26 deletions(-)
New commits:
commit cd888e4c04d209a8d436906369c13d6206c176f4
Author: Noel Grandin
AuthorDate: Wed Dec 1 19:07:50 2021 +0200
Commit: Noel Grandin
CommitDate: Fri Dec 3 08:39:51 2021 +0100
use OMultiTypeInterfaceContainerHelperVar3 in SbaXVetoableChangeMultiplexer
Change-Id: I60088bdf046659ca94a2aa9c09a3091e2dd03945
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/126196
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/dbaccess/source/ui/browser/sbamultiplex.cxx
b/dbaccess/source/ui/browser/sbamultiplex.cxx
index 76a625d47069..48e907221b39 100644
--- a/dbaccess/source/ui/browser/sbamultiplex.cxx
+++ b/dbaccess/source/ui/browser/sbamultiplex.cxx
@@ -464,7 +464,7 @@ void SAL_CALL
SbaXVetoableChangeMultiplexer::disposing(const css::lang::EventObj
}
void SAL_CALL SbaXVetoableChangeMultiplexer::vetoableChange(const
css::beans::PropertyChangeEvent& e)
{
-::comphelper::OInterfaceContainerHelper2* pListeners =
m_aListeners.getContainer(e.PropertyName);
+
::comphelper::OInterfaceContainerHelper3*
pListeners = m_aListeners.getContainer(e.PropertyName);
if (pListeners)
Notify(*pListeners, e);
@@ -475,13 +475,13 @@ void SAL_CALL
SbaXVetoableChangeMultiplexer::vetoableChange(const css::beans::Pr
}
void SbaXVetoableChangeMultiplexer::addInterface(const OUString& rName,
-const css::uno::Reference< css::uno::XInterface > & rListener)
+const css::uno::Reference< css::beans::XVetoableChangeListener > &
rListener)
{
m_aListeners.addInterface(rName, rListener);
}
void SbaXVetoableChangeMultiplexer::removeInterface(const OUString& rName,
-const css::uno::Reference< css::uno::XInterface > & rListener)
+const css::uno::Reference< css::beans::XVetoableChangeListener > &
rListener)
{
m_aListeners.removeInterface(rName, rListener);
}
@@ -498,7 +498,7 @@ sal_Int32 SbaXVetoableChangeMultiplexer::getOverallLen()
const
const std::vector< OUString > aContained =
m_aListeners.getContainedTypes();
for ( OUString const & s : aContained)
{
-::comphelper::OInterfaceContainerHelper2* pListeners =
m_aListeners.getContainer(s);
+::comphelper::OInterfaceContainerHelper3*
pListeners = m_aListeners.getContainer(s);
if (!pListeners)
continue;
nLen += pListeners->getLength();
@@ -506,13 +506,13 @@ sal_Int32 SbaXVetoableChangeMultiplexer::getOverallLen()
const
return nLen;
}
-void
SbaXVetoableChangeMultiplexer::Notify(::comphelper::OInterfaceContainerHelper2&
rListeners, const css::beans::PropertyChangeEvent& e)
+void
SbaXVetoableChangeMultiplexer::Notify(::comphelper::OInterfaceContainerHelper3&
rListeners, const css::beans::PropertyChangeEvent& e)
{
css::beans::PropertyChangeEvent aMulti(e);
aMulti.Source = _rParent;
-::comphelper::OInterfaceIteratorHelper2 aIt(rListeners);
+::comphelper::OInterfaceIteratorHelper3 aIt(rListeners);
while (aIt.hasMoreElements())
-static_cast<
css::beans::XVetoableChangeListener*>(aIt.next())->vetoableChange(aMulti);
+aIt.next()->vetoableChange(aMulti);
}
// css::beans::XPropertiesChangeListener
diff --git a/dbaccess/source/ui/inc/sbamultiplex.hxx
b/dbaccess/source/ui/inc/sbamultiplex.hxx
index a3af5d5e0af3..88d1ad3bf1a3 100644
--- a/dbaccess/source/ui/inc/sbamultiplex.hxx
+++ b/dbaccess/source/ui/inc/sbamultiplex.hxx
@@ -259,7 +259,7 @@ namespace dbaui
:public OSbaWeakSubObject
,public css::beans::XVetoableChangeListener
{
-typedef ::comphelper::OMultiTypeInterfaceContainerHelperVar2 ListenerContainerMap;
+typedef
::comphelper::OMultiTypeInterfaceContainerHelperVar3 ListenerContainerMap;
ListenerContainerMapm_aListeners;
public:
@@ -272,18 +272,18 @@ namespace dbaui
virtual void SAL_CALL vetoableChange(const
css::beans::PropertyChangeEvent& e) override;
-void addInterface(const OUString& rName, const css::uno::Reference<
css::uno::XInterface >& rListener);
-void removeInterface(const OUString& rName, const css::uno::Reference<
css::uno::XInterface >& rListener);
+void addInterface(const OUString& rName, const css::uno::Reference<
css::beans::XVetoableChangeListener >& rListener);
+void removeInterface(const OUString& rName, const css::uno::Reference<
css::beans::XVetoableChangeListener >& rListener);
void disposeAndClear();
sal_Int32 getOverallLen() const;
-::comphelper::OInterfaceContainerHelper2* getContainer(const OUString&
rName)
+
::comphelper::OInterfaceContainerHelper3*
getContainer(const OUString& rName)
{ return
[Libreoffice-commits] core.git: comphelper/source
comphelper/source/property/genericpropertyset.cxx |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
New commits:
commit 0edde043a03cb7c6b6123d79700bfcdff9882f88
Author: Noel Grandin
AuthorDate: Wed Dec 1 18:28:50 2021 +0200
Commit: Noel Grandin
CommitDate: Fri Dec 3 08:36:28 2021 +0100
use OMultiTypeInterfaceContainerHelperVar3 in GenericPropertySet
Change-Id: I8ce94a11b632f51086480acef8dcfc3e8bea1b65
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/126193
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/comphelper/source/property/genericpropertyset.cxx
b/comphelper/source/property/genericpropertyset.cxx
index 68ae7a3353b4..26f21e987e29 100644
--- a/comphelper/source/property/genericpropertyset.cxx
+++ b/comphelper/source/property/genericpropertyset.cxx
@@ -25,7 +25,7 @@
#include
#include
#include
-#include
+#include
#include
#include
#include
@@ -57,7 +57,7 @@ namespace comphelper
{
private:
std::map maAnyMap;
-comphelper::OMultiTypeInterfaceContainerHelperVar2
m_aListener;
+
comphelper::OMultiTypeInterfaceContainerHelperVar3 m_aListener;
protected:
virtual void _setPropertyValues( const PropertyMapEntry** ppEntries,
const Any* pValues ) override;
@@ -148,7 +148,7 @@ void GenericPropertySet::_setPropertyValues( const
PropertyMapEntry** ppEntries,
while( *ppEntries )
{
-OInterfaceContainerHelper2 * pHelper =
m_aListener.getContainer((*ppEntries)->maName);
+OInterfaceContainerHelper3 * pHelper =
m_aListener.getContainer((*ppEntries)->maName);
maAnyMap[ (*ppEntries)->maName ] = *pValues;
[Libreoffice-bugs] [Bug 95512] Small usability error in placement of context-based list controls
https://bugs.documentfoundation.org/show_bug.cgi?id=95512 Luke Kendall changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #7 from Luke Kendall --- The UI now keeps the Find arrows and other UI elements in that area in the same places, and instead adds the extra buttons above all those elements. Thanks, much appreciated. Version: 7.2.3.2 / LibreOffice Community Build ID: d166454616c1632304285822f9c83ce2e660fd92 CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/source
sw/source/filter/ww8/ww8par.cxx |9 -
1 file changed, 9 deletions(-)
New commits:
commit f8fa0d27074ec1af450196efa1be14ae1dda9314
Author: Miklos Vajna
AuthorDate: Thu Dec 2 20:13:55 2021 +0100
Commit: Miklos Vajna
CommitDate: Fri Dec 3 08:23:30 2021 +0100
sw: remove useless debug code in SwWW8ImplReader
One can check the value of addString in a debugger without this code.
Change-Id: I863b3c70e741f270b5aac07ba2c0fa5186daeaa7
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/126261
Tested-by: Jenkins
Reviewed-by: Miklos Vajna
diff --git a/sw/source/filter/ww8/ww8par.cxx b/sw/source/filter/ww8/ww8par.cxx
index cf5f4fe2cb6e..a23d4ee4ece4 100644
--- a/sw/source/filter/ww8/ww8par.cxx
+++ b/sw/source/filter/ww8/ww8par.cxx
@@ -133,11 +133,6 @@
#include
-#if OSL_DEBUG_LEVEL > 1
-#include
-#include
-#endif
-
#include
#include
#include "WW8Sttbf.hxx"
@@ -3450,10 +3445,6 @@ void SwWW8ImplReader::simpleAddTextToParagraph(const
OUString& rAddString)
if (addString.isEmpty())
return;
-#if OSL_DEBUG_LEVEL > 1
-SAL_INFO("sw.ww8", "" << addString <<
"");
-#endif
-
const SwContentNode *pCntNd = m_pPaM->GetContentNode();
const SwTextNode* pNd = pCntNd ? pCntNd->GetTextNode() : nullptr;
[Libreoffice-bugs] [Bug 46462] trouble opening files with backslashes in file name
https://bugs.documentfoundation.org/show_bug.cgi?id=46462 --- Comment #10 from ajv...@gmail.com --- Still present in 7.0.4.2 2021 Dec. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95969] Wrapping contour trims/crops/clips an image like a image mask
https://bugs.documentfoundation.org/show_bug.cgi?id=95969 --- Comment #6 from Mike Kaganski --- Repro with Version: 7.2.3.2 (x64) / LibreOffice Community Build ID: d166454616c1632304285822f9c83ce2e660fd92 CPU threads: 12; OS: Windows 10.0 Build 19043; UI render: default; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sot/source vcl/source vcl/win
sot/source/base/exchange.cxx |2 +-
vcl/source/treelist/transfer.cxx | 10 +-
vcl/win/dtrans/ftransl.cxx |5 +++--
3 files changed, 5 insertions(+), 12 deletions(-)
New commits:
commit 52e1d0ca6ad38b4b4fdc77b0951ad26f0ac18ec5
Author: Mike Kaganski
AuthorDate: Thu Dec 2 08:50:41 2021 +0300
Commit: Mike Kaganski
CommitDate: Fri Dec 3 08:13:24 2021 +0100
Windows format name is UniformResourceLocatorW for Unicode strings
See also commit 5fb9f4ffa9284c7248e2e82210506babaad4044d
tdf#145964: Windows format name is FileNameW for Unicode strings
TODO: replace one remaining format from CFSTR_* family that we use (see
https://www.codeproject.com/Reference/1091137/Windows-Clipboard-Formats):
FileGroupDescriptor -> FileGroupDescriptorW. That one needs more complex
handling.
Change-Id: I4d4ad83099854768cf36c7b3d89059d79c8e77f6
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/126213
Tested-by: Mike Kaganski
Reviewed-by: Mike Kaganski
diff --git a/sot/source/base/exchange.cxx b/sot/source/base/exchange.cxx
index 2d26887557a6..3138d89de0aa 100644
--- a/sot/source/base/exchange.cxx
+++ b/sot/source/base/exchange.cxx
@@ -156,7 +156,7 @@ const DataFlavorRepresentation* FormatArray_Impl()
/*101 SotClipboardFormatId::NETSCAPE_IMAGE*/ {
"application/x-openoffice-netscape-image;windows_formatname=\"Netscape Image
Format\"", "Netscape Image Format", ::UnoType>::get() },
/*102 SotClipboardFormatId::SBA_FORMEXCHANGE*/ {
"application/x-openoffice-sba-formexchange;windows_formatname=\"SBA_FORMEXCHANGE\"",
"SBA_FORMEXCHANGE", ::UnoType>::get() },
/*103 SotClipboardFormatId::SBA_REPORTEXCHANGE*/ {
"application/x-openoffice-sba-reportexchange;windows_formatname=\"SBA_REPORTEXCHANGE\"",
"SBA_REPORTEXCHANGE", ::UnoType>::get() },
-/*104 SotClipboardFormatId::UNIFORMRESOURCELOCATOR*/ {
"application/x-openoffice-uniformresourcelocator;windows_formatname=\"UniformResourceLocator\"",
"UniformResourceLocator", ::UnoType>::get() },
+/*104 SotClipboardFormatId::UNIFORMRESOURCELOCATOR*/ {
"application/x-openoffice-uniformresourcelocator;windows_formatname=\"UniformResourceLocatorW\"",
"UniformResourceLocator", ::UnoType::get() },
/*105 SotClipboardFormatId::STARCHARTDOCUMENT_50*/ {
"application/x-openoffice-starchartdocument-50;windows_formatname=\"StarChartDocument
5.0\"", "StarChartDocument 5.0", ::UnoType>::get() },
/*106 SotClipboardFormatId::GRAPHOBJ*/ {
"application/x-openoffice-graphobj;windows_formatname=\"Graphic Object\"",
"Graphic Object", ::UnoType>::get() },
/*107 SotClipboardFormatId::STARWRITER_60*/ {
MIMETYPE_VND_SUN_XML_WRITER_ASCII, "Writer 6.0",
::UnoType>::get() },
diff --git a/vcl/source/treelist/transfer.cxx b/vcl/source/treelist/transfer.cxx
index bb245767cb63..81c99653578f 100644
--- a/vcl/source/treelist/transfer.cxx
+++ b/vcl/source/treelist/transfer.cxx
@@ -777,18 +777,10 @@ bool TransferableHelper::SetINetBookmark( const
INetBookmark& rBmk,
break;
case SotClipboardFormatId::STRING:
+case SotClipboardFormatId::UNIFORMRESOURCELOCATOR:
maAny <<= rBmk.GetURL();
break;
-case SotClipboardFormatId::UNIFORMRESOURCELOCATOR:
-{
-OString sURL(OUStringToOString(rBmk.GetURL(), eSysCSet));
-Sequence< sal_Int8 > aSeq( sURL.getLength() );
-memcpy( aSeq.getArray(), sURL.getStr(), sURL.getLength() );
-maAny <<= aSeq;
-}
-break;
-
case SotClipboardFormatId::NETSCAPE_BOOKMARK:
{
Sequence< sal_Int8 > aSeq( 2048 );
diff --git a/vcl/win/dtrans/ftransl.cxx b/vcl/win/dtrans/ftransl.cxx
index 0fc4aa53f804..2d5ecd492754 100644
--- a/vcl/win/dtrans/ftransl.cxx
+++ b/vcl/win/dtrans/ftransl.cxx
@@ -302,10 +302,11 @@ const std::vector< FormatEntry > g_TranslTable {
//SotClipboardFormatId::NETSCAPE_IMAGE
FormatEntry("application/x-openoffice-netscape-image;windows_formatname=\"Netscape
Image Format\"", "Netscape Image Format", nullptr, CF_INVALID,
CPPUTYPE_DEFAULT),
//SotClipboardFormatId::SBA_FORMEXCHANGE
-
FormatEntry("application/x-openoffice-sba-formexchange;windows_formatname=\"SBA_FORMEXCHANGE\"",
"SBA_FORMEXCHANGE", nullptr, CF_INVALID, CPPUTYPE_DEFAULT),
//SotClipboardFormatId::SBA_REPORTEXCHANGE
+
FormatEntry("application/x-openoffice-sba-formexchange;windows_formatname=\"SBA_FORMEXCHANGE\"",
"SBA_FORMEXCHANGE", nullptr, CF_INVALID, CPPUTYPE_DEFAULT),
+//SotClipboardFormatId::SBA_REPORTEXCHANGE
FormatEntry("application/x-openoffice-sba-reportexchange;windows_formatname=\"SBA_REPORTEXCHANGE\"",
"SBA_REPORTEXCHANGE", nullptr, CF_INVALID, CPPUTYPE_DEFAULT),
//SotClipboardFormatId::UNIFORMRESOURCELOCATOR
-
[Libreoffice-commits] core.git: Makefile.in
Makefile.in |1 +
1 file changed, 1 insertion(+)
New commits:
commit 74895bf55846c56cebbd927817b8b9756ed800d0
Author: Stephan Bergmann
AuthorDate: Thu Dec 2 23:11:52 2021 +0100
Commit: Stephan Bergmann
CommitDate: Fri Dec 3 08:05:33 2021 +0100
distclean generated solenv/lockfile/autoconf.h
...introduced with e050b09c7ef193da9da4441d9984c793e35b5a8a "gbuild:
serialize
dynamic link for static builds"
Change-Id: I31410cfe2291d51a860d33fed1861eb933bbb10e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/126264
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann
diff --git a/Makefile.in b/Makefile.in
index 2d94186644ea..e8774a3987c5 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -225,6 +225,7 @@ distclean : clean compilerplugins-clean
$(BUILDDIR)/configure \
$(BUILDDIR)/hardened_runtime.xcent \
$(BUILDDIR)/instsetoo_native/util/openoffice.lst \
+$(BUILDDIR)/solenv/lockfile/autoconf.h \
$(BUILDDIR)/sysui/desktop/macosx/Info.plist \
$(BUILDDIR)/vs-code-template.code-workspace
$(if $(filter WNT,$(OS)),env -i PATH="$$PATH") $(FIND)
$(SRCDIR)/solenv/gdb -name \*.pyc -exec rm {} \;
[Libreoffice-bugs] [Bug 92010] Easier autocomplete access to more frequently used functions
https://bugs.documentfoundation.org/show_bug.cgi?id=92010 Justin L changed: What|Removed |Added CC||jl...@mail.com --- Comment #11 from Justin L --- Yikes. I was going to remove "regression" since master changed so much, but then I saw this commit (which removed references to MRU). author Winfried Donkers on 2014-05-12 16:44:20 + commit 5b0b7553241bb5150b12bbf7625b4b0b36970272 tdf#75264 fix incorrect/missing function tips in Calc -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145982] The Word Joiner feature mentioned in the 7.2 Writer Guide is missing
https://bugs.documentfoundation.org/show_bug.cgi?id=145982 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||0796 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109390] UX: The Hyperlink dialog closes immediately after clicking OK for the the warning dialog: Please type in a valid file name
https://bugs.documentfoundation.org/show_bug.cgi?id=109390 Justin L changed: What|Removed |Added Severity|minor |trivial --- Comment #5 from Justin L --- (In reply to Justin L from comment #4) > I never get a warning dialog on an empty "New Document" hyperlink. Oops. I was always choosing "Document" instead of "New Document". repro 7.4+ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145982] The Word Joiner feature mentioned in the 7.2 Writer Guide is missing
https://bugs.documentfoundation.org/show_bug.cgi?id=145982 Eek! A Bug. Kill it! changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |WONTFIX -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104064] No possibility to override grid when creating an object.
https://bugs.documentfoundation.org/show_bug.cgi?id=104064 Robert Großkopf changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #6 from Robert Großkopf --- Seems it has been changed. Ctrl doesn't work any more. Alt will work instead. And it seems to be it is working for moving any point of a figure ignoring the grid when grid is enabled. It doesn't disable the grid before starting to draw a figure. Tested with LO 7.2.3.2 on OpenSUSE 15.2 with vcl:kf5 I will set this one to worksforme. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109390] UX: The Hyperlink dialog closes immediately after clicking OK for the the warning dialog: Please type in a valid file name
https://bugs.documentfoundation.org/show_bug.cgi?id=109390 --- Comment #4 from Justin L --- I could not reproduce in 6.3 or 6.4 on gtk3 linux with comment 0's STR. I never get a warning dialog on an empty "New Document" hyperlink. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: dbaccess/source include/comphelper
dbaccess/source/ui/browser/sbagrid.cxx | 12 -
dbaccess/source/ui/inc/sbagrid.hxx |6
include/comphelper/multiinterfacecontainer3.hxx | 224
3 files changed, 234 insertions(+), 8 deletions(-)
New commits:
commit cd96af570352ff19b1f1a3d006750237eba8ca5c
Author: Noel Grandin
AuthorDate: Wed Dec 1 18:18:47 2021 +0200
Commit: Noel Grandin
CommitDate: Fri Dec 3 07:37:28 2021 +0100
create OMultiTypeInterfaceContainerHelperVar3 template
to supercede OMultiTypeInterfaceContainerHelperVar2 and add
(a) type-safety
(b) skip the need for doing UNO_QUERY when firing events
Change-Id: Iaeb2421da5d92d2d4fd4feb45ab5019ca85d0d7a
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/126192
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/dbaccess/source/ui/browser/sbagrid.cxx
b/dbaccess/source/ui/browser/sbagrid.cxx
index 16980f05bfe5..5c8ab2095d60 100644
--- a/dbaccess/source/ui/browser/sbagrid.cxx
+++ b/dbaccess/source/ui/browser/sbagrid.cxx
@@ -280,13 +280,14 @@ void SbaXGridPeer::NotifyStatusChanged(const
css::util::URL& _rUrl, const Refere
xControl->statusChanged(aEvt);
else
{
-::comphelper::OInterfaceContainerHelper2 * pIter =
m_aStatusListeners.getContainer(_rUrl);
+::comphelper::OInterfaceContainerHelper3
* pIter
+= m_aStatusListeners.getContainer(_rUrl);
if (pIter)
{
-::comphelper::OInterfaceIteratorHelper2 aListIter(*pIter);
+::comphelper::OInterfaceIteratorHelper3 aListIter(*pIter);
while (aListIter.hasMoreElements())
-static_cast<
css::frame::XStatusListener*>(aListIter.next())->statusChanged(aEvt);
+aListIter.next()->statusChanged(aEvt);
}
}
}
@@ -445,7 +446,8 @@ void SAL_CALL SbaXGridPeer::dispatch(const URL& aURL, const
Sequence< PropertyVa
void SAL_CALL SbaXGridPeer::addStatusListener(const Reference<
css::frame::XStatusListener > & xControl, const css::util::URL& aURL)
{
-::comphelper::OInterfaceContainerHelper2* pCont =
m_aStatusListeners.getContainer(aURL);
+::comphelper::OInterfaceContainerHelper3< css::frame::XStatusListener >*
pCont
+= m_aStatusListeners.getContainer(aURL);
if (!pCont)
m_aStatusListeners.addInterface(aURL,xControl);
else
@@ -455,7 +457,7 @@ void SAL_CALL SbaXGridPeer::addStatusListener(const
Reference< css::frame::XStat
void SAL_CALL SbaXGridPeer::removeStatusListener(const Reference<
css::frame::XStatusListener > & xControl, const css::util::URL& aURL)
{
-::comphelper::OInterfaceContainerHelper2* pCont =
m_aStatusListeners.getContainer(aURL);
+::comphelper::OInterfaceContainerHelper3< css::frame::XStatusListener >*
pCont = m_aStatusListeners.getContainer(aURL);
if ( pCont )
pCont->removeInterface(xControl);
}
diff --git a/dbaccess/source/ui/inc/sbagrid.hxx
b/dbaccess/source/ui/inc/sbagrid.hxx
index fceb8d84f7ad..0d22f6dceec1 100644
--- a/dbaccess/source/ui/inc/sbagrid.hxx
+++ b/dbaccess/source/ui/inc/sbagrid.hxx
@@ -25,7 +25,7 @@
#include
#include
-#include
+#include
#include
#include
#include "sbamultiplex.hxx"
@@ -93,8 +93,8 @@ namespace dbaui
:public FmXGridPeer
,public css::frame::XDispatch
{
-comphelper::OMultiTypeInterfaceContainerHelperVar2<
-css::util::URL, void, SbaURLCompare> m_aStatusListeners;
+comphelper::OMultiTypeInterfaceContainerHelperVar3<
css::frame::XStatusListener,
+css::util::URL, SbaURLCompare> m_aStatusListeners;
public:
SbaXGridPeer(const css::uno::Reference< css::uno::XComponentContext
>&);
diff --git a/include/comphelper/multiinterfacecontainer3.hxx
b/include/comphelper/multiinterfacecontainer3.hxx
new file mode 100644
index ..a9abdd5f77b0
--- /dev/null
+++ b/include/comphelper/multiinterfacecontainer3.hxx
@@ -0,0 +1,224 @@
+/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */
+/*
+ * This file is part of the LibreOffice project.
+ *
+ * This Source Code Form is subject to the terms of the Mozilla Public
+ * License, v. 2.0. If a copy of the MPL was not distributed with this
+ * file, You can obtain one at http://mozilla.org/MPL/2.0/.
+ *
+ * This file incorporates work covered by the following license notice:
+ *
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed
+ * with this work for additional information regarding copyright
+ * ownership. The ASF licenses this file to you under the Apache
+ * License, Version 2.0 (the "License"); you may not use this file
+ * except in compliance with the License. You may obtain a copy of
+ * the License at http://www.apache.org/licenses/LICENSE-2.0 .
+ */
+#pragma once
+
+#include
+
+#include
+#include
+#include
[Libreoffice-bugs] [Bug 112321] Find & Replace All for cell styles only works the second time
https://bugs.documentfoundation.org/show_bug.cgi?id=112321 --- Comment #8 from Justin L --- The whole work-flow here is entirely different from a normal find/replace, so it is hard to know what the correct action should be. repro 7.4+ I guess. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103757] FILESAVE, FORMATTING: Different limits for column/row size in UI and filters
https://bugs.documentfoundation.org/show_bug.cgi?id=103757 --- Comment #5 from Daniel Rentz --- Confirmed in Version: 7.2.3.2 (x64) / LibreOffice Community Build ID: d166454616c1632304285822f9c83ce2e660fd92 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113379] UI Settings icon in Select template not visible initially
https://bugs.documentfoundation.org/show_bug.cgi?id=113379 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INSUFFICIENTDATA --- Comment #4 from Justin L --- The video link in comment 0 is now unavailable, and from my understanding of the report I don't see any actual problem described. It sounds like "settings change after closing the initial wizard dialog" which is exactly what ought to happen when the master page is finalized. Closing as INSUFFICIENT DATA. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145996] Collate Rows and Columns.
https://bugs.documentfoundation.org/show_bug.cgi?id=145996 onlyshi...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from onlyshi...@gmail.com --- Thank you for reporting the bug. Unfortunately I can't reproduce it on Windows 10. Version: 7.4.0.0.alpha0+ (x86) / LibreOffice Community Build ID: 4ac9032163cf55c160145373e7c41741c9c339ca CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 55749] EDITING: wrong character position (1/2 character height displaced down) after copy/paste
https://bugs.documentfoundation.org/show_bug.cgi?id=55749 --- Comment #9 from Rainer Bielefeld Retired --- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: configure.ac
configure.ac | 15 ---
1 file changed, 4 insertions(+), 11 deletions(-)
New commits:
commit 6e334850104b2fe5d325328e64e08c190027f8d9
Author: Jan-Marek Glogowski
AuthorDate: Fri Dec 3 01:13:51 2021 +0100
Commit: Jan-Marek Glogowski
CommitDate: Fri Dec 3 06:51:43 2021 +0100
Normalize --disable-scripting handling
Just add the default value to the platform section and handle the
AC_ARG_ENABLE action-if-not-present accordingly.
Change-Id: I050ace4b20808cedcc4b8ab92f8766c5b5d49d33
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/126266
Tested-by: Jenkins
Reviewed-by: Jan-Marek Glogowski
diff --git a/configure.ac b/configure.ac
index 80ce42b33fcd..c84cad5855a6 100644
--- a/configure.ac
+++ b/configure.ac
@@ -982,6 +982,7 @@ ios*) # iOS
enable_coinmp=no
enable_lpsolve=no
enable_extension_integration=no
+enable_scripting=no
enable_xmlhelp=no
with_ppds=no
if test "$enable_ios_simulator" = "yes"; then
@@ -,6 +1112,7 @@ emscripten)
test_webdav=no
enable_database_connectivity=no
enable_lpsolve=no
+enable_scripting=no
enable_xmlhelp=no
with_system_zlib=no
with_theme="breeze"
@@ -1400,8 +1402,8 @@ libo_FUZZ_ARG_ENABLE(extensions,
AC_ARG_ENABLE(scripting,
AS_HELP_STRING([--disable-scripting],
-[Disable BASIC, Java and Python. Work in progress, use only if you are
hacking on it.])
-)
+[Disable BASIC, Java and Python. Work in progress, use only if you are
hacking on it.]),
+,test "${enable_scripting+set}" = set || enable_scripting=yes)
# This is mainly for Android and iOS, but could potentially be used in some
# special case otherwise, too, so factored out as a separate setting
@@ -2977,14 +2979,6 @@ else
enable_extension_update=no
fi
-if test -z "$enable_scripting"; then
-# Disable scripting for iOS unless specifically overridden
-# with --enable-scripting.
-if test $_os != iOS -o $_os = Emscripten; then
-enable_scripting=yes
-fi
-fi
-
DISABLE_SCRIPTING=''
if test "$enable_scripting" = yes; then
BUILD_TYPE="$BUILD_TYPE SCRIPTING"
@@ -5485,7 +5479,6 @@ if test "$cross_compiling" = "yes"; then
# While we don't need scripting support, we don't have a PYTHON_FOR_BUILD
Java equivalent, so must enable scripting for Java
if test -n "$ENABLE_JAVA"; then
case "$_os" in
-iOS) sub_conf_opts="$sub_conf_opts --disable-scripting" ;; # force it
off, as it used to be
Android)
# Hack for Android - the build doesn't need a host JDK, so just
forward to build for convenience
test -n "$with_jdk_home" && sub_conf_opts="$sub_conf_opts
--with-jdk-home=$with_jdk_home"
[Libreoffice-bugs] [Bug 102847] [META] Quick Find, Search and Replace
https://bugs.documentfoundation.org/show_bug.cgi?id=102847 Aron Budea changed: What|Removed |Added Depends on||140031 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=140031 [Bug 140031] Find & Replace can't tell difference between straight and curly apostrophes (recent regression) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140031] Find & Replace can't tell difference between straight and curly apostrophes (recent regression)
https://bugs.documentfoundation.org/show_bug.cgi?id=140031 Aron Budea changed: What|Removed |Added CC||ba...@caesar.elte.hu Blocks||102847 Keywords||bisected Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102847 [Bug 102847] [META] Quick Find, Search and Replace -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: accessibility/Library_acc.mk accessibility/source configure.ac dbaccess/Module_dbaccess.mk Repository.mk sccomp/Module_sccomp.mk sc/Module_sc.mk scripting/Module_script
Repository.mk |2 +-
accessibility/Library_acc.mk| 13 +
accessibility/source/helper/acc_factory.cxx |6 ++
configure.ac|6 +++---
dbaccess/Module_dbaccess.mk |2 ++
sc/Module_sc.mk |2 ++
sccomp/Module_sccomp.mk |2 +-
scripting/Module_scripting.mk |2 +-
unotest/source/cpp/bootstrapfixturebase.cxx |4 +++-
9 files changed, 28 insertions(+), 11 deletions(-)
New commits:
commit fb308c193bc9f0d07ad2cccd5a0b239f86cbe442
Author: Jan-Marek Glogowski
AuthorDate: Wed May 19 12:16:42 2021 +0200
Commit: Jan-Marek Glogowski
CommitDate: Fri Dec 3 06:46:24 2021 +0100
Fix --disable-scripting for DESKTOP build
Unfortunatly we cannot add --disable-scripting to
sub_conf_defaults, because Java currently has no
equivalent to the PYTHON_FOR_BUILD setting.
Change-Id: I89938a17307a363f5de808200914940503312829
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/126186
Tested-by: Jenkins
Reviewed-by: Jan-Marek Glogowski
diff --git a/Repository.mk b/Repository.mk
index 5b867ca478bc..ee6c60fb33d0 100644
--- a/Repository.mk
+++ b/Repository.mk
@@ -956,7 +956,7 @@ $(eval $(call gb_Helper_register_packages_for_install,ooo,\
$(if $(ENABLE_SCRIPTING_BEANSHELL),scripting_ScriptsBeanShell) \
$(if
$(ENABLE_SCRIPTING_JAVASCRIPT),scripting_ScriptsJavaScript) \
) \
- $(if $(DISABLE_SCRIPTING),,scripting_scriptbindinglib) \
+ $(call gb_Helper_optional,SCRIPTING,scripting_scriptbindinglib) \
$(if $(filter $(OS),MACOSX),sysui_osxicons) \
wizards_basicshare \
wizards_basicsrvaccess2base \
diff --git a/accessibility/Library_acc.mk b/accessibility/Library_acc.mk
index 815e2a88bd70..0926fee97e5d 100644
--- a/accessibility/Library_acc.mk
+++ b/accessibility/Library_acc.mk
@@ -64,10 +64,6 @@ $(eval $(call gb_Library_add_exception_objects,acc,\
accessibility/source/extended/accessibleiconchoicectrlentry \
accessibility/source/extended/accessiblelistbox \
accessibility/source/extended/accessiblelistboxentry \
-accessibility/source/extended/accessibletabbar \
-accessibility/source/extended/accessibletabbarbase \
-accessibility/source/extended/accessibletabbarpage \
-accessibility/source/extended/accessibletabbarpagelist \
accessibility/source/extended/accessibletablistbox \
accessibility/source/extended/accessibletablistboxtable \
accessibility/source/extended/textwindowaccessibility \
@@ -112,4 +108,13 @@ $(eval $(call gb_Library_add_exception_objects,acc,\
accessibility/source/standard/vclxaccessibletoolboxitem \
))
+ifneq ($(filter SCRIPTING,$(BUILD_TYPE)),)
+$(eval $(call gb_Library_add_exception_objects,acc,\
+accessibility/source/extended/accessibletabbar \
+accessibility/source/extended/accessibletabbarbase \
+accessibility/source/extended/accessibletabbarpage \
+accessibility/source/extended/accessibletabbarpagelist \
+))
+endif
+
# vim:set noet sw=4 ts=4:
diff --git a/accessibility/source/helper/acc_factory.cxx
b/accessibility/source/helper/acc_factory.cxx
index 51adeaca8d21..53ed173c15b2 100644
--- a/accessibility/source/helper/acc_factory.cxx
+++ b/accessibility/source/helper/acc_factory.cxx
@@ -17,6 +17,7 @@
* the License at http://www.apache.org/licenses/LICENSE-2.0 .
*/
+#include
#include
#include
@@ -386,7 +387,12 @@ Reference< XAccessible >
AccessibleFactory::createAccessibleIconChoiceCtrl(
Reference< XAccessible > AccessibleFactory::createAccessibleTabBar( TabBar&
_rTabBar ) const
{
+#if HAVE_FEATURE_SCRIPTING
return new AccessibleTabBar( &_rTabBar );
+#else
+(void)_rTabBar;
+return nullptr;
+#endif
}
Reference< XAccessibleContext >
AccessibleFactory::createAccessibleTextWindowContext(
diff --git a/configure.ac b/configure.ac
index e7ea00ef8cb3..80ce42b33fcd 100644
--- a/configure.ac
+++ b/configure.ac
@@ -5482,9 +5482,10 @@ if test "$cross_compiling" = "yes"; then
test -n "$enable_ccache" && sub_conf_opts="$sub_conf_opts
--enable-ccache=$enable_ccache"
test -n "$with_ant_home" && sub_conf_opts="$sub_conf_opts
--with-ant-home=$with_ant_home"
test "$with_junit" = "no" && sub_conf_opts="$sub_conf_opts --without-junit"
+# While we don't need scripting support, we don't have a PYTHON_FOR_BUILD
Java equivalent, so must enable scripting for Java
if test -n "$ENABLE_JAVA"; then
case "$_os" in
-iOS) sub_conf_opts="$sub_conf_opts --without-java" ;; # force it off,
like it used to be
+iOS) sub_conf_opts="$sub_conf_opts --disable-scripting" ;; # force it
off, as it used to be
Android)
# Hack for Android - the build doesn't need a host JDK, so just
forward to build for convenience
test -n "$with_jdk_home" &&
[Libreoffice-bugs] [Bug 91500] Changing heading spacing above paragraph does not work with previous image with caption
https://bugs.documentfoundation.org/show_bug.cgi?id=91500 --- Comment #14 from Edmund Laugasson --- Version: 7.2.3.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: et-EE (et_EE.UTF-8); UI: et-EE 7.2.3-1 Calc: threaded Image with caption: Currently Heading 2 was in proper distance. Image without caption (just plain image) still distance is too small with Heading 2 and changing its indentation above paragraph does not change it actually in text. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-2021' - sc/source
sc/source/core/data/drwlayer.cxx | 16
1 file changed, 12 insertions(+), 4 deletions(-)
New commits:
commit 8065f24a2a480aaafc8f7bb8441ff61607789f31
Author: Julien Nabet
AuthorDate: Thu Nov 25 21:59:57 2021 +0100
Commit: Aron Budea
CommitDate: Fri Dec 3 06:02:48 2021 +0100
tdf#144244: fix crash when FILESAVE a calc file after delete some columns
see bt here:
https://bugs.documentfoundation.org/attachment.cgi?id=176507
Regression from 3238606c8470f3eaeada3fc601e186ec5cfac925
tdf138138 Apply shape shift also to NoRotatedAnchor
The 'normal' anchor (as on screen) is connected to the snap rectangle,
the NoRotatedAnchor is connected to the logic rectangle. They differ,
if the shape is transformed, e.g. rotated. Error was, that values of
the 'normal' anchor were applied to NoRotatedAnchor instead of
calculating the shift of NoRotatedAnchor independently. The error
becomes only visible on save, because there the NoRotatedAnchor is
used. Effected shape types are legacy shapes, text boxes and
transformable OLEs.
I have not tested, whether this fix would work for LO 7.0 too.
Let's apply the same controls as we do with ScDrawObjData retrieved with
GetObjDataTab
Change-Id: I73cb3dd3c47a7ec55667e498d4a62842ce63d861
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/125852
Tested-by: Jenkins
Tested-by: Xisco Fauli
Reviewed-by: Eike Rathke
(cherry picked from commit 1d45f84bd08c8d196fcf3c9baaf2cad010884e5c)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/126140
Reviewed-by: Xisco Fauli
(cherry picked from commit 788859c02f11d264ab04cec4a29a1bcaafc05c18)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/126267
Tested-by: Jenkins CollaboraOffice
Reviewed-by: Aron Budea
diff --git a/sc/source/core/data/drwlayer.cxx b/sc/source/core/data/drwlayer.cxx
index 15440fa3f94b..3aa4649022ab 100644
--- a/sc/source/core/data/drwlayer.cxx
+++ b/sc/source/core/data/drwlayer.cxx
@@ -559,10 +559,18 @@ void ScDrawLayer::MoveCells( SCTAB nTab, SCCOL
nCol1,SCROW nRow1, SCCOL nCol2,SC
ScDrawObjData* pNoRotatedAnchor = GetNonRotatedObjData( pObj );
if ( pNoRotatedAnchor )
{
-pNoRotatedAnchor->maStart.IncCol(nDx);
-pNoRotatedAnchor->maStart.IncRow(nDy);
-pNoRotatedAnchor->maEnd.IncCol(nDx);
-pNoRotatedAnchor->maEnd.IncRow(nDy);
+const ScAddress aOldSttNoRotatedAnchor =
pNoRotatedAnchor->maStart;
+const ScAddress aOldEndNoRotatedAnchor =
pNoRotatedAnchor->maEnd;
+if ( aOldSttNoRotatedAnchor.IsValid() && IsInBlock(
aOldSttNoRotatedAnchor, nCol1,nRow1, nCol2,nRow2 ) )
+{
+pNoRotatedAnchor->maStart.IncCol(nDx);
+pNoRotatedAnchor->maStart.IncRow(nDy);
+}
+if ( aOldEndNoRotatedAnchor.IsValid() && IsInBlock(
aOldEndNoRotatedAnchor, nCol1,nRow1, nCol2,nRow2 ) )
+{
+pNoRotatedAnchor->maEnd.IncCol(nDx);
+pNoRotatedAnchor->maEnd.IncRow(nDy);
+}
}
AddCalcUndo( std::make_unique( pObj, aOldStt,
aOldEnd, pData->maStart, pData->maEnd ) );
[Libreoffice-bugs] [Bug 91494] Format painter made font larger and bold but did not align.
https://bugs.documentfoundation.org/show_bug.cgi?id=91494 --- Comment #7 from Edmund Laugasson --- Tested with LibreOffice Writer in Linux (Arch): Version: 7.2.3.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: et-EE (et_EE.UTF-8); UI: et-EE 7.2.3-1 Calc: threaded Text bold and size attribute were pasted, alignment not. So, still exist that issue with current latest stable version. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145729] Default text alignment on styles when setting locale to RTL language (Hebrew)
https://bugs.documentfoundation.org/show_bug.cgi?id=145729 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145520] LODraw: Export dialog forgets last used format
https://bugs.documentfoundation.org/show_bug.cgi?id=145520 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145760] saving a BASE file LO file does not offer to add password or GPG encryption via the File saving dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=145760 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145757] saving AutoRecovery information cannot be setup, turned off
https://bugs.documentfoundation.org/show_bug.cgi?id=145757 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145568] "Undo" fails to restore text format in some conditions
https://bugs.documentfoundation.org/show_bug.cgi?id=145568 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142104] Copy & paste not working correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=142104 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142104] Copy & paste not working correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=142104 --- Comment #3 from QA Administrators --- Dear paul chaundy, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142089] LIbreoffice crashes at opening a document
https://bugs.documentfoundation.org/show_bug.cgi?id=142089 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142089] LIbreoffice crashes at opening a document
https://bugs.documentfoundation.org/show_bug.cgi?id=142089 --- Comment #8 from QA Administrators --- Dear Jerzy Orlowski, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142085] LibreOffice Impress fails to properly display .tif image files even with hardware accel. disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=142085 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142085] LibreOffice Impress fails to properly display .tif image files even with hardware accel. disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=142085 --- Comment #6 from QA Administrators --- Dear brian.is...@gmail.com, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137574] The image selection frame lagging behind when moving they image with arrow keys
https://bugs.documentfoundation.org/show_bug.cgi?id=137574 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137574] The image selection frame lagging behind when moving they image with arrow keys
https://bugs.documentfoundation.org/show_bug.cgi?id=137574 --- Comment #4 from QA Administrators --- Dear Telesto, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142663] Paragraph Style does not change all lines in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=142663 --- Comment #3 from QA Administrators --- Dear lloyde4628, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142411] LibreOffice paste unformatted text results in Chinese (simplified)
https://bugs.documentfoundation.org/show_bug.cgi?id=142411 --- Comment #2 from QA Administrators --- Dear luancarvalhomartins, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125964] Font not recognized
https://bugs.documentfoundation.org/show_bug.cgi?id=125964 --- Comment #12 from QA Administrators --- Dear seven, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99882] Visual artifact when tables are moved system-driven
https://bugs.documentfoundation.org/show_bug.cgi?id=99882 --- Comment #13 from QA Administrators --- Dear Eric B., To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99804] Can not edit vertical margin text
https://bugs.documentfoundation.org/show_bug.cgi?id=99804 --- Comment #4 from QA Administrators --- Dear Nicolas Mailhot, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99780] Libre Office blocks start of Windows Live Mail
https://bugs.documentfoundation.org/show_bug.cgi?id=99780 --- Comment #4 from QA Administrators --- Dear LeifH, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99731] UI Exit from Edit Mode stops button from acting.
https://bugs.documentfoundation.org/show_bug.cgi?id=99731 --- Comment #4 from QA Administrators --- Dear Mark_T2016, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99714] Paragraph numbering in frames not updated immediately after inserting a new frame
https://bugs.documentfoundation.org/show_bug.cgi?id=99714 --- Comment #17 from QA Administrators --- Dear Hakan, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99668] UNO: API Java example won't run (ArrayOutOfBounds)
https://bugs.documentfoundation.org/show_bug.cgi?id=99668 --- Comment #4 from QA Administrators --- Dear Daniel Brenzel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99660] unreachable condition in generated code OOXMLFactory_shared-math.cxx
https://bugs.documentfoundation.org/show_bug.cgi?id=99660 --- Comment #7 from QA Administrators --- Dear dcb314, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99541] '.uno:GoToCell' call selects an entire column IF the target cell is in column C.
https://bugs.documentfoundation.org/show_bug.cgi?id=99541 --- Comment #9 from QA Administrators --- Dear Fred Hamilton, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99451] Screen keyboard does not correctly accept input of € and @
https://bugs.documentfoundation.org/show_bug.cgi?id=99451 --- Comment #4 from QA Administrators --- Dear Dietrich Klauder, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99408] Dialog Designer doesn't remember Window state
https://bugs.documentfoundation.org/show_bug.cgi?id=99408 --- Comment #4 from QA Administrators --- Dear Samuel Mehrbrodt (CIB), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99391] EDITING Rotating text in a cell rotates also cell background
https://bugs.documentfoundation.org/show_bug.cgi?id=99391 --- Comment #8 from QA Administrators --- Dear Katarina Behrens (CIB), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99259] Cursor being wrongly displayed
https://bugs.documentfoundation.org/show_bug.cgi?id=99259 --- Comment #7 from QA Administrators --- Dear Roberto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99131] Alfred/Finder/Pathfinder will not open files; when opened the Title bar says Untitled 1
https://bugs.documentfoundation.org/show_bug.cgi?id=99131 --- Comment #5 from QA Administrators --- Dear Roger, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99052] continues to select array dimensions after closing 'managed names' dialog box
https://bugs.documentfoundation.org/show_bug.cgi?id=99052 --- Comment #8 from QA Administrators --- Dear rob, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99013] EDITING: Find settings chosen for one document affects searches in all open documents
https://bugs.documentfoundation.org/show_bug.cgi?id=99013 --- Comment #6 from QA Administrators --- Dear Luke Kendall, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98998] Variant Parameter Fails on Non-Executed Branch
https://bugs.documentfoundation.org/show_bug.cgi?id=98998 --- Comment #4 from QA Administrators --- Dear DM, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98973] Extrusion-length of some areas changed after reopening the document
https://bugs.documentfoundation.org/show_bug.cgi?id=98973 --- Comment #12 from QA Administrators --- Dear bugzilla, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98941] Selecting Spell Checking language has no effect
https://bugs.documentfoundation.org/show_bug.cgi?id=98941 --- Comment #4 from QA Administrators --- Dear henpemaz, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98913] Autocomplete multi-line text ignores new line white spaces when filling cell value
https://bugs.documentfoundation.org/show_bug.cgi?id=98913 --- Comment #5 from QA Administrators --- Dear teo8976, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98744] Connector Paragraph Property : Align Top and Align Bottom buttons have reverse effect on text
https://bugs.documentfoundation.org/show_bug.cgi?id=98744 --- Comment #10 from QA Administrators --- Dear Tomek, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98741] LibreOffice print header with Print Selected Area and print wihout header by default
https://bugs.documentfoundation.org/show_bug.cgi?id=98741 --- Comment #5 from QA Administrators --- Dear Maxim Britov, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98711] EDITING: Incorrect bottom connecting point in "manual input" shape (flowcharts)
https://bugs.documentfoundation.org/show_bug.cgi?id=98711 --- Comment #8 from QA Administrators --- Dear Jan Lachnitt, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98669] Space in username is not stripped in 'Other CMIS' configuration
https://bugs.documentfoundation.org/show_bug.cgi?id=98669 --- Comment #7 from QA Administrators --- Dear Jeff, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98644] REMOTE FILE: "The specified device is invalid." error dialog appears when wrong password entered
https://bugs.documentfoundation.org/show_bug.cgi?id=98644 --- Comment #8 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98442] Redo of editing incomplete in comment editing
https://bugs.documentfoundation.org/show_bug.cgi?id=98442 --- Comment #9 from QA Administrators --- Dear Luke Kendall, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98424] FORMATTING circle dashed line segments should be equally spaced
https://bugs.documentfoundation.org/show_bug.cgi?id=98424 --- Comment #5 from QA Administrators --- Dear herr.pfad, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98302] Hidden Section doesnot work properly
https://bugs.documentfoundation.org/show_bug.cgi?id=98302 --- Comment #6 from QA Administrators --- Dear RAV, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98263] Autofill does not respect data validation rule
https://bugs.documentfoundation.org/show_bug.cgi?id=98263 --- Comment #7 from QA Administrators --- Dear Roberto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98221] EDITING Formula gets cut down after entering
https://bugs.documentfoundation.org/show_bug.cgi?id=98221 --- Comment #8 from QA Administrators --- Dear Lorenz25, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98135] Format windows popup takes very long time
https://bugs.documentfoundation.org/show_bug.cgi?id=98135 --- Comment #6 from QA Administrators --- Dear Raf, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98146] VIEWING: Images inserted as a DATA URL are not shown
https://bugs.documentfoundation.org/show_bug.cgi?id=98146 --- Comment #6 from QA Administrators --- Dear Fede, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98001] File/New, Recent documents, Wizards cannot be disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=98001 --- Comment #9 from QA Administrators --- Dear Oliver Specht (CIB), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97967] Highlighting of cell range just flash and disappear
https://bugs.documentfoundation.org/show_bug.cgi?id=97967 --- Comment #4 from QA Administrators --- Dear moreje, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97896] Swedish Help in section "Statistical Functions Part Five" not fully translated
https://bugs.documentfoundation.org/show_bug.cgi?id=97896 --- Comment #5 from QA Administrators --- Dear Peter Bacharach, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97881] Freeze when selecting style for drop cap
https://bugs.documentfoundation.org/show_bug.cgi?id=97881 --- Comment #5 from QA Administrators --- Dear Kurt Wilson, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97838] Date control - earliest year value written is 1600
https://bugs.documentfoundation.org/show_bug.cgi?id=97838 --- Comment #8 from QA Administrators --- Dear Scott Tate, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97641] Beanshell Editor: Translations missing
https://bugs.documentfoundation.org/show_bug.cgi?id=97641 --- Comment #4 from QA Administrators --- Dear Samuel Mehrbrodt (CIB), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97615] Problem with fraction alignment (on Fedora)
https://bugs.documentfoundation.org/show_bug.cgi?id=97615 --- Comment #4 from QA Administrators --- Dear Alexis Clarembeau, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97612] Grid changes when page is resized
https://bugs.documentfoundation.org/show_bug.cgi?id=97612 --- Comment #7 from QA Administrators --- Dear Morten Leikvoll, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97609] On mouseover, text in comments with scroll text effects is not visible.
https://bugs.documentfoundation.org/show_bug.cgi?id=97609 --- Comment #5 from QA Administrators --- Dear coypu, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97494] Row/column gets not always selected
https://bugs.documentfoundation.org/show_bug.cgi?id=97494 --- Comment #4 from QA Administrators --- Dear sworddragon2, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97424] Record macro does not work for "color scale" action
https://bugs.documentfoundation.org/show_bug.cgi?id=97424 --- Comment #4 from QA Administrators --- Dear jari.koso...@rayence.com, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97423] Top and left borders get thinner when copy/paste table from Calc to Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=97423 --- Comment #4 from QA Administrators --- Dear HD, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97390] Menu item 'Recent Documents' not available when Query result window is in front
https://bugs.documentfoundation.org/show_bug.cgi?id=97390 --- Comment #6 from QA Administrators --- Dear Jon Kleiser, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97265] DDE Link update issue - only first link updated on open
https://bugs.documentfoundation.org/show_bug.cgi?id=97265 --- Comment #4 from QA Administrators --- Dear kepesadam88, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97180] parenthesis in text are randomly bold
https://bugs.documentfoundation.org/show_bug.cgi?id=97180 --- Comment #7 from QA Administrators --- Dear teo8976, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97237] Dialog Designer: Changes are always saved
https://bugs.documentfoundation.org/show_bug.cgi?id=97237 --- Comment #5 from QA Administrators --- Dear Samuel Mehrbrodt (CIB), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97152] To lowercase/uppercase not working with some Greek Unicode characters
https://bugs.documentfoundation.org/show_bug.cgi?id=97152 --- Comment #5 from QA Administrators --- Dear nemzag, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97059] Dialog Designer: Mouse click should not close dropdown list
https://bugs.documentfoundation.org/show_bug.cgi?id=97059 --- Comment #4 from QA Administrators --- Dear Samuel Mehrbrodt (CIB), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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.
