core.git: include/tools tools/source
include/tools/globname.hxx| 21 +
tools/source/ref/globname.cxx | 11 ---
2 files changed, 17 insertions(+), 15 deletions(-)
New commits:
commit 70153b7350fbd0c12a63e879a93a443672061044
Author: Mike Kaganski
AuthorDate: Mon Dec 11 17:47:43 2023 +0300
Commit: Mike Kaganski
CommitDate: Tue Dec 12 08:54:59 2023 +0100
Make some SvGlobalName ctors constexpr
Change-Id: Idacca005723b995061dc1df06f98bd584cbfd675
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160606
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/include/tools/globname.hxx b/include/tools/globname.hxx
index 50c3fc27b923..d72b6bf1ab51 100644
--- a/include/tools/globname.hxx
+++ b/include/tools/globname.hxx
@@ -35,17 +35,17 @@ class SvStream;
class SAL_WARN_UNUSED TOOLS_DLLPUBLIC SvGlobalName
{
public:
-SvGlobalName() = default;
-SvGlobalName(const SvGlobalName& rObj) = default;
+constexpr SvGlobalName() = default;
+constexpr SvGlobalName(const SvGlobalName& rObj) = default;
-SvGlobalName( sal_uInt32 n1, sal_uInt16 n2, sal_uInt16 n3,
+inline constexpr SvGlobalName( sal_uInt32 n1, sal_uInt16 n2, sal_uInt16 n3,
sal_uInt8 b8, sal_uInt8 b9, sal_uInt8 b10, sal_uInt8 b11,
sal_uInt8 b12, sal_uInt8 b13, sal_uInt8 b14, sal_uInt8 b15 );
// create SvGlobalName from a platform independent representation
SvGlobalName( const css::uno::Sequence< sal_Int8 >& aSeq );
-SvGlobalName( const SvGUID & rId );
+inline constexpr SvGlobalName( const SvGUID & rId );
SvGlobalName & operator = ( const SvGlobalName & rObj ) = default;
@@ -72,6 +72,19 @@ private:
SvGUID m_aData = {};
};
+inline constexpr SvGlobalName::SvGlobalName(const SvGUID& rId)
+: m_aData(rId)
+{
+}
+
+inline constexpr SvGlobalName::SvGlobalName(sal_uInt32 n1, sal_uInt16 n2,
sal_uInt16 n3,
+sal_uInt8 b8, sal_uInt8 b9,
sal_uInt8 b10,
+sal_uInt8 b11, sal_uInt8 b12,
sal_uInt8 b13,
+sal_uInt8 b14, sal_uInt8 b15)
+: m_aData{ n1, n2, n3, { b8, b9, b10, b11, b12, b13, b14, b15 } }
+{
+}
+
#endif
/* vim:set shiftwidth=4 softtabstop=4 expandtab: */
diff --git a/tools/source/ref/globname.cxx b/tools/source/ref/globname.cxx
index df8ff10943ea..e5cee830df22 100644
--- a/tools/source/ref/globname.cxx
+++ b/tools/source/ref/globname.cxx
@@ -27,17 +27,6 @@
#include
// SvGlobalName
-SvGlobalName::SvGlobalName( const SvGUID & rId ) :
-m_aData( rId )
-{
-}
-
-SvGlobalName::SvGlobalName( sal_uInt32 n1, sal_uInt16 n2, sal_uInt16 n3,
-sal_uInt8 b8, sal_uInt8 b9, sal_uInt8 b10,
sal_uInt8 b11,
-sal_uInt8 b12, sal_uInt8 b13, sal_uInt8 b14,
sal_uInt8 b15 ) :
-m_aData{ n1, n2, n3, { b8, b9, b10, b11, b12, b13, b14, b15 } }
-{
-}
SvGlobalName::SvGlobalName( const css::uno::Sequence < sal_Int8 >& aSeq )
{
[Bug 158649] [beta 1]Wrong Spanish translation for "Footnote or/and Endnote"
https://bugs.documentfoundation.org/show_bug.cgi?id=158649 Julien Nabet changed: What|Removed |Added CC||albac...@gmail.com, ||fit...@ubuntu.com, ||serval2...@yahoo.fr --- Comment #1 from Julien Nabet --- Adolfo/Albert: thought you might be interested in this one. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158656] Page background pictures dont save
https://bugs.documentfoundation.org/show_bug.cgi?id=158656 mithril changed: What|Removed |Added Summary|Page backgound pictures |Page background pictures |dont save |dont save -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158656] New: Page backgound pictures dont save
https://bugs.documentfoundation.org/show_bug.cgi?id=158656 Bug ID: 158656 Summary: Page backgound pictures dont save Product: LibreOffice Version: 7.5.5.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: shigure-k...@protonmail.com Description: Whenever I change the page background to an imported picture in a writer document, for the whole document or different ones for each page, and save the file, the backgrounds will revert to a solid color. This also happens in presentations. Steps to Reproduce: 1.change page background to picture and import it 2.save it, save the document 3.close the document 4.open the document Actual Results: the page background is a solid color Expected Results: page background should be the picture i chose Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158654] Print Dialog box incorrectly renders landscape documents
https://bugs.documentfoundation.org/show_bug.cgi?id=158654 --- Comment #4 from Mubeen --- Created attachment 191376 --> https://bugs.documentfoundation.org/attachment.cgi?id=191376=edit Mismatch print preview AND print - Using HP LaserJet 8000 driver and OfficeJet 9100 This sample file shows that some print drivers in combination of letter paper size do not print and print preview correctly. Tried: 1) HP LaserJet 8000 2) HP OfficeJet 9100 PS 3) Microsoft Print To PDF Mubeen -- You are receiving this mail because: You are the assignee for the bug.
core.git: sw/source
sw/source/core/inc/frame.hxx |4
1 file changed, 4 insertions(+)
New commits:
commit c4ba535eccf1e264d7c9feea48156a2b48000dd6
Author: Miklos Vajna
AuthorDate: Mon Dec 11 20:44:28 2023 +0100
Commit: Miklos Vajna
CommitDate: Tue Dec 12 08:23:00 2023 +0100
sw: document SwFrame::Paste()
It was clear we want to insert a frame, but which frame is to be
inserted and if that will be before or after the non-parent frame was
far from clear. Document this based on how it's implemented in
SwContentFrame::Paste() and SwFrame::InsertBefore().
Change-Id: I3eea471f9feecb35e20910e1869f5db1406d7c43
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160603
Tested-by: Jenkins
Reviewed-by: Miklos Vajna
diff --git a/sw/source/core/inc/frame.hxx b/sw/source/core/inc/frame.hxx
index d57654f6a9e7..1c5aa331f927 100644
--- a/sw/source/core/inc/frame.hxx
+++ b/sw/source/core/inc/frame.hxx
@@ -761,6 +761,10 @@ public:
virtual Size ChgSize( const Size& aNewSize );
virtual void Cut() = 0;
+
+/// Inserts the current frame under pParent, before pSibling.
+///
+/// If pSibling is nullptr, then insert under pParent, at the end.
virtual void Paste( SwFrame* pParent, SwFrame* pSibling = nullptr ) = 0;
void ValidateLineNum() { mbValidLineNum = true; }
core.git: sw/qa sw/source
sw/qa/extras/uiwriter/uiwriter3.cxx | 35 +++
sw/source/core/crsr/crsrsh.cxx |1 +
2 files changed, 36 insertions(+)
New commits:
commit 78fb5e63a4c4832181b92550df567e9b9fd56ba6
Author: Justin Luth
AuthorDate: Thu Dec 7 14:39:08 2023 -0500
Commit: Miklos Vajna
CommitDate: Tue Dec 12 08:22:41 2023 +0100
tdf#111969 sw: acknowledge that last half-character is in selection
Wow, wrong since initial import and no one has touched it yet.
This is not obscure code - it is called on most right mouse clicks
and various other places. Kinda scary to make a change here...
This unit test is copied from testCreateTextRangeByPixelPosition.
Hopefully this pixel code is stable enough for unit tests...
m_bPosMatchesBounds was introduced with
commit cc63f3f550be4c8fe22cc8c6ff874812eefae20e
Author: Vladimir Glazounov on Thu Apr 17 09:08:37 2003 +
make CppunitTest_sw_uiwriter3 \
CPPUNIT_TEST_NAME=testTdf111969_lastHalfcharOfSelection
Change-Id: Ia2bcb93e390d14c9b4c1ab8a7059c41ed1b92429
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160442
Tested-by: Jenkins
Reviewed-by: Justin Luth
Reviewed-by: Miklos Vajna
diff --git a/sw/qa/extras/uiwriter/uiwriter3.cxx
b/sw/qa/extras/uiwriter/uiwriter3.cxx
index 3027c65855ed..0ad197bf1198 100644
--- a/sw/qa/extras/uiwriter/uiwriter3.cxx
+++ b/sw/qa/extras/uiwriter/uiwriter3.cxx
@@ -2371,6 +2371,41 @@ CPPUNIT_TEST_FIXTURE(SwUiWriterTest3, testTdf104649)
CPPUNIT_ASSERT_EQUAL(OUString("Test"), getParagraph(1)->getString());
}
+CPPUNIT_TEST_FIXTURE(SwUiWriterTest3, testTdf111969_lastHalfcharOfSelection)
+{
+// Given a document with a selected character,
+// the last half of the character should also be considered to be "in the
selection"
+createSwDoc();
+SwDoc* pDoc = getSwDoc();
+SwDocShell* pDocShell = pDoc->GetDocShell();
+SwWrtShell* pWrtShell = pDocShell->GetWrtShell();
+// move the cursor after the "o" (this is better/safer than testing cursor
at end of paragrah)
+pWrtShell->Insert2("Hello!");
+pWrtShell->Left(SwCursorSkipMode::Chars, /*bSelect=*/false, 1,
/*bBasicCall=*/false);
+// get last pixel that will be part of the selection (current position 1pt
wide).
+Point aLogicL(pWrtShell->GetCharRect().Center());
+// cursor pos WOULD be in the selection, but just reduce by one for good
measure...
+aLogicL.AdjustX(-1);
+// sanity check - pixel after should NOT be in the selection
+Point aLogicR(pWrtShell->GetCharRect().Center());
+aLogicR.AdjustX(1);
+SwRect aStartRect;
+SwRect aEndRect;
+//now select the letter 'o'
+pWrtShell->Left(SwCursorSkipMode::Chars, /*bSelect=*/true, 1,
/*bBasicCall=*/false);
+
+// sanity check - the selection really does contain (or not) the two logic
points
+pWrtShell->GetCursor_()->FillStartEnd(aStartRect, aEndRect);
+SwRect aSel(aStartRect.TopLeft(), aEndRect.BottomRight());
+CPPUNIT_ASSERT(aSel.Contains(aLogicL));
+CPPUNIT_ASSERT(!aSel.Contains(aLogicR));
+
+// the pixel just at the end of the selection is considered to be in
ModelPositionForViewPoint
+CPPUNIT_ASSERT(pWrtShell->TestCurrPam(aLogicL));
+// the pixel just past the end of the selection is not considered to be
inside.
+CPPUNIT_ASSERT(!pWrtShell->TestCurrPam(aLogicR));
+}
+
CPPUNIT_TEST_FIXTURE(SwUiWriterTest3, testTdf134931)
{
createSwDoc("tdf134931.odt");
diff --git a/sw/source/core/crsr/crsrsh.cxx b/sw/source/core/crsr/crsrsh.cxx
index 04b263cda754..c29020615058 100644
--- a/sw/source/core/crsr/crsrsh.cxx
+++ b/sw/source/core/crsr/crsrsh.cxx
@@ -1292,6 +1292,7 @@ bool SwCursorShell::TestCurrPam(
SwCursorMoveState aTmpState( CursorMoveState::NONE );
aTmpState.m_bSetInReadOnly = IsReadOnlyAvailable();
+aTmpState.m_bPosMatchesBounds = true; // treat last half of character same
as first half
if ( !GetLayout()->GetModelPositionForViewPoint( , aPt,
) && bTstHit )
return false;
[Bug 158654] Print Dialog box incorrectly renders landscape documents
https://bugs.documentfoundation.org/show_bug.cgi?id=158654 --- Comment #3 from Mubeen --- I have noticed, the following 2 symptoms, in particular for multi page document 1) Page 1 is in landscape mode 2) Page 2 is in portrait mode 3) Both page sizes are Letter The print preview will NOT work. On the other hand if: 1) Page 1 is in landscape mode 2) Page 2 is in portrait mode 3) Both page sizes are A4 The print preview will work! It would seem to suggest, LibreOffice either can't communicate correctly with some print drivers or it simply doesn't know how to work correctly US paper sizes. Another symptom, try change the print driver from the drop down list, which would explain why the workaround, sort of works - but doesn't completely work. -- You are receiving this mail because: You are the assignee for the bug.
core.git: Branch 'libreoffice-24-2' - vcl/source
vcl/source/control/listbox.cxx | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
New commits:
commit b0b5ae68cbc95990ad72653212005ef89d7f3ea3
Author: Michael Weghorn
AuthorDate: Fri Dec 8 11:50:40 2023 +0100
Commit: Michael Weghorn
CommitDate: Tue Dec 12 08:16:51 2023 +0100
tdf#158548 vcl: Require mouse over listbox to mouse-wheel through entries
As described in tdf#158548, it's unexpected that listbox/
combobox entries change when using the mouse wheel while the
listbox/combobox has keyboard focus, but the mouse cursor
is positioned somewhere else
Therefore, only do that for the VCL ListBox when the mouse cursor
is currently positioned above it, which also matches what
e.g. native Qt applications do.
(When using the gtk3 VCL plugin that uses a native GtkComboBox,
nothing changes on scroll independent of the position.)
Change-Id: I8a69628471c1cd4258194627b95145d6b8fb686a
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160459
Tested-by: Jenkins
Reviewed-by: Michael Weghorn
(cherry picked from commit 22250df05830700b2555348b8ac46ee1007d0e5d)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160583
diff --git a/vcl/source/control/listbox.cxx b/vcl/source/control/listbox.cxx
index 7e87ae390185..e189c8480f05 100644
--- a/vcl/source/control/listbox.cxx
+++ b/vcl/source/control/listbox.cxx
@@ -867,12 +867,14 @@ bool ListBox::PreNotify( NotifyEvent& rNEvt )
(rNEvt.GetCommandEvent()->GetCommand() ==
CommandEventId::Wheel) &&
(rNEvt.GetWindow() == mpImplWin) )
{
+const Point& rMousePos =
rNEvt.GetCommandEvent()->GetMousePosPixel();
+const tools::Rectangle aWinRect(mpImplWin->GetPosPixel(),
mpImplWin->GetSizePixel());
+const bool bMousePositionedOverWin = aWinRect.Contains(rMousePos);
+
MouseWheelBehaviour nWheelBehavior(
GetSettings().GetMouseSettings().GetWheelBehavior() );
-if ( ( nWheelBehavior == MouseWheelBehaviour::ALWAYS )
-|| ( ( nWheelBehavior == MouseWheelBehaviour::FocusOnly )
-&& HasChildPathFocus()
-)
-)
+if (bMousePositionedOverWin
+&& ((nWheelBehavior == MouseWheelBehaviour::ALWAYS)
+|| ((nWheelBehavior == MouseWheelBehaviour::FocusOnly) &&
HasChildPathFocus(
{
bDone =
mpImplLB->HandleWheelAsCursorTravel(*rNEvt.GetCommandEvent(), *this);
}
[Bug 145081] Line spacing style type "Fixed" is exposed on the property side bar but not on the style sheet dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=145081 Kira Tubo changed: What|Removed |Added CC||kira.t...@gmail.com Assignee|libreoffice-b...@lists.free |kira.t...@gmail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Bug 57202] FORMATTING: Make Header/footer font size independent from scaling of the sheets
https://bugs.documentfoundation.org/show_bug.cgi?id=57202 --- Comment #11 from Mike Kaganski --- This is definitely not a bug, since e.g. in MS Excel, there is an *option* named "Scale with document" (*enabled by default*); so definitely there is a use case for the current implementation as well. However, the lack of a similar option in Calc is an *interoperability* bug, and a missing feature. -- You are receiving this mail because: You are the assignee for the bug.
Re: Need help for bug 158451
On Mon, 2023-12-11 at 03:15 +0100, Regina Henschel wrote: > Steps before the crash are > SwTextFormatter::NewPortion() > SwTextFormatter::CalcFlyWidth() > SwTextFly::GetFrame() > SwTextFly::ForEach() > SwAnchoredObject::GetObjRectWithSpaces() It is possible that this is also been recently picked up with a document I added to crashtesting https://wiki.documentfoundation.org/Development/Crashtesting Try running it under valgrind and see if it is a use-after-free and get those backtraces for the bug, Use valgrind --num-callers=50 or some large enough number to get useful info.
[Bug 158620] TRANSPOSE() should generate a #SPILL! error if cells available are not sufficient to write the result, i.e. Spill range is too big
https://bugs.documentfoundation.org/show_bug.cgi?id=158620 Óvári changed: What|Removed |Added Summary|TRANSPOSE() should generate |TRANSPOSE() should generate |an error if cells available |a #SPILL! error if cells |are not sufficient to write |available are not |the result. |sufficient to write the ||result, i.e. Spill range is ||too big -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158620] TRANSPOSE() should generate an error if cells available are not sufficient to write the result.
https://bugs.documentfoundation.org/show_bug.cgi?id=158620 --- Comment #8 from Óvári --- Created attachment 191375 --> https://bugs.documentfoundation.org/attachment.cgi?id=191375=edit TRANSPOSE Spill range is too big (In reply to Eike Rathke from comment #6) > (In reply to ady from comment #5) > > While I see the potential need to receive some kind of warning regarding the > > procedure described in comment 0, I am not sure that getting an error on the > > cell result (e.g. #REF!) is adequate; the result within the cell is correct. > But that is only _one_ scalar value cell (no matter how many rows or columns > are actually missing), not even a hidden matrix behind it. > > Again, what does Excel do? #SPILL! Spill range it too big -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158620] TRANSPOSE() should generate an error if cells available are not sufficient to write the result.
https://bugs.documentfoundation.org/show_bug.cgi?id=158620 --- Comment #7 from Óvári --- Created attachment 191374 --> https://bugs.documentfoundation.org/attachment.cgi?id=191374=edit TRANSPOSE #SPILL! (In reply to Eike Rathke from comment #6) > (In reply to ady from comment #5) > > While I see the potential need to receive some kind of warning regarding the > > procedure described in comment 0, I am not sure that getting an error on the > > cell result (e.g. #REF!) is adequate; the result within the cell is correct. > But that is only _one_ scalar value cell (no matter how many rows or columns > are actually missing), not even a hidden matrix behind it. > > Again, what does Excel do? #SPILL! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 37903] EDITING: Moving object using ALT - cursor keys also moves the object behind it
https://bugs.documentfoundation.org/show_bug.cgi?id=37903 --- Comment #21 from Gerry --- The bug is still present in Version: 7.5.9.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 16; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: de-DE (fr_FR.UTF-8); UI: de-DE Ubuntu package version: 4:7.5.9-0ubuntu0.23.04.1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158644] invalid registry entries
https://bugs.documentfoundation.org/show_bug.cgi?id=158644 --- Comment #1 from Mike Kaganski --- (In reply to Tracey from comment #0) > registry flag to remove the following: What does it mean? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158595] Performance : PDF export is taking 1min 20 sec
https://bugs.documentfoundation.org/show_bug.cgi?id=158595 Buovjaga changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED CC||ilmari.lauhakangas@libreoff ||ice.org --- Comment #9 from Buovjaga --- Thanks, Steven! While the fix candidate sounds very plausible, there is a mystery: 16aa870598d00eb3e6ac15435fef080d3b87cbc1 has been backported to 7.6 and should have already been in 7.6.0. Even the additional commits toward the bug were backported to 7.6.3. Possibly there is some earlier change affecting this in 24.2 which has not been backported. I would still call it fixed as everybody here confirmed it. I can mention this in the chat. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158533] Incorrectly export number 0 form calc to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=158533 Kira Tubo changed: What|Removed |Added CC||kira.t...@gmail.com, ||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval --- Comment #4 from Kira Tubo --- I guess the question is whether or not we want the exported PDF to display "0" values using the "Zero values" settings from "Print preview" or "Tools" section. I can understand from the user's perspective that it would be pretty easy to assume that the "Zero values" setting from "Print preview" should only controls documents that are physically printed. Maybe something for the UX team to review? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158533] Incorrectly export number 0 form calc to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=158533 Kira Tubo changed: What|Removed |Added CC||kira.t...@gmail.com, ||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval --- Comment #4 from Kira Tubo --- I guess the question is whether or not we want the exported PDF to display "0" values using the "Zero values" settings from "Print preview" or "Tools" section. I can understand from the user's perspective that it would be pretty easy to assume that the "Zero values" setting from "Print preview" should only controls documents that are physically printed. Maybe something for the UX team to review? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 109239] [META] CSV / TSV / Text Import and export / Text to Columns dialogs bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109239 Bug 109239 depends on bug 158548, which changed state. Bug 158548 Summary: File encoding UI element focused on CSV import dialog, changes on unrelated scroll events https://bugs.documentfoundation.org/show_bug.cgi?id=158548 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
core.git: vcl/source
vcl/source/control/listbox.cxx | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
New commits:
commit 22250df05830700b2555348b8ac46ee1007d0e5d
Author: Michael Weghorn
AuthorDate: Fri Dec 8 11:50:40 2023 +0100
Commit: Michael Weghorn
CommitDate: Tue Dec 12 06:22:11 2023 +0100
tdf#158548 vcl: Require mouse over listbox to mouse-wheel through entries
As described in tdf#158548, it's unexpected that listbox/
combobox entries change when using the mouse wheel while the
listbox/combobox has keyboard focus, but the mouse cursor
is positioned somewhere else
Therefore, only do that for the VCL ListBox when the mouse cursor
is currently positioned above it, which also matches what
e.g. native Qt applications do.
(When using the gtk3 VCL plugin that uses a native GtkComboBox,
nothing changes on scroll independent of the position.)
Change-Id: I8a69628471c1cd4258194627b95145d6b8fb686a
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160459
Tested-by: Jenkins
Reviewed-by: Michael Weghorn
diff --git a/vcl/source/control/listbox.cxx b/vcl/source/control/listbox.cxx
index 7e87ae390185..e189c8480f05 100644
--- a/vcl/source/control/listbox.cxx
+++ b/vcl/source/control/listbox.cxx
@@ -867,12 +867,14 @@ bool ListBox::PreNotify( NotifyEvent& rNEvt )
(rNEvt.GetCommandEvent()->GetCommand() ==
CommandEventId::Wheel) &&
(rNEvt.GetWindow() == mpImplWin) )
{
+const Point& rMousePos =
rNEvt.GetCommandEvent()->GetMousePosPixel();
+const tools::Rectangle aWinRect(mpImplWin->GetPosPixel(),
mpImplWin->GetSizePixel());
+const bool bMousePositionedOverWin = aWinRect.Contains(rMousePos);
+
MouseWheelBehaviour nWheelBehavior(
GetSettings().GetMouseSettings().GetWheelBehavior() );
-if ( ( nWheelBehavior == MouseWheelBehaviour::ALWAYS )
-|| ( ( nWheelBehavior == MouseWheelBehaviour::FocusOnly )
-&& HasChildPathFocus()
-)
-)
+if (bMousePositionedOverWin
+&& ((nWheelBehavior == MouseWheelBehaviour::ALWAYS)
+|| ((nWheelBehavior == MouseWheelBehaviour::FocusOnly) &&
HasChildPathFocus(
{
bDone =
mpImplLB->HandleWheelAsCursorTravel(*rNEvt.GetCommandEvent(), *this);
}
core.git: android/source
dev/null |binary 1 file changed New commits: commit 946a7fd8063219b3621fbdc22c28a57ee72a2067 Author: Michael Weghorn AuthorDate: Fri Dec 8 16:12:09 2023 +0100 Commit: Michael Weghorn CommitDate: Tue Dec 12 06:18:22 2023 +0100 android lint: Drop unused image resources Drop unused image resources that lint warns about, e.g.: Change-Id: I69422d485fc324245fd562fd75b016862b29c2a5 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160490 Tested-by: Jenkins Reviewed-by: Michael Weghorn diff --git a/android/source/res/drawable-hdpi/action_search.png b/android/source/res/drawable-hdpi/action_search.png deleted file mode 100644 index e6b70451863a.. Binary files a/android/source/res/drawable-hdpi/action_search.png and /dev/null differ diff --git a/android/source/res/drawable-hdpi/action_search_light.png b/android/source/res/drawable-hdpi/action_search_light.png deleted file mode 100644 index f12e005ebe83.. Binary files a/android/source/res/drawable-hdpi/action_search_light.png and /dev/null differ
core.git: android/source
android/source/res/layout/toolbar_bottom.xml |1 - 1 file changed, 1 deletion(-) New commits: commit 43689c37648adb934ca902c6ae4acb4f8ec831ef Author: Michael Weghorn AuthorDate: Fri Dec 8 16:34:51 2023 +0100 Commit: Michael Weghorn CommitDate: Tue Dec 12 06:17:57 2023 +0100 android lint: Drop extra closing XML tag This was accidently added in commit a21e7a76d745750dcea14bc6311e4f1766c3fa45 Author: Michael Weghorn Date: Thu Nov 9 10:24:13 2023 +0100 android a11y: Add content labels and now reported by lint: Change-Id: If4a17c4cd10450c2f5e13ead88a7511684ab9956 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160469 Tested-by: Jenkins Reviewed-by: Michael Weghorn diff --git a/android/source/res/layout/toolbar_bottom.xml b/android/source/res/layout/toolbar_bottom.xml index 7efb5c0fc7fe..172b215f5a1c 100644 --- a/android/source/res/layout/toolbar_bottom.xml +++ b/android/source/res/layout/toolbar_bottom.xml @@ -478,7 +478,6 @@ android:padding="10dp" android:src="@drawable/ic_search_direction_up" android:contentDescription="@string/search_find_previous" /> -/>
[Bug 158646] LibreOffice recent files application too few files
https://bugs.documentfoundation.org/show_bug.cgi?id=158646 --- Comment #2 from Ian Eales --- I used to see 20+ on Windows on the previous release 7.5.7 Now I see 10 for the same sized window on 7.5.9. sure I can scroll for the other 11 but that's not a feature additionally each 'thumbnail' is a different size 'icon' At the very least, we should be able to choose view style and size AND clicking already selected "Recent Documents" changes to "Templates" <<< Not standard pick list behavior. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158655] New: No furigana (Asian Phonetic Guide) support in LibreOffice Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=158655 Bug ID: 158655 Summary: No furigana (Asian Phonetic Guide) support in LibreOffice Calc Product: LibreOffice Version: 7.6.4.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rondo...@gmail.com Description: LibreOffice Writer supports the use of furigana in kanji through the Asian Phonetic Guide option. However, LibreOffice Calc does not support it in any way, in fact the Asian Phonetic Guide option is shown disabled in the Format menu. From my point of view, this is incomplete support in the LibreOffice suite of the furigana functionality supported through Asian Phonetic Guide. It is not that furigana can be created and edited directly within a Japanese text in a cell, it is not even supported when pasting content, in fact if you copy a Japanese text with furigana from LibreOffice Writer to Calc, the furigana disappears. The only way to get it to display correctly is to paste the text as a LibreOffice 7.6 Text Document format, but doing it this way pastes it as a text box, making the spreadsheet unmanageable. This lack of functionality was already reported a few years ago: https://bugs.documentfoundation.org/show_bug.cgi?id=124473 But from what I see, it is still not implemented. This functionality has been fully supported in Microsoft Excel for years, where you can create furigana in any cell for the kanji, it can be edited directly in the cell and it can be displayed or hidden individually for each cell. Please, we need this functionality to be implemented in LibreOffice Calc, there are many reasons to need to use furigana when filling the contents of a cell with Japanese text, for example to create vocabulary lists for Japanese learners, and many other reasons. I am willing to financially support the development of this functionality through some type of donation, if it is not excessively expensive. Ultimately, although I would prefer not to do it, if there is no developer willing to undertake this task, I am a computer scientist, although I have not programmed for some years, but I would be willing to try to implement it if I receive enough support and help from other LibreOffice developers that they can guide me in the development of LibreOffice, since I have no idea how it is implemented (I don't even know in what programming language it is developed). Steps to Reproduce: 1. Create a Japanese text in LibreOffice Writer that has kanji, and add some furigana for the kanji via the Asian Phonetig Guide option. 2. Copy the text and try to paste it into LibreOffice Calc, either as plain text, as rich format or as HTML, you will see that it is impossible, the furigana disappear. 3. Now try to paste the text in LibreOffice 7.6 Text Document format, you will see that now the furigana characters are displayed correctly above the kanji, but the problem is that it has been pasted as a text box, making the sheet unmanageable. Actual Results: By pasting the text into some manageable format that allows the content to be edited (plain text, RTF or HTML), the furigana disappears. Expected Results: Although you cannot create and edit furigana directly from LibreOffice Calc, as Microsoft Excel does allow, it should at least allow you to paste Japanese text with furigana from LibreOffice Writer, respecting the furigana format and displaying it correctly. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: 60(Build:1) CPU threads: 16; OS: Linux 6.6; UI render: default; VCL: kf5 (cairo+wayland) Locale: es-ES (en_US.UTF-8); UI: en-US 7.6.4-1 Calc: threaded For users who use Linux, we have no alternative. If you use Windows, you can indeed use Microsoft Excel, which supports this functionality. But for those users who usually use Linux, there is no alternative right now, there is no other spreadsheet on the market that supports the use of furigana on Linux. Therefore, LibreOffice being the most complete and important office suite used in Linux, it is important to support this functionality. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 139902] [META] PPTX Image issues
https://bugs.documentfoundation.org/show_bug.cgi?id=139902 Aron Budea changed: What|Removed |Added Depends on||158513 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158513 [Bug 158513] FILESAVE PPTX: background lost -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158513] FILESAVE PPTX: background lost
https://bugs.documentfoundation.org/show_bug.cgi?id=158513 Aron Budea changed: What|Removed |Added Blocks||139902 CC||aron.bu...@gmail.com Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=139902 [Bug 139902] [META] PPTX Image issues -- You are receiving this mail because: You are the assignee for the bug.
core.git: sc/inc sc/source
sc/inc/table.hxx | 10 ++
sc/source/core/data/dociter.cxx | 20 ++--
sc/source/core/data/document.cxx |2 +-
sc/source/core/data/table2.cxx | 16
sc/source/core/data/table4.cxx |2 +-
5 files changed, 22 insertions(+), 28 deletions(-)
New commits:
commit 93801094fa7a3d276dc56138fafbf21029aae4d5
Author: Aron Budea
AuthorDate: Tue Dec 12 02:15:43 2023 +1030
Commit: Mike Kaganski
CommitDate: Tue Dec 12 05:40:12 2023 +0100
sc: Unify GetColumnData
This added ColumnData:
a15c02effa654da06e9695b5e4c0c595f851a878
This added GetColumnData:
1c53f5b6647dcffa57012990d342b21eaff19888
Both functions are the same, one is const, other is non-const.
Change-Id: I8ed214290c7ee8d9e22bd466f9ada95b40300e34
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160601
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/sc/inc/table.hxx b/sc/inc/table.hxx
index 3bf61e701c16..dbfffacc67bf 100644
--- a/sc/inc/table.hxx
+++ b/sc/inc/table.hxx
@@ -309,12 +309,8 @@ public:
// out-of-line the cold part of the function
void CreateColumnIfNotExistsImpl( const SCCOL nScCol );
-ScColumnData& GetColumnData( SCCOL nCol )
-{
-if( nCol >= aCol.size())
-return aDefaultColData;
-return aCol[nCol];
-}
+const ScColumnData& GetColumnData( SCCOL nCol ) const { return nCol <
aCol.size() ? aCol[ nCol ] : aDefaultColData; }
+ScColumnData& GetColumnData( SCCOL nCol ) { return nCol < aCol.size() ?
aCol[ nCol ] : aDefaultColData; }
sal_uInt64 GetCellCount() const;
sal_uInt64 GetWeightedCount() const;
@@ -1187,8 +1183,6 @@ public:
std::set QueryColumnsWithFormulaCells() const;
-const ScColumnData& ColumnData( SCCOL nCol ) const { return nCol <
aCol.size() ? aCol[ nCol ] : aDefaultColData; }
-
void CheckIntegrity() const;
void CollectBroadcasterState(sc::BroadcasterState& rState) const;
diff --git a/sc/source/core/data/dociter.cxx b/sc/source/core/data/dociter.cxx
index 35c0d2caa8fd..6fd13c2e3885 100644
--- a/sc/source/core/data/dociter.cxx
+++ b/sc/source/core/data/dociter.cxx
@@ -1383,7 +1383,7 @@ void ScHorizontalAttrIterator::InitForNextRow(bool
bInitialization)
SCCOL nPos = i - nStartCol;
if ( bInitialization || pNextEnd[nPos] < nRow )
{
-const ScAttrArray& pArray =
rDoc.maTabs[nTab]->ColumnData(i).AttrArray();
+const ScAttrArray& pArray =
rDoc.maTabs[nTab]->GetColumnData(i).AttrArray();
SCSIZE nIndex;
if (bInitialization)
@@ -1579,7 +1579,7 @@ ScDocAttrIterator::ScDocAttrIterator(ScDocument&
rDocument, SCTAB nTable,
nCol( nCol1 )
{
if ( ValidTab(nTab) && nTab < rDoc.GetTableCount() && rDoc.maTabs[nTab] )
-pColIter = rDoc.maTabs[nTab]->ColumnData(nCol).CreateAttrIterator(
nStartRow, nEndRow );
+pColIter = rDoc.maTabs[nTab]->GetColumnData(nCol).CreateAttrIterator(
nStartRow, nEndRow );
}
ScDocAttrIterator::~ScDocAttrIterator()
@@ -1599,7 +1599,7 @@ const ScPatternAttr* ScDocAttrIterator::GetNext( SCCOL&
rCol, SCROW& rRow1, SCRO
++nCol;
if ( nCol <= nEndCol )
-pColIter = rDoc.maTabs[nTab]->ColumnData(nCol).CreateAttrIterator(
nStartRow, nEndRow );
+pColIter =
rDoc.maTabs[nTab]->GetColumnData(nCol).CreateAttrIterator( nStartRow, nEndRow );
else
pColIter.reset();
}
@@ -1711,10 +1711,10 @@ ScAttrRectIterator::ScAttrRectIterator(ScDocument&
rDocument, SCTAB nTable,
{
if ( ValidTab(nTab) && nTab < rDoc.GetTableCount() && rDoc.maTabs[nTab] )
{
-pColIter =
rDoc.maTabs[nTab]->ColumnData(nIterStartCol).CreateAttrIterator( nStartRow,
nEndRow );
+pColIter =
rDoc.maTabs[nTab]->GetColumnData(nIterStartCol).CreateAttrIterator( nStartRow,
nEndRow );
while ( nIterEndCol < nEndCol &&
-rDoc.maTabs[nTab]->ColumnData(nIterEndCol).IsAllAttrEqual(
-rDoc.maTabs[nTab]->ColumnData(nIterEndCol+1), nStartRow,
nEndRow ) )
+rDoc.maTabs[nTab]->GetColumnData(nIterEndCol).IsAllAttrEqual(
+rDoc.maTabs[nTab]->GetColumnData(nIterEndCol+1),
nStartRow, nEndRow ) )
++nIterEndCol;
}
}
@@ -1728,7 +1728,7 @@ void ScAttrRectIterator::DataChanged()
if (pColIter)
{
SCROW nNextRow = pColIter->GetNextRow();
-pColIter =
rDoc.maTabs[nTab]->ColumnData(nIterStartCol).CreateAttrIterator( nNextRow,
nEndRow );
+pColIter =
rDoc.maTabs[nTab]->GetColumnData(nIterStartCol).CreateAttrIterator( nNextRow,
nEndRow );
}
}
@@ -1749,10 +1749,10 @@ const ScPatternAttr* ScAttrRectIterator::GetNext(
SCCOL& rCol1, SCCOL& rCol2,
if ( nIterStartCol <= nEndCol )
{
nIterEndCol = nIterStartCol;
-pColIter =
[Bug 158334] EDITING selecting and deselecting a connector is slow
https://bugs.documentfoundation.org/show_bug.cgi?id=158334 Kira Tubo changed: What|Removed |Added Ever confirmed|0 |1 CC||kira.t...@gmail.com Whiteboard| QA:needsComment| Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Kira Tubo --- Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158595] Performance : PDF export is taking 1min 20 sec
https://bugs.documentfoundation.org/show_bug.cgi?id=158595 --- Comment #8 from Steven Casey --- Created attachment 191373 --> https://bugs.documentfoundation.org/attachment.cgi?id=191373=edit FixedCommit This video shows the commit from 24.2 which fixes the culprit commit. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158595] Performance : PDF export is taking 1min 20 sec
https://bugs.documentfoundation.org/show_bug.cgi?id=158595 --- Comment #7 from Steven Casey --- Created attachment 191372 --> https://bugs.documentfoundation.org/attachment.cgi?id=191372=edit CulpritCommit This video shows the commit that caused the issue in 7.2 and beyond -- You are receiving this mail because: You are the assignee for the bug.
[Bug 142806] Freeze/hang when exporting to PDF with style inspector panel active
https://bugs.documentfoundation.org/show_bug.cgi?id=142806 Steven Casey changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||8595 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158595] Performance : PDF export is taking 1min 20 sec
https://bugs.documentfoundation.org/show_bug.cgi?id=158595 Steven Casey changed: What|Removed |Added CC||stca...@csumb.edu See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||2806, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6306 Ever confirmed|0 |1 Keywords|bibisectRequest |bibisected, bisected, ||regression Status|UNCONFIRMED |NEW Version|7.6.3.2 release |7.2.7.2 release --- Comment #6 from Steven Casey --- Takes about 20 seconds for me in: Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Practically instant on: Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 0ddd9f7e055a0c1ecb120de3e40c3fdb8373e9dc CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded I decided to bibisect the Win64-24.2 repo to see which commit fixed the slow exporting. I believe it will be: https://git.libreoffice.org/core/+/16aa870598d00eb3e6ac15435fef080d3b87cbc1 This also makes sense, directly from the commit: "tdf#156306 sw: PDF export: duplicate structure element from ..." I also tried to figure out when this bug was introduced. I bibisected Win64-7.2 repo and found this commit to be the culprit: https://git.libreoffice.org/core/+/cd60a2d31737f491088cfb0789bc014b1e0aad5f Considering this seems to have a fix already in the 24.2 repo, I am not sure exactly what info to change in this report without accidently inconveniencing someone else. I will reach out for guidance and come back to change whatever is needed. In the meantime, I will change the version, set the status to NEW, add some keywords, and add a few "see also" links. I also propose raising the importance to High-Major Shortly, I will also add videos showing my findings. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158650] Scrolling is lagging/freezing everywhere
https://bugs.documentfoundation.org/show_bug.cgi?id=158650 gP changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #2 from gP --- Thanks for your reply Steven, Yes, it's occurring on all documents. I also tried LO in safe mode and the same thing occurs. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158395] Text is white in recovery dialog with light mode appearance for LibreOffice set in OS dark-mode (macOS)
https://bugs.documentfoundation.org/show_bug.cgi?id=158395 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158402] Blank screen after standby
https://bugs.documentfoundation.org/show_bug.cgi?id=158402 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158340] Page Style Header and Footer tabs: Add setting for choosing Header Right/Left Footer Right/Left
https://bugs.documentfoundation.org/show_bug.cgi?id=158340 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158340] Page Style Header and Footer tabs: Add setting for choosing Header Right/Left Footer Right/Left
https://bugs.documentfoundation.org/show_bug.cgi?id=158340 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 129062] [META] Skia library bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=129062 Bug 129062 depends on bug 150555, which changed state. Bug 150555 Summary: Crash after resizing Writer's main window https://bugs.documentfoundation.org/show_bug.cgi?id=150555 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 146134] Difficulty creating mail labels
https://bugs.documentfoundation.org/show_bug.cgi?id=146134 --- Comment #3 from QA Administrators --- Dear JohnG, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 146701] Button size issue in Shapes sidebar in high DPI environments.
https://bugs.documentfoundation.org/show_bug.cgi?id=146701 --- Comment #4 from QA Administrators --- Dear TOKAI KOTARO, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155831] libreoffice does not start on intel i7-3520M integrated graphics except hardware accel is disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=155831 --- Comment #4 from QA Administrators --- Dear krumelmonster, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155828] Missing Table cell attributes to rotate text
https://bugs.documentfoundation.org/show_bug.cgi?id=155828 --- Comment #2 from QA Administrators --- Dear paul.mitterberger, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Bug 98998] Variant Parameter Fails on Non-Executed Branch
https://bugs.documentfoundation.org/show_bug.cgi?id=98998 --- Comment #6 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.
[Bug 155817] Crash when create personalized color for font color in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=155817 --- Comment #3 from QA Administrators --- Dear Clém, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155722] Footers and Pagebreaks are never saved when I edit a saved Spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=155722 --- Comment #2 from QA Administrators --- Dear Ian, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Bug 86536] 4.4.0.0.beta1: couldn't mouse click on TextBox for edit when selection on shape
https://bugs.documentfoundation.org/show_bug.cgi?id=86536 --- Comment #8 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.
[Bug 91961] Vertical text in a table cell rotated through paragraph or character style shows huge cursor at the beginning of the text
https://bugs.documentfoundation.org/show_bug.cgi?id=91961 --- Comment #16 from QA Administrators --- Dear Ramil, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 75634] FILESAVE: DOC: Document saved with a bookmark in a footnote is a corrupt file that cannot be opened by MSO (DOCX opens)
https://bugs.documentfoundation.org/show_bug.cgi?id=75634 --- Comment #13 from QA Administrators --- Dear aurimas.dev, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 75633] Bookmark position slightly read character to the right when bookmark is inside a footnote from .doc file
https://bugs.documentfoundation.org/show_bug.cgi?id=75633 --- Comment #9 from QA Administrators --- Dear aurimas.dev, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 139255] Paragraph border is not continuous, if paragraph contains a list
https://bugs.documentfoundation.org/show_bug.cgi?id=139255 --- Comment #6 from QA Administrators --- Dear DarkTrick, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 39756] Paragraph background color may extend too far FORMATTING
https://bugs.documentfoundation.org/show_bug.cgi?id=39756 --- Comment #17 from QA Administrators --- Dear HansPL, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 113554] ODF: LibreOffice writes an attribute presentation:preset-property which does not exist in ODF
https://bugs.documentfoundation.org/show_bug.cgi?id=113554 --- Comment #9 from QA Administrators --- Dear Regina Henschel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108907] conditional paragraph style does not work with outline level
https://bugs.documentfoundation.org/show_bug.cgi?id=108907 --- Comment #8 from QA Administrators --- Dear Regina Henschel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108536] ODF: Invalid text:start-value="-1" attribute in element
https://bugs.documentfoundation.org/show_bug.cgi?id=108536 --- Comment #8 from QA Administrators --- Dear Regina Henschel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107253] Import from docx with variable in ASK field produces invalid ODF on resave
https://bugs.documentfoundation.org/show_bug.cgi?id=107253 --- Comment #10 from QA Administrators --- Dear Regina Henschel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 106021] FORMATTING: Writer does not accept CSS box model for paragraphs
https://bugs.documentfoundation.org/show_bug.cgi?id=106021 --- Comment #12 from QA Administrators --- Dear Thomas Lendo, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 156443] Windows: alt+numpad doesn't work for Unicode decimal codes, like in WordPad/Word
https://bugs.documentfoundation.org/show_bug.cgi?id=156443 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1059 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158641] inconsistent 'point edit mode' for comments in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=158641 V Stuart Foote changed: What|Removed |Added Status|NEEDINFO|NEW --- Comment #3 from V Stuart Foote --- OK, so confirmed with STR But the comment (ScPostit) is already a "special" drawing shape on a calc sheet assigned its own style "Note", so while it can take the DF cloned from the text box with rounded corners its object type does not include the 'Slant and Corner Radius' of other text object frames. An attribute omission when the comment's (CaptionObj) was implemented? Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158650] Scrolling is lagging/freezing everywhere
https://bugs.documentfoundation.org/show_bug.cgi?id=158650 Steven Casey changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||stca...@csumb.edu Ever confirmed|0 |1 --- Comment #1 from Steven Casey --- Scrolling results in no lag for me, however I am on Windows: Version: 7.5.6.0.0+ (X86_64) / LibreOffice Community Build ID: f0e825382a76d685998be702ed551a00b73476a5 CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded (In reply to gP from comment #0) > Description: > Scrolling is very slow, often freezes or produces display bugs in Calc, > Writer, Draw, Preferences window, Startcenter, menu's dialogboxes, etc. > Seems to be generalized... It is very confusing :( Is this occurring on all documents? Sounds like it is, but, if its on specific documents, could you attach one so we can test using those documents? If possible, adding a screen capture would be extremely helpful as well :) Could you also try starting LO in safe mode (Open LO > Help > Restart in safe mode) and see if the same thing occurs? I have set this report to NEEDINFO, once you reply, please change it back to UNCONFIRMED. Thanks! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158504] "Default Page Style" does not appear as an applied style
https://bugs.documentfoundation.org/show_bug.cgi?id=158504 Kira Tubo changed: What|Removed |Added Regression By||Bjoern Michaelsen Keywords|bibisectRequest |bibisected, bisected CC||bjoern.michaelsen@libreoffi ||ce.org, kira.t...@gmail.com --- Comment #6 from Kira Tubo --- Hm, I don't experience the issue from comment 4 bibisecting on win64-24.2. Could be specific to Linux. - Bibisected win64-24.2. Added Bjoern Michaelsen to cc. Regression introduced at commit: https://git.libreoffice.org/core/+/140079362502408c75ceee67e86d779f61c0ac1b - commit 140079362502408c75ceee67e86d779f61c0ac1b[log] author Bjoern MichaelsenWed Aug 09 11:34:00 2023 +0200 committer Bjoern MichaelsenFri Sep 01 00:05:28 2023 +0200 tree192aac811efa24025ce2059c89a8141a059799d6 parent 345b214c37d1f645dd0e6e084358f8ca81d9ed66 [diff] - commit ebea09b5c456572c2843a8dd0da2aa09649f149b Author: Norbert Thiebaud Date: Wed Sep 13 18:17:10 2023 -0700 source sha:140079362502408c75ceee67e86d779f61c0ac1b - Reproduced on: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community CPU threads: 6; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158654] Print Dialog box incorrectly renders landscape documents
https://bugs.documentfoundation.org/show_bug.cgi?id=158654 Steven Casey changed: What|Removed |Added CC||stca...@csumb.edu --- Comment #2 from Steven Casey --- Not repro for me on: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 0ddd9f7e055a0c1ecb120de3e40c3fdb8373e9dc CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157042] Calc crashes when closed in rtl::str::release<_rtl_uString>(_rtl_uString*)
https://bugs.documentfoundation.org/show_bug.cgi?id=157042 --- Comment #25 from Eric --- The crash is intermittent and doesn't seem to be able to be forced. Also, one thing i seem to notice, if i have a few spreadsheets open (instances not tabs)(say 2 or 3 instances of calc) and then after awhile i close one then the other then the last ( not rapidly and sometimes a minute or more from close to close), it's always the last sheet closing that causes it. Actual content doesn't seem t matter. Each sheet had a few rows of data, not a big crowded sheet with tons of data and hundreds of rows. I think there might be some interaction between the sheets in the calc code? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158647] add a 'comments reviewing' pane
https://bugs.documentfoundation.org/show_bug.cgi?id=158647 Rafael Lima changed: What|Removed |Added CC||rafael.palma.l...@gmail.com --- Comment #3 from Rafael Lima --- Created attachment 191371 --> https://bugs.documentfoundation.org/attachment.cgi?id=191371=edit Comments sidebar in OnlyOffice (In reply to Stéphane Guillou (stragu) from comment #2) > Heiko, I thought there was some "comment sidebar" proposal somewhere? A comment sidebar would be very much welcome. Are there any mockups? I would love to see something similar to the Comment sidebar from OnlyOffice (see attached image). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158647] add a 'comments reviewing' pane
https://bugs.documentfoundation.org/show_bug.cgi?id=158647 Rafael Lima changed: What|Removed |Added CC||rafael.palma.l...@gmail.com --- Comment #3 from Rafael Lima --- Created attachment 191371 --> https://bugs.documentfoundation.org/attachment.cgi?id=191371=edit Comments sidebar in OnlyOffice (In reply to Stéphane Guillou (stragu) from comment #2) > Heiko, I thought there was some "comment sidebar" proposal somewhere? A comment sidebar would be very much welcome. Are there any mockups? I would love to see something similar to the Comment sidebar from OnlyOffice (see attached image). -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 157042] Calc crashes when closed in rtl::str::release<_rtl_uString>(_rtl_uString*)
https://bugs.documentfoundation.org/show_bug.cgi?id=157042 --- Comment #24 from Matt K --- I'm unable to repro using the following: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1f45453152a34beea5ec1b858c45a585ead3a73e CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Can you please provide a sample document on which the crash occurs, with some repro steps of how you interacted with document, particularly if you can repro every time? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158654] Print Dialog box incorrectly renders landscape documents
https://bugs.documentfoundation.org/show_bug.cgi?id=158654 Mubeen changed: What|Removed |Added Hardware|All |x86-64 (AMD64) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158654] Print Dialog box incorrectly renders landscape documents
https://bugs.documentfoundation.org/show_bug.cgi?id=158654 --- Comment #1 from Mubeen --- Created attachment 191370 --> https://bugs.documentfoundation.org/attachment.cgi?id=191370=edit Shows incorrect print dialog box preview -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158514] Add Edit command to right click menu of comments in Calc Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=158514 Rafael Lima changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 Assignee|libreoffice-b...@lists.free |rafael.palma.l...@gmail.com |desktop.org | --- Comment #5 from Rafael Lima --- Here's a proposed solution: https://gerrit.libreoffice.org/c/core/+/160582 When the user double-clicks the comment, it is automatically made visible. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158514] Add Edit command to right click menu of comments in Calc Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=158514 Rafael Lima changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 Assignee|libreoffice-b...@lists.free |rafael.palma.l...@gmail.com |desktop.org | --- Comment #5 from Rafael Lima --- Here's a proposed solution: https://gerrit.libreoffice.org/c/core/+/160582 When the user double-clicks the comment, it is automatically made visible. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158654] New: Print Dialog box incorrectly renders landscape documents
https://bugs.documentfoundation.org/show_bug.cgi?id=158654 Bug ID: 158654 Summary: Print Dialog box incorrectly renders landscape documents Product: LibreOffice Version: 7.6.4.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: minor Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mubee...@yahoo.com Description: When creating a Writer document that has the first page in Landscape mode, the File > Print dialog box shows an incorrect preview of the page. Instead of the page shown in landscape mode, it appears in portrait mode. This also happens for mixed orientation documents. For example, Page 1 = landscape mode and Page 2 = portrait and vise-versa. The preview from the File Print dialog always shows both pages in portrait mode. Doing a simple Print Preview does work, but the File Print dialog box doesn't. Workaround. Re-select the printer from drop down list. Steps to Reproduce: 1.Open Writer 2.Format > Page Style 3.Select Landscape 4. Type "Hello world" 5. File > Print Actual Results: 1) The print preview on the left panel will show the print as a Portrait mode document instead of landscape. 2) Paper size will be blanked out, instead of showing Letter or whatever the printer default. Expected Results: 1) The print preview should show a landscape mode document. 2) Paper size should be automatically selected (instead of blanked out) Reproducible: Always User Profile Reset: No Additional Info: In spite of doing an actual, File > Print Preview (CTRL + SHIFT + O) and seeing the correct page layout, if the user clicks Print, they will still be shown the wrong layout. The workaround is, the user MUST re-select the printer from the drop down list of printers. When that happens, the paper size will be correctly shown and the print preview will be correctly displayed. If the user does not re-select the print and tries to print, the document will not print correctly! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158652] List of comments in Navigator does not update automatically
https://bugs.documentfoundation.org/show_bug.cgi?id=158652 --- Comment #1 from Rafael Lima --- Also, deleting a comment does not update the Navigator. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103369] [META] Bullet, numbered, and outline list bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103369 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||158628 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158628 [Bug 158628] pressing backspace on list with empty paragraph moves the text to previous item or out of the list -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158628] pressing backspace on list with empty paragraph moves the text to previous item or out of the list
https://bugs.documentfoundation.org/show_bug.cgi?id=158628 Stéphane Guillou (stragu) changed: What|Removed |Added Summary|pressing backspace on |pressing backspace on list |numbered list with empty|with empty paragraph moves |paragraph moves the text to |the text to previous item |previous item or out of the |or out of the list |list| Status|UNCONFIRMED |NEW Blocks||103369 Keywords||needsUXEval Version|7.6.2.1 release |Inherited From OOo CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||stephane.guillou@libreoffic ||e.org OS|Windows (All) |All Ever confirmed|0 |1 Hardware|Other |All Severity|normal |enhancement --- Comment #1 from Stéphane Guillou (stragu) --- This was the same in OOo 3.3. How MS Office does it: - first backspace: remove bullet/number _and_ indent - second backspace: take paragraph to first line, does not remove bullet (as nvhorst expects) OnlyOffice behaves like MS Office (with an extra backspace action to remove the indent). I agree that I'd expect the bullet/number to remain, and I would go with how OnlyOffice does it. Couldn't find a duplicate. UX/design team, any thoughts? Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 0ddd9f7e055a0c1ecb120de3e40c3fdb8373e9dc CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103369 [Bug 103369] [META] Bullet, numbered, and outline list bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158628] pressing backspace on list with empty paragraph moves the text to previous item or out of the list
https://bugs.documentfoundation.org/show_bug.cgi?id=158628 Stéphane Guillou (stragu) changed: What|Removed |Added Summary|pressing backspace on |pressing backspace on list |numbered list with empty|with empty paragraph moves |paragraph moves the text to |the text to previous item |previous item or out of the |or out of the list |list| Status|UNCONFIRMED |NEW Blocks||103369 Keywords||needsUXEval Version|7.6.2.1 release |Inherited From OOo CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||stephane.guillou@libreoffic ||e.org OS|Windows (All) |All Ever confirmed|0 |1 Hardware|Other |All Severity|normal |enhancement --- Comment #1 from Stéphane Guillou (stragu) --- This was the same in OOo 3.3. How MS Office does it: - first backspace: remove bullet/number _and_ indent - second backspace: take paragraph to first line, does not remove bullet (as nvhorst expects) OnlyOffice behaves like MS Office (with an extra backspace action to remove the indent). I agree that I'd expect the bullet/number to remain, and I would go with how OnlyOffice does it. Couldn't find a duplicate. UX/design team, any thoughts? Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 0ddd9f7e055a0c1ecb120de3e40c3fdb8373e9dc CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103369 [Bug 103369] [META] Bullet, numbered, and outline list bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158653] New: Comment commands in Calc's menus need to be rearranged
https://bugs.documentfoundation.org/show_bug.cgi?id=158653 Bug ID: 158653 Summary: Comment commands in Calc's menus need to be rearranged Product: LibreOffice Version: 7.6.4.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rafael.palma.l...@gmail.com In Calc there are three places where you can find comment-related commands. The first is in "Insert - Comment". Then there is "View - Comments". And then there is "Sheet - Cell Comments" that appear to host the remaining comment commands in a somewhat obscure place. The first two in "Insert" and "View" feel OK to me... but the other commands in the "Sheet" tab feel lost and hidden in an obscure submenu. Maybe we could relocate them to the "Edit - Comment" menu, as in Writer. Or maybe have them all in "View", except for the "Insert - Comment" command. Present in Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: 60(Build:1) CPU threads: 12; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+wayland) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Ubuntu package version: 4:7.6.4-0ubuntu0.23.10.1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 104160] [META] Bugs and features related to multiple monitor setups
https://bugs.documentfoundation.org/show_bug.cgi?id=104160 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|157065 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=157065 [Bug 157065] Maximising a Base form opens it too wide the next time (Windows, multiple screens) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 117792] Maximised windows for forms or reports in Base are reopened bigger than the actual window (Windows-only)
https://bugs.documentfoundation.org/show_bug.cgi?id=117792 Stéphane Guillou (stragu) changed: What|Removed |Added CC||bugreport...@protonmail.com --- Comment #8 from Stéphane Guillou (stragu) --- *** Bug 157065 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157065] Maximising a Base form opens it too wide the next time (Windows, multiple screens)
https://bugs.documentfoundation.org/show_bug.cgi?id=157065 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED Blocks|104160 | --- Comment #6 from Stéphane Guillou (stragu) --- Ah, we actually already track that in bug 117792. Thank you all! *** This bug has been marked as a duplicate of bug 117792 *** Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=104160 [Bug 104160] [META] Bugs and features related to multiple monitor setups -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158366] Blurry text hinting (possible regression)
https://bugs.documentfoundation.org/show_bug.cgi?id=158366 Stéphane Guillou (stragu) changed: What|Removed |Added Whiteboard| QA:needsComment| Status|UNCONFIRMED |NEEDINFO CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 --- Comment #3 from Stéphane Guillou (stragu) --- No reproduced with 13 pt Georgia in: Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 0ddd9f7e055a0c1ecb120de3e40c3fdb8373e9dc CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Can you please test again with a recent trunk build and if you can still reproduce, provide an example file and the zoom level you see the issue at? https://dev-builds.libreoffice.org/daily/master/current.html Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158652] New: List of comments in Navigator does not update automatically
https://bugs.documentfoundation.org/show_bug.cgi?id=158652 Bug ID: 158652 Summary: List of comments in Navigator does not update automatically Product: LibreOffice Version: 7.6.4.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rafael.palma.l...@gmail.com In Calc, when you insert comments to the document the "Comments" section in the Navigator does not update automatically after inserting the second comment. Steps to reproduce: 1) Open Calc and make sure the Navigator sidebar is visible. 2) Select any cell and insert a comment (with any text) 3) Notice that the "Comments" section can now be expanded because there is one comment. So click the ">" sign to expand the Comments. 4) Now create another comment in any other cell with any text 5) Notice that the comment will not appear in the Navigator If you keep adding comments, they will not appear in the Navigator. They'll only appear after you right-click a comment and then choose "Show comment". Present in Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: 60(Build:1) CPU threads: 12; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+wayland) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Ubuntu package version: 4:7.6.4-0ubuntu0.23.10.1 Calc: threaded Also in Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 7b3b97efbfeae6ef5d8fbe4e4e27b5b765d3eb08 CPU threads: 12; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: pt-BR (pt_BR.UTF-8); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 98889] selected character and word count in statusbar does not update frequently enough when using Shift +
https://bugs.documentfoundation.org/show_bug.cgi?id=98889 Stéphane Guillou (stragu) changed: What|Removed |Added CC||hoss...@libreoffice.org, ||stephane.guillou@libreoffic ||e.org Hardware|x86-64 (AMD64) |All Summary|Error in character selected |selected character and word |count in statusbar when |count in statusbar does not |using |update frequently enough |to change selected text |when using Shift + || OS|Linux (All) |All Priority|lowest |low Blocks||86066 --- Comment #10 from Stéphane Guillou (stragu) --- As commented in duplicate bug 156801: The behaviour has been wrong for a while, just in a slightly different way since 5.4. The two different stages I see: - Character and word count don't update unless cursor _reaches_ a word boundary (for both directions), which was still true in 5.3.0.3 - Character and word count don't update unless cursor _reaches_ a word boundary if using Shift + Right, and unless it _leaves_ a word boundary if using Shift + Left, which is the case in 5.4.0.3. That 5.4 change could be bibisected, but that wouldn't necessarily help much. Hossein, what kind of easyhack could this be? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=86066 [Bug 86066] [META] Bugs and improvements to the statusbar -- You are receiving this mail because: You are the assignee for the bug.
[Bug 86066] [META] Bugs and improvements to the statusbar
https://bugs.documentfoundation.org/show_bug.cgi?id=86066 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||98889 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=98889 [Bug 98889] selected character and word count in statusbar does not update frequently enough when using Shift + -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158651] New: Comment marker in Calc is not visible right after creation (kf5 and gen)
https://bugs.documentfoundation.org/show_bug.cgi?id=158651 Bug ID: 158651 Summary: Comment marker in Calc is not visible right after creation (kf5 and gen) Product: LibreOffice Version: 7.6.4.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rafael.palma.l...@gmail.com Created attachment 191369 --> https://bugs.documentfoundation.org/attachment.cgi?id=191369=edit Video showing the problem In Calc, when you insert a comment there is a triangular marker on the top-right corner of the cell. However, when using kf5 and gen the marker is only partially visible right after the comment is created. The problem does not happen with gtk3. If you scroll up or down, the marker appears as expected. See the attached video for more info. It seems the drawing area needs to be updated. Problem happens with Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: 60(Build:1) CPU threads: 12; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+wayland) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Ubuntu package version: 4:7.6.4-0ubuntu0.23.10.1 Calc: threaded Also happens in Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 7b3b97efbfeae6ef5d8fbe4e4e27b5b765d3eb08 CPU threads: 12; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+wayland) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103479] [META] Word and character count bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103479 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|156801 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156801 [Bug 156801] Inconsistent updating of selected character count -- You are receiving this mail because: You are the assignee for the bug.
[Bug 156801] Inconsistent updating of selected character count
https://bugs.documentfoundation.org/show_bug.cgi?id=156801 Stéphane Guillou (stragu) changed: What|Removed |Added Version|6.0.7.3 release |5.4.0.3 release Blocks|103479 | Resolution|--- |DUPLICATE CC||stephane.guillou@libreoffic ||e.org Status|NEW |RESOLVED --- Comment #3 from Stéphane Guillou (stragu) --- The behaviour has been wrong for a while, just in a slightly different way since 5.4. The two different stages I see: - Character and word count don't update unless cursor _reaches_ a word boundary (for both directions), which was still true in 5.3.0.3 - Character and word count don't update unless cursor _reaches_ a word boundary if using the Right arrow, and unless it _leaves_ a word boundary if using the Left arrow, which is the case in 5.4.0.3. Let's mark as duplicate of earlier bug 98889, and give more details there. *** This bug has been marked as a duplicate of bug 98889 *** Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103479 [Bug 103479] [META] Word and character count bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 98889] Error in character selected count in statusbar when using to change selected text
https://bugs.documentfoundation.org/show_bug.cgi?id=98889 Stéphane Guillou (stragu) changed: What|Removed |Added CC||will.fried...@gmail.com --- Comment #9 from Stéphane Guillou (stragu) --- *** Bug 156801 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158650] New: Scrolling is lagging/freezing everywhere
https://bugs.documentfoundation.org/show_bug.cgi?id=158650 Bug ID: 158650 Summary: Scrolling is lagging/freezing everywhere Product: LibreOffice Version: 7.5.9.2 release Hardware: x86-64 (AMD64) OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: support.dazzler...@passmail.net Description: Scrolling is very slow, often freezes or produces display bugs in Calc, Writer, Draw, Preferences window, Startcenter, menu's dialogboxes, etc. Seems to be generalized... It is very confusing :( Steps to Reproduce: 1.Scroll 2. 3. Actual Results: slow, often freezes or produces display bugs Expected Results: Scroll smoothly with no bugs Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.9.2 (X86_64) / LibreOffice Community Build ID: cdeefe45c17511d326101eed8008ac4092f278a9 CPU threads: 4; OS: Mac OS X 11.7.10; UI render: default; VCL: osx Locale: fr-CA (fr_CA.UTF-8); UI: fr-FR Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 98889] Error in character selected count in statusbar when using to change selected text
https://bugs.documentfoundation.org/show_bug.cgi?id=98889 Stéphane Guillou (stragu) changed: What|Removed |Added CC||rdl...@gmail.com --- Comment #8 from Stéphane Guillou (stragu) --- *** Bug 158378 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158378] Word count don't update when select text by moving Shift and Arrow on keyboard in Chinese.
https://bugs.documentfoundation.org/show_bug.cgi?id=158378 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE Whiteboard| QA:needsComment| --- Comment #1 from Stéphane Guillou (stragu) --- Thank you for the report! I think this is a duplicate of bug 98889, but it is more noticeable for Chinese because of the lack of spaces. *** This bug has been marked as a duplicate of bug 98889 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 51707] Right aligned single line textfield Currency Symbol Problem
https://bugs.documentfoundation.org/show_bug.cgi?id=51707 --- Comment #13 from madmuffin --- I just checked, the bug is still present in LO 7.6.3.2 Version: 7.6.3.2 (X86_64) / LibreOffice Community Build ID: 29d686fea9f6705b262d369fede658f824154cc0 CPU threads: 12; OS: Mac OS X 14.1.2; UI render: Skia/Metal; VCL: osx Locale: de-DE (de_DE.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158649] New: [beta 1]Wrong Spanish translation for "Footnote or/and Endnote"
https://bugs.documentfoundation.org/show_bug.cgi?id=158649 Bug ID: 158649 Summary: [beta 1]Wrong Spanish translation for "Footnote or/and Endnote" Product: LibreOffice Version: 24.2.0.0 alpha1+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Localization Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rgb.m...@gmail.com Created attachment 191368 --> https://bugs.documentfoundation.org/attachment.cgi?id=191368=edit Screenshot of ES UI showing the translation problem In the Text context menu (right click on any paragraph in Writer) for 24.2 beta 1 there are two entries: "Footnote or Endnote" and "Footnotes and Endnotes" that perform different tasks. On the Spanish UI both are translated as "Notas al pie y finales" which introduce confusion (see attached screenshot). The first one should be translated as "Nota al pie o final" instead. Version: 24.2.0.0.beta1 (X86_64) / LibreOffice Community Build ID: 5f390384195b7264c6e52add9e90a39790285249 CPU threads: 8; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb) Locale: es-ES (es_ES.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158635] AutoRecovery cannot be turned off
https://bugs.documentfoundation.org/show_bug.cgi?id=158635 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Stéphane Guillou (stragu) --- Can you please: - install a currently supported version (7.6 preferably) - test again to see if the issue persists - if it does, please share the full information copied from Help > About LibreOffice. Thank you! -- You are receiving this mail because: You are the assignee for the bug.
core.git: sal/rtl
sal/rtl/string.cxx |7 --- sal/rtl/ustring.cxx |7 --- 2 files changed, 14 deletions(-) New commits: commit 76400f66096a5cdc64cbd72ed9a94961b3200216 Author: Stephan Bergmann AuthorDate: Fri Oct 27 15:55:12 2023 +0200 Commit: Stephan Bergmann CommitDate: Mon Dec 11 23:03:53 2023 +0100 Step 3 of removing cargo-cult pragma pack around rtl_[u]String see 8ae3ae4bf75fdd0aaa132c956d9da029baa3adc6 "Step 1 of removing cargo-cult pragma pack around rtl_[u]String" Change-Id: If6c2ea0ab2e7e61cdbc880d7b27d2af7f816e66d Reviewed-on: https://gerrit.libreoffice.org/c/core/+/158568 Tested-by: Jenkins Reviewed-by: Stephan Bergmann diff --git a/sal/rtl/string.cxx b/sal/rtl/string.cxx index 95f51ad288d0..05f87475df0b 100644 --- a/sal/rtl/string.cxx +++ b/sal/rtl/string.cxx @@ -31,13 +31,6 @@ #include -#if defined _WIN32 -// Temporary check to verify that the #pragma pack around rtl_String is indeed cargo cult and can -// safely be removed: -static_assert(alignof (rtl_String) == 4); -static_assert(sizeof (rtl_String) == 12); -#endif - /* === */ #if USE_SDT_PROBES diff --git a/sal/rtl/ustring.cxx b/sal/rtl/ustring.cxx index 6bc595b7f3bf..fe9795710b50 100644 --- a/sal/rtl/ustring.cxx +++ b/sal/rtl/ustring.cxx @@ -40,13 +40,6 @@ #include -#if defined _WIN32 -// Temporary check to verify that the #pragma pack around rtl_uString is indeed cargo cult and can -// safely be removed: -static_assert(alignof (rtl_uString) == 4); -static_assert(sizeof (rtl_uString) == 12); -#endif - /* === */ #if USE_SDT_PROBES
[Bug 158618] Picture made with draw and pasted in Writer disappear when you modify or/and register Writer file
https://bugs.documentfoundation.org/show_bug.cgi?id=158618 --- Comment #6 from m.a.riosv --- Please test: Create a new Writer document. In the original document: Selecting all [Ctrl+A] Menu/Edit/Select all. Select the new document and paste. Everything seems fine. There are several threads in Ask like https://ask.libreoffice.org/t/unhide-hidden-images/19361 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 156042] Inconsistent undo/redo problems with formatting list numbers
https://bugs.documentfoundation.org/show_bug.cgi?id=156042 Stéphane Guillou (stragu) changed: What|Removed |Added CC||oliver.spe...@cib.de --- Comment #2 from Stéphane Guillou (stragu) --- *** Bug 158638 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158638] No undo when changing attributes of numbering symbols
https://bugs.documentfoundation.org/show_bug.cgi?id=158638 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #2 from Stéphane Guillou (stragu) --- Thank you for the report. This is already tracked in bug 156042, marking as duplicate. *** This bug has been marked as a duplicate of bug 156042 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158646] LibreOffice recent files application too few files
https://bugs.documentfoundation.org/show_bug.cgi?id=158646 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Stéphane Guillou (stragu) --- Thank you for the report. Do you mean in the Start Center, where thumbnails of the documents are shown? I can't reproduce on Linux: I can see 12 recent documents. Version: 7.5.9.2 (X86_64) / LibreOffice Community Build ID: cdeefe45c17511d326101eed8008ac4092f278a9 CPU threads: 8; OS: Linux 5.15; 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.
[Bug 158647] add a 'comments reviewing' pane
https://bugs.documentfoundation.org/show_bug.cgi?id=158647 Stéphane Guillou (stragu) changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||stephane.guillou@libreoffic ||e.org --- Comment #2 from Stéphane Guillou (stragu) --- Thanks for the suggestion. Heiko, I thought there was some "comment sidebar" proposal somewhere? -- You are receiving this mail because: You are on the CC list for the bug.
