[Libreoffice-bugs] [Bug 134509] FILEOPEN DOCX: Text behind image (confirmed MSWord layout bug)
https://bugs.documentfoundation.org/show_bug.cgi?id=134509 Justin L changed: What|Removed |Added Summary|FILEOPEN DOCX: Text behind |FILEOPEN DOCX: Text behind |image |image (confirmed MSWord ||layout bug) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143617] can't format long number with natural space in table
https://bugs.documentfoundation.org/show_bug.cgi?id=143617 patrice.karatchentz...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|NEEDINFO|RESOLVED --- Comment #9 from patrice.karatchentz...@gmail.com --- The shame on me... I 'd never thought about format :( For my excuse, the table seems proposes random format for each case (because I did not anything about it, only add rows...). Thank you and excuse me for the lost time! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113618] Cell background color is offset to top-left when copied from CALC to DRAW as metafile
https://bugs.documentfoundation.org/show_bug.cgi?id=113618 --- Comment #6 from syriusamis+libreoff...@gmail.com --- This bug is still present in 7.1.5.2 #99953 indicates that this is more of a core functionality problem rather than an isolated bug. Version: 7.1.5.2 / LibreOffice Community Build ID: 85f04e9f809797b8199d13c421bd8a2b025d52b5 CPU threads: 24; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105868] FILESAVE DOC: TNR with style 12 and direct format font size 11 saved as font size 12 (also 12 in Word)
https://bugs.documentfoundation.org/show_bug.cgi?id=105868 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #9 from Justin L --- Font size 12 instead of 11 fixed in 7.1 with commit 6457d46967f8dbb41199b750d59edde839f24b5d Author: Justin Luth on Wed Aug 5 14:15:14 2020 +0300 tdf#132726 tdf#134948 doc/rtf export: don't PostponeWritingText *** This bug has been marked as a duplicate of bug 132726 *** -- You are receiving this mail because: You are the assignee for the bug.
Ankur Khandelwal license statement
All of my past & future contributions to LibreOffice may be licensed under the MPLv2/LGPLv3+ dual license.
[Libreoffice-commits] core.git: sw/source
sw/source/uibase/shells/basesh.cxx | 49 +++--
1 file changed, 26 insertions(+), 23 deletions(-)
New commits:
commit 0ff5eb97b89f89e770d4397bf76f24fb7cd76b57
Author: Jim Raykowski
AuthorDate: Sun Aug 8 21:43:25 2021 -0800
Commit: Jim Raykowski
CommitDate: Wed Aug 11 07:10:20 2021 +0200
tdf#143577 check node is a text node before use as such
Change-Id: I337c94aa90ed906c5b744171728022ba5f9c64b3
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/120191
Tested-by: Jenkins
Reviewed-by: Jim Raykowski
diff --git a/sw/source/uibase/shells/basesh.cxx
b/sw/source/uibase/shells/basesh.cxx
index 4a0691d36f99..0ef37aeb3a00 100644
--- a/sw/source/uibase/shells/basesh.cxx
+++ b/sw/source/uibase/shells/basesh.cxx
@@ -199,25 +199,26 @@ void SwBaseShell::ExecDelete(SfxRequest )
case SID_DELETE:
if (rSh.GetViewOptions()->IsShowOutlineContentVisibilityButton())
{
+// Disallow if the cursor is at the end of a paragraph and the
document model
+// node at this position is an outline node with folded
content or the next node
+// is an outline node with folded content.
if (rSh.IsEndPara())
{
SwNodeIndex aIdx(rSh.GetCursor()->GetNode());
-// disallow if this is an outline node having folded
content
-bool bVisible = true;
-
aIdx.GetNode().GetTextNode()->GetAttrOutlineContentVisible(bVisible);
-if (!bVisible)
-return;
-// disallow if the next text node is an outline node
having folded content
-++aIdx;
-SwNodeType aNodeType;
-while ((aNodeType = aIdx.GetNode().GetNodeType()) !=
SwNodeType::Text)
-++aIdx;
if (aIdx.GetNode().IsTextNode())
{
-bVisible = true;
+bool bVisible = true;
aIdx.GetNode().GetTextNode()->GetAttrOutlineContentVisible(bVisible);
if (!bVisible)
-return;
+break;
+++aIdx;
+if (aIdx.GetNode().IsTextNode())
+{
+bVisible = true;
+
aIdx.GetNode().GetTextNode()->GetAttrOutlineContentVisible(bVisible);
+if (!bVisible)
+break;
+}
}
}
}
@@ -227,21 +228,23 @@ void SwBaseShell::ExecDelete(SfxRequest )
case FN_BACKSPACE:
if (rSh.GetViewOptions()->IsShowOutlineContentVisibilityButton())
{
+// Disallow if the cursor is at the start of a paragraph and
the document model
+// node at this position is an outline node with folded
content or the previous
+// node is a content node without a layout frame.
if (rSh.IsSttPara())
{
SwNodeIndex aIdx(rSh.GetCursor()->GetNode());
-// disallow if this is a folded outline node
-bool bVisible = true;
-
aIdx.GetNode().GetTextNode()->GetAttrOutlineContentVisible(bVisible);
-if (!bVisible)
-return;
-// disallow if previous text node does not have a layout
frame
---aIdx;
-SwNodeType aNodeType;
-while ((aNodeType = aIdx.GetNode().GetNodeType()) !=
SwNodeType::Text)
+if (aIdx.GetNode().IsTextNode())
+{
+bool bVisible = true;
+
aIdx.GetNode().GetTextNode()->GetAttrOutlineContentVisible(bVisible);
+if (!bVisible)
+break;
--aIdx;
-if (aIdx.GetNode().IsContentNode() &&
!aIdx.GetNode().GetContentNode()->getLayoutFrame(nullptr))
-return;
+if (aIdx.GetNode().IsContentNode() &&
+
!aIdx.GetNode().GetContentNode()->getLayoutFrame(nullptr))
+break;
+}
}
}
if( rSh.IsNoNum() )
[Libreoffice-commits] core.git: chart2/source cui/source desktop/source editeng/source extensions/source o3tl/qa reportdesign/source sc/qa sc/source sd/qa sd/source sfx2/source svx/source sw/source vc
chart2/source/controller/chartapiwrapper/WrappedSymbolProperties.cxx |3 -
chart2/source/controller/main/ChartWindow.cxx|4 +
cui/source/tabpages/chardlg.cxx |3 -
cui/source/tabpages/tpbitmap.cxx |5 +
desktop/source/lib/init.cxx |5 +
editeng/source/editeng/impedit.cxx |8 ++
editeng/source/items/paperinf.cxx|4 -
extensions/source/propctrlr/fontdialog.cxx |5 +
o3tl/qa/test-unit_conversion.cxx |2
reportdesign/source/ui/dlg/Condition.cxx |2
reportdesign/source/ui/misc/UITools.cxx |2
sc/qa/unit/tiledrendering/tiledrendering.cxx |6 +-
sc/source/filter/rtf/rtfparse.cxx|3 -
sc/source/ui/view/drawview.cxx |4 +
sc/source/ui/view/gridwin4.cxx |4 +
sc/source/ui/view/gridwin_dbgutil.cxx|2
sc/source/ui/view/viewdata.cxx |5 +
sd/qa/unit/tiledrendering/LOKitSearchTest.cxx| 28
+-
sd/source/core/annotations/Annotation.cxx|2
sd/source/core/drawdoc.cxx |2
sd/source/ui/view/Outliner.cxx |4 -
sd/source/ui/view/sdview.cxx |4 +
sd/source/ui/view/sdwindow.cxx |4 +
sfx2/source/control/unoctitm.cxx |2
sfx2/source/view/ipclient.cxx|2
svx/source/sdr/overlay/overlayobjectlist.cxx |2
svx/source/sidebar/paragraph/ParaPropertyPanel.cxx | 25
+++-
svx/source/svdraw/sdrpagewindow.cxx |2
svx/source/svdraw/svdmrkv.cxx| 20
---
svx/source/tbxctrls/grafctrl.cxx | 21
++-
sw/source/uibase/dochdl/swdtflvr.cxx | 11 ++-
sw/source/uibase/shells/textsh.cxx |3 -
vcl/source/treelist/transfer.cxx |2
33 files changed, 110 insertions(+), 91 deletions(-)
New commits:
commit fa339b3adb53300ae68913bed87e18caf9f2e262
Author: Tomaž Vajngerl
AuthorDate: Tue Aug 10 08:10:19 2021 +0900
Commit: Tomaž Vajngerl
CommitDate: Wed Aug 11 06:41:17 2021 +0200
convert some LogicToLogic calls to use o3tl::convert instead
If a LogicToLogic uses fixed units, we can use o3tl::convert
instead. We can also do the same for all other cases where
LogicToLogic is used, but that needs additional investigation to
determine if it is safe to do so.
Note:
MapUnit::Pixel is converted to o3tl::Length::pt because it assumed
72 PPI for a logical pixel, which corresponds with the conversion
rate of a point (72 PPI).
Today, 96 PPI is standard, which is also used for o3tl::Length:px.
Change-Id: I29126df38bfcfda74b5d83d4cb880a378aecd18b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/120230
Tested-by: Jenkins
Reviewed-by: Tomaž Vajngerl
diff --git
a/chart2/source/controller/chartapiwrapper/WrappedSymbolProperties.cxx
b/chart2/source/controller/chartapiwrapper/WrappedSymbolProperties.cxx
index 4dfabee4836f..e48875d7c7a2 100644
--- a/chart2/source/controller/chartapiwrapper/WrappedSymbolProperties.cxx
+++ b/chart2/source/controller/chartapiwrapper/WrappedSymbolProperties.cxx
@@ -408,7 +408,8 @@ void lcl_correctSymbolSizeForBitmaps( chart2::Symbol&
rSymbol )
if( xProp->getPropertyValue( "SizePixel" ) >>= aAWTPixelSize )
{
Size aPixelSize(aAWTPixelSize.Width,aAWTPixelSize.Height);
-Size aNewSize = OutputDevice::LogicToLogic(aPixelSize,
MapMode(MapUnit::MapPixel), MapMode(MapUnit::Map100thMM));
+Size aNewSize = o3tl::convert(aPixelSize,
o3tl::Length::pt, o3tl::Length::mm100);
+
aSize = awt::Size( aNewSize.Width(), aNewSize.Height() );
if( aSize.Width == 0 && aSize.Height == 0 )
diff --git a/chart2/source/controller/main/ChartWindow.cxx
b/chart2/source/controller/main/ChartWindow.cxx
index ad5afd131b96..556cc81dcdeb 100644
--- a/chart2/source/controller/main/ChartWindow.cxx
+++ b/chart2/source/controller/main/ChartWindow.cxx
@@ -296,7 +296,9 @@ void ChartWindow::LogicInvalidate(const tools::Rectangle*
pRectangle)
if
Re: Can I submit patches from my colleagues?
Hello Jeff, On Thu, Aug 5, 2021 at 4:17 PM Jeff Huang wrote: Can I submit patches from my colleagues to LibreOffice Gerrit? This is our company license statement: https://lists.freedesktop.org/archives/libreoffice/2020-February/084572.html If I can do this, how can I do? Thank you. Yes, you can submit the patches from your colleagues. There are two options: 1. Submit patches by yourself on behalf of them with your own email address, and add this note in the commit description: Co-authored-by: ... (Other person's name and email address) 2. Add multiple addresses to your Gerrit account, and submit the patches using the email address you want. This is OK as long as the other email is available in your Gerrit account. Every email address should be verified by the owner. On the other hand, we would be happy to see the people submit their patches by themselves. The disadvantage of using a proxy for sending patches is that there would be an indirect communication between the reviewer(s) and the author. As you know, the author should get involved in the submission process to do the changes and fixes suggested by the reviewers before the submission is accepted and merged. Regards, Hossein -- Hossein Nourikhah, Ph.D. Developer Community Architect The Document Foundation (TDF) Email: hoss...@libreoffice.org Wiki: https://wiki.documentfoundation.org/User:Hossein IRC: hossein at libreoffice-dev room in LiberaChat Network irc://irc.libera.chat/#libreoffice-dev
[Libreoffice-bugs] [Bug 143820] New: Mail merge creates pages of the same label. ie one page of duplicates for each individual label
https://bugs.documentfoundation.org/show_bug.cgi?id=143820 Bug ID: 143820 Summary: Mail merge creates pages of the same label. ie one page of duplicates for each individual label Product: LibreOffice Version: 7.0.1.2 release Hardware: Other OS: Mac OS X (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: darkr...@derek.co.nz Description: Mail. Merge has until recently worked perfectly, now I get a page of duplicates for each individual label. Followed the instructions step by step several times to be sure. Running a Mac Pro with OS 14.1.2. Have just installed LibreOffice on a new laptop with Windows 10 and get the same result. Steps to Reproduce: 1.Register a data source 2.Create a label 3.Print using Mail Merge Actual Results: Sheets of duplicate labels produced. So 44 pages of labels instead of 44 individual labels. Expected Results: Should have created 44 individual labels on 8 pages Reproducible: Always User Profile Reset: No Additional Info: Version: 7.0.1.2 Build ID: 7cbcfc562f6eb6708b5ff7d7397325de9e764452 CPU threads: 8; OS: Mac OS X 10.14.6; UI render: default; VCL: osx Locale: en-NZ (en_NZ.UTF-8); UI: en-US Calc: threadedSame result with version 7.1.5.2 on Windows 10 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143119] Writer and Calc (v7.1.4 and v7.2.0) crash when copying content (cmd-C or menu) on macOS if Tamil UI installed
https://bugs.documentfoundation.org/show_bug.cgi?id=143119 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141028] problem with connecting to the cloud via webdav protocol
https://bugs.documentfoundation.org/show_bug.cgi?id=141028 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139750] Calc display does not follow when there are cells of differing height
https://bugs.documentfoundation.org/show_bug.cgi?id=139750 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143564] 20210727 LibreOffice Calc, German version 7.1.5.2, x64: Bedingungen in der Bedingten Formatierung funktionieren nicht korrekt.
https://bugs.documentfoundation.org/show_bug.cgi?id=143564 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138118] Allow rotation of Area Image fills
https://bugs.documentfoundation.org/show_bug.cgi?id=138118 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 138119] Add option for preserving aspect ratio of an Area Image fill
https://bugs.documentfoundation.org/show_bug.cgi?id=138119 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 138119] Add option for preserving aspect ratio of an Area Image fill
https://bugs.documentfoundation.org/show_bug.cgi?id=138119 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 138118] Allow rotation of Area Image fills
https://bugs.documentfoundation.org/show_bug.cgi?id=138118 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 137863] Add source field for images and graphics and auto formatting to appear in presentation
https://bugs.documentfoundation.org/show_bug.cgi?id=137863 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 137863] Add source field for images and graphics and auto formatting to appear in presentation
https://bugs.documentfoundation.org/show_bug.cgi?id=137863 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 137645] Link to Certificate Path setting when available signatures are empty
https://bugs.documentfoundation.org/show_bug.cgi?id=137645 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135886] Change Chart Data Ranges in Calc by using fill handle and drag and drop
https://bugs.documentfoundation.org/show_bug.cgi?id=135886 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 137645] Link to Certificate Path setting when available signatures are empty
https://bugs.documentfoundation.org/show_bug.cgi?id=137645 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 135886] Change Chart Data Ranges in Calc by using fill handle and drag and drop
https://bugs.documentfoundation.org/show_bug.cgi?id=135886 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 143806] docx to PDF export bug
https://bugs.documentfoundation.org/show_bug.cgi?id=143806 --- Comment #4 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143806] docx to PDF export bug
https://bugs.documentfoundation.org/show_bug.cgi?id=143806 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143640] UNO Object Inspector: Crash while clicking on the "Object" tree
https://bugs.documentfoundation.org/show_bug.cgi?id=143640 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143640] UNO Object Inspector: Crash while clicking on the "Object" tree
https://bugs.documentfoundation.org/show_bug.cgi?id=143640 --- Comment #6 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139541] Disparition du texte après import en PDF avec LibreOffice 6.4.2
https://bugs.documentfoundation.org/show_bug.cgi?id=139541 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139541] Disparition du texte après import en PDF avec LibreOffice 6.4.2
https://bugs.documentfoundation.org/show_bug.cgi?id=139541 --- Comment #3 from QA Administrators --- Dear virginie.basille, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135348] Distorted images when exporting to PNG (and possibly other formats) with transparency
https://bugs.documentfoundation.org/show_bug.cgi?id=135348 --- Comment #12 from QA Administrators --- Dear msh, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135348] Distorted images when exporting to PNG (and possibly other formats) with transparency
https://bugs.documentfoundation.org/show_bug.cgi?id=135348 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134938] Spinning Beachball and won't save document when I try to use save in LibreOffice 6.3.6.2
https://bugs.documentfoundation.org/show_bug.cgi?id=134938 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134938] Spinning Beachball and won't save document when I try to use save in LibreOffice 6.3.6.2
https://bugs.documentfoundation.org/show_bug.cgi?id=134938 --- Comment #3 from QA Administrators --- Dear Jim Erwin, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132617] endless auto-save without saving
https://bugs.documentfoundation.org/show_bug.cgi?id=132617 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132617] endless auto-save without saving
https://bugs.documentfoundation.org/show_bug.cgi?id=132617 --- Comment #4 from QA Administrators --- Dear Noel Boutin, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140357] libre Office Calc, Col A vanished, Format->Columns-> Show does not make it appear
https://bugs.documentfoundation.org/show_bug.cgi?id=140357 --- Comment #2 from QA Administrators --- Dear Duncan, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140337] In 7.1.0.3, the Basic macro of calc shows the error "CellAddress method is missing.
https://bugs.documentfoundation.org/show_bug.cgi?id=140337 --- Comment #3 from QA Administrators --- Dear camper, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140331] Program in the use of the process is a crash
https://bugs.documentfoundation.org/show_bug.cgi?id=140331 --- Comment #2 from QA Administrators --- Dear richardcw, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96199] toolbar "popups" like color pickers open in wrong direction when using multiple monitors
https://bugs.documentfoundation.org/show_bug.cgi?id=96199 --- Comment #15 from QA Administrators --- Dear RC, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 89096] Pasting images and text from a website results in distorted images
https://bugs.documentfoundation.org/show_bug.cgi?id=89096 --- Comment #4 from QA Administrators --- Dear Aidas, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 71954] EDITING: drag and drop text into database form fields will not get stored
https://bugs.documentfoundation.org/show_bug.cgi?id=71954 --- Comment #13 from QA Administrators --- Dear e325001, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 70533] EDITING: Drop caps prevents arrow down to move to next line
https://bugs.documentfoundation.org/show_bug.cgi?id=70533 --- Comment #10 from QA Administrators --- Dear Y, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 68065] EDITING: Clicking into half-visible comment selects text, because it shifts the view
https://bugs.documentfoundation.org/show_bug.cgi?id=68065 --- Comment #9 from QA Administrators --- Dear freddi34, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 66503] macOS: Formula bar can not be resized smaller when using secondary monitor
https://bugs.documentfoundation.org/show_bug.cgi?id=66503 --- Comment #11 from QA Administrators --- Dear Tim Richardson, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 53007] VIEWING: In bar (and column) charts, can't totally remove space between bars
https://bugs.documentfoundation.org/show_bug.cgi?id=53007 --- Comment #12 from QA Administrators --- Dear Hyogapag, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 43894] UI: macOS feature Menu Search not available in some localizations
https://bugs.documentfoundation.org/show_bug.cgi?id=43894 --- Comment #18 from QA Administrators --- Dear Martin Steiger, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126829] Able to apply an indent for right justified values in cell, even though indent not selectable.
https://bugs.documentfoundation.org/show_bug.cgi?id=126829 --- Comment #3 from QA Administrators --- Dear themountinman, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126820] Editing: Cannot enter edit mode after Select all
https://bugs.documentfoundation.org/show_bug.cgi?id=126820 --- Comment #3 from QA Administrators --- Dear Emil Tanev, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123417] File with lots of comments opens slower compared to LibO 4.4.7.2
https://bugs.documentfoundation.org/show_bug.cgi?id=123417 --- Comment #8 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121626] When copying sheets or objects (checkboxes/charts) references in the objects are not updated
https://bugs.documentfoundation.org/show_bug.cgi?id=121626 --- Comment #6 from QA Administrators --- Dear Fabio Zaffora, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113618] Cell background color is offset to top-left when copied from CALC to DRAW as metafile
https://bugs.documentfoundation.org/show_bug.cgi?id=113618 --- Comment #5 from QA Administrators --- Dear syriusamis+libreoffice, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108837] Graphic object size will be changed incorrectly under vertical writing mode
https://bugs.documentfoundation.org/show_bug.cgi?id=108837 --- Comment #13 from QA Administrators --- Dear Franklin Weng, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104003] Autofit text option set to false in master slide is not respected as default for new slides
https://bugs.documentfoundation.org/show_bug.cgi?id=104003 --- Comment #9 from QA Administrators --- Dear Antonello, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140202] [META] Issues with files in MS Office formats created by external producers (not MS Office)
https://bugs.documentfoundation.org/show_bug.cgi?id=140202 Aron Budea changed: What|Removed |Added Depends on||142463 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=142463 [Bug 142463] Fileopen DOCX: Different text and table flow (table on 1 page in MSO, splits in LO) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142463] Fileopen DOCX: Different text and table flow (table on 1 page in MSO, splits in LO)
https://bugs.documentfoundation.org/show_bug.cgi?id=142463 Aron Budea changed: What|Removed |Added CC||ba...@caesar.elte.hu Blocks||140202 Keywords|notBibisectable |preBibisect --- Comment #8 from Aron Budea --- (In reply to Timur from comment #4) > Reproduced 7.2+ and back to LO 3.5. Not with 3.4 for DOCX so could be a > regression. To be sure, I checked with oldest of bibisect-43all (which predates 3.5 a bit), and indeed the bug is there already, setting preBibisect. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=140202 [Bug 140202] [META] Issues with files in MS Office formats created by external producers (not MS Office) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143816] Dragging formulae across columns result in persistent wrong data
https://bugs.documentfoundation.org/show_bug.cgi?id=143816 Dmitrii A changed: What|Removed |Added CC||anisimov...@gmail.com --- Comment #3 from Dmitrii A --- no repro in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: ac80ec817eb07c77a51bc0729985a473c734182e CPU threads: 16; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL Hello, this is just formula mistake, for examle G2 "=MAX(G2:G301)" should be "=MAX(G3:G301)". Try to edit and copy this formula to H2, I2, J2 cells. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143819] Undo doesn't restore image anchor position
https://bugs.documentfoundation.org/show_bug.cgi?id=143819 Dmitrii A changed: What|Removed |Added Ever confirmed|0 |1 CC||anisimov...@gmail.com Status|UNCONFIRMED |NEW --- Comment #3 from Dmitrii A --- confirm in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: ac80ec817eb07c77a51bc0729985a473c734182e CPU threads: 16; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 86066] [META] Bugs and improvements to the status bar
https://bugs.documentfoundation.org/show_bug.cgi?id=86066 Aron Budea changed: What|Removed |Added Depends on||143016 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143016 [Bug 143016] Issue with the [Paragraph Selection] section of the status bar -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 86066] [META] Bugs and improvements to the status bar
https://bugs.documentfoundation.org/show_bug.cgi?id=86066 Bug 86066 depends on bug 143016, which changed state. Bug 143016 Summary: Issue with the [Paragraph Selection] section of the status bar https://bugs.documentfoundation.org/show_bug.cgi?id=143016 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143016] Issue with the [Paragraph Selection] section of the status bar
https://bugs.documentfoundation.org/show_bug.cgi?id=143016 Aron Budea changed: What|Removed |Added Resolution|--- |WORKSFORME Version|unspecified |7.0.6.2 release Blocks||86066 CC||ba...@caesar.elte.hu Status|NEW |RESOLVED --- Comment #2 from Aron Budea --- This is fine for me in 7.2.0.1 / Windows, the icon changes (while in 7.1.4.2 it still doesn't get updated). Closing as WORKSFORME. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=86066 [Bug 86066] [META] Bugs and improvements to the status bar -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 86066] [META] Bugs and improvements to the status bar
https://bugs.documentfoundation.org/show_bug.cgi?id=86066 Aron Budea changed: What|Removed |Added Summary|[META] bugs and |[META] Bugs and |improvements to the |improvements to the status |statusbar |bar -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 74862] FILEOPEN: DOC filter: embedded WAV (OLE) does not open properly on Linux
https://bugs.documentfoundation.org/show_bug.cgi?id=74862 Aron Budea changed: What|Removed |Added Blocks||107322 Hardware|x86-64 (AMD64) |All OS|Linux (All) |All Version|unspecified |Inherited From OOo Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107322 [Bug 107322] [META] Media (audio / video) bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107322] [META] Media (audio / video) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107322 Aron Budea changed: What|Removed |Added Depends on||74862 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=74862 [Bug 74862] FILEOPEN: DOC filter: embedded WAV (OLE) does not open properly on Linux -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108731] [META] Export formats available through File > Export...
https://bugs.documentfoundation.org/show_bug.cgi?id=108731 Aron Budea changed: What|Removed |Added Depends on||128731 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=128731 [Bug 128731] exporting a selection crops the result -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128731] exporting a selection crops the result
https://bugs.documentfoundation.org/show_bug.cgi?id=128731 Aron Budea changed: What|Removed |Added Blocks||108731 CC||ba...@caesar.elte.hu Version|unspecified |4.1.0.4 release Keywords||notBibisectable, regression --- Comment #7 from Aron Budea --- For the record, with gen VCL plugin in Linux, since 4.1.0.4 the Selection check box is greyed out if there's no selection, however gtk(3) VCL plugins don't follow that. In addition, when it was possible to tick it without selection (in 4.0.0.3), the complete shape was included in the export. And that was actually the same on Windows in that version, and the behavior changed with 4.1.0.4. Too bad there isn't a 4.1 Windows bibisect repo, and in Linux the gtk VCL plugin in those old builds fail to work in recent Linux versions, thus the regression isn't bibisectable. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108731 [Bug 108731] [META] Export formats available through File > Export... -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108687] Form option buttons not reachable with tab key
https://bugs.documentfoundation.org/show_bug.cgi?id=108687
Christophe Strobbe changed:
What|Removed |Added
CC||c_strobbe-...@yahoo.co.uk
--- Comment #34 from Christophe Strobbe ---
While I can confirm that the issue still exists in LibreOffice 7.1.3.2 (on
OpenSUSE Leap 15.2), I would like to point out that the file attachment does
not demonstrate how forms are intended to be filled in. As the LibreOffice
Writer Guide points out at
https://books.libreoffice.org/en/WG71/WG7118-Forms.html#toc24
[begin quote]
If you plan to send this [form] out to other people to complete, you probably
want to make the document read-only so that users would be able to fill in the
form but not make any other changes to the document.
To make the document read-only, select File > Properties, select the Security
tab and enable Open file read-only.
[end quote]
A similar feature exists in Microsoft Word ("Restrict Editing", so the form can
only be filled in, not modified).
However, when a Writer form is saved in read-only mode and re-opened, the form
fields are not keyboard accessible, as I have reported in bug 143818:
https://bugs.documentfoundation.org/show_bug.cgi?id=143818
With the document in read-only mode, once you use the mouse to put the cursor
into the first text field, you can cycle through all the form fields except the
radio buttons (just as in unprotected mode).
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 85339] FORMCONTROLS: Tabindex is ignored for fields withe the same name
https://bugs.documentfoundation.org/show_bug.cgi?id=85339
Christophe Strobbe changed:
What|Removed |Added
CC||c_strobbe-...@yahoo.co.uk
Keywords||accessibility
--- Comment #11 from Christophe Strobbe ---
While I can confirm that the issue still exists in LibreOffice 7.1.3.2 (on
OpenSUSE Leap 15.2), I would like to point out that the file attachment does
not demonstrate how forms are intended to be filled in. As the LibreOffice
Writer Guide points out at
https://books.libreoffice.org/en/WG71/WG7118-Forms.html#toc24
[begin quote]
If you plan to send this [form] out to other people to complete, you probably
want to make the document read-only so that users would be able to fill in the
form but not make any other changes to the document.
To make the document read-only, select File > Properties, select the Security
tab and enable Open file read-only.
[end quote]
A similar feature exists in Microsoft Word ("Restrict Editing", so the form can
only be filled in, not modified).
However, when a Writer form is saved in read-only mode and re-opened, the form
fields are not keyboard accessible, as I have reported in bug 143818:
https://bugs.documentfoundation.org/show_bug.cgi?id=143818
Probably, that bug needs to be looked into before this bug (85339) can be
tested again in read-only mode.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-commits] core.git: basic/source
basic/source/sbx/sbxscan.cxx |8
1 file changed, 4 insertions(+), 4 deletions(-)
New commits:
commit e89404f00b25cfddd4098b4b2cf900d190617221
Author: Eike Rathke
AuthorDate: Wed Aug 11 01:16:16 2021 +0200
Commit: Eike Rathke
CommitDate: Wed Aug 11 02:34:36 2021 +0200
There is no LANGUAGE_ENGLISH {en} locale but LANGUAGE_ENGLISH_US {en-US}
The known fallback locale is en-US so this worked by chance..
Change-Id: I81ee2aff0cc35b4c8d501dfb6846f0709f1417ef
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/120301
Reviewed-by: Eike Rathke
Tested-by: Jenkins
diff --git a/basic/source/sbx/sbxscan.cxx b/basic/source/sbx/sbxscan.cxx
index a632a689a42f..08f43ab475fa 100644
--- a/basic/source/sbx/sbxscan.cxx
+++ b/basic/source/sbx/sbxscan.cxx
@@ -720,7 +720,7 @@ void SbxValue::Format( OUString& rRes, const OUString* pFmt
) const
else
{
aFmtStr = OUString::createFromAscii(pInfo->mpOOoFormat);
-pFormatter->PutandConvertEntry( aFmtStr, nCheckPos, nType,
nIndex, LANGUAGE_ENGLISH, eLangType, true);
+pFormatter->PutandConvertEntry( aFmtStr, nCheckPos, nType,
nIndex, LANGUAGE_ENGLISH_US, eLangType, true);
}
pFormatter->GetOutputString( nNumber, nIndex, rRes, );
}
@@ -737,7 +737,7 @@ void SbxValue::Format( OUString& rRes, const OUString* pFmt
) const
if( floor( nNumber ) != nNumber )
{
aFmtStr = "H:MM:SS AM/PM";
-pFormatter->PutandConvertEntry( aFmtStr, nCheckPos,
nType, nIndex, LANGUAGE_ENGLISH, eLangType, true);
+pFormatter->PutandConvertEntry( aFmtStr, nCheckPos,
nType, nIndex, LANGUAGE_ENGLISH_US, eLangType, true);
OUString aTime;
pFormatter->GetOutputString( nNumber, nIndex, aTime,
);
rRes += " " + aTime;
@@ -747,7 +747,7 @@ void SbxValue::Format( OUString& rRes, const OUString* pFmt
) const
{
// long time only
aFmtStr = "H:MM:SS AM/PM";
-pFormatter->PutandConvertEntry( aFmtStr, nCheckPos, nType,
nIndex, LANGUAGE_ENGLISH, eLangType, true);
+pFormatter->PutandConvertEntry( aFmtStr, nCheckPos, nType,
nIndex, LANGUAGE_ENGLISH_US, eLangType, true);
pFormatter->GetOutputString( nNumber, nIndex, rRes,
);
}
}
@@ -783,7 +783,7 @@ void SbxValue::Format( OUString& rRes, const OUString* pFmt
) const
}
else
{
-pFormatter->PutandConvertEntry( aFmtStr, nCheckPos, nType,
nIndex, LANGUAGE_ENGLISH, eLangType, true);
+pFormatter->PutandConvertEntry( aFmtStr, nCheckPos, nType,
nIndex, LANGUAGE_ENGLISH_US, eLangType, true);
pFormatter->GetOutputString( nNumber, nIndex, rRes, );
}
[Libreoffice-bugs] [Bug 143818] Writer form fields are not accessible using only the keyboard [accessibility]
https://bugs.documentfoundation.org/show_bug.cgi?id=143818 --- Comment #1 from Christophe Strobbe --- I have now reproduced this issue on Windows 10, which suggests that this is not a Linux-only issue. I have reproduced the issue using LibreOffice 7.1.4.2 with the same results as under Linux. In addition, I have also reproduced the issue using OpenOffice.org Writer 3.3, again with the same results, which suggests that the issue was probably inherited from OpenOffice.org rather than being a regression. In each of these cases, I recreated the same document with the same form fields from scratch: a name field (plain text), a numeric field, a date field and a group box with option buttons (gender: male, female, other). Both under Linux and Windows, the form fields could not be tabbed into. When the mouse was used to put the cursor in the first text field, tabbing to the numeric field and the date field became possible, but the group box remained inaccessible. After selecting one of the radio buttons, tabbing between the group box and the other fields became possible. The behaviour was the same regardless of platform. The anchoring of the form fields (e.g. "To character" or "As character") did not make any difference. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143781] [META] Development- and code-related bug reports
https://bugs.documentfoundation.org/show_bug.cgi?id=143781 Aron Budea changed: What|Removed |Added Depends on||39674 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=39674 [Bug 39674] find / fix all German spellings in internal APIs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 39674] find / fix all German spellings in internal APIs
https://bugs.documentfoundation.org/show_bug.cgi?id=39674 Aron Budea changed: What|Removed |Added Hardware|Other |All Blocks||143781 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143781 [Bug 143781] [META] Development- and code-related bug reports -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143819] Undo doesn't restore image anchor position
https://bugs.documentfoundation.org/show_bug.cgi?id=143819 Telesto changed: What|Removed |Added Keywords||bibisectRequest, regression Version|7.3.0.0 alpha0+ Master |4.4.0.3 release --- Comment #2 from Telesto --- Also in Version: 6.1.0.0.beta2+ Build ID: 22c451df33b733440f24c1feb6380d31240d55e6 CPU threads: 4; OS: Windows 6.3; UI render: GL; Locale: nl-NL (nl_NL); Calc: CL and in Versie: 4.4.7.2 Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600 Locale: nl_NL fine in Version: 4.3.0.4 Build ID: 62ad5818884a2fc2e5780dd45466868d41009ec0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143819] Undo doesn't restore image anchor position
https://bugs.documentfoundation.org/show_bug.cgi?id=143819 --- Comment #1 from Telesto --- Created attachment 174198 --> https://bugs.documentfoundation.org/attachment.cgi?id=174198=edit Example file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143819] New: Undo doesn't restore image anchor position
https://bugs.documentfoundation.org/show_bug.cgi?id=143819 Bug ID: 143819 Summary: Undo doesn't restore image anchor position Product: LibreOffice Version: 7.3.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tele...@surfxs.nl Description: Undo doesn't restore image anchor position Steps to Reproduce: 1. Open the attached file 2. Place cursor after the yellow marked text (so after "current") 3. Press and hold backspace. Say until 'setup' in line above 4. Press and hold undo Actual Results: Image has gone up & anchor is at 'setup' after undo Expected Results: Should be back to area with yellow marking Reproducible: Always User Profile Reset: No Additional Info: Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 36efb384a66b6dd645e0ae80fd7df68370a9dc8b CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143818] New: Writer form fields are not accessible using only the keyboard [accessibility]
https://bugs.documentfoundation.org/show_bug.cgi?id=143818 Bug ID: 143818 Summary: Writer form fields are not accessible using only the keyboard [accessibility] Product: LibreOffice Version: 7.1.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: c_strobbe-...@yahoo.co.uk Description: Form fields are not accessible using only the keyboard; they cannot be reached using the TAB key (or any other key, apparently) and therefore cannot be filled in. Steps to Reproduce: 1. In a Writer document, add a few form fields, such as a text entry field (e.g. for the user's name), a numeric field, a date field and a set of option buttons. 2. Go to File -> Properties -> Security and check the option "Open file read-only". This makes sure that users just fill in the field instead of modifying the form (as explained in Chapter 15 of the LibreOffice Writer Guide). 3. Save the file, close it and reopen it. 4. Without using the mouse, try to reach any of the form fields using the TAB key; none of the fields receives focus. Move around the document using the arrow keys; the cursor moves through any text above and below the fields and through the labels, but the form fields are ignored. 5. When using the mouse to put the focus into the first field, it becomes possible to TAB to some of the other fields (the numeric field and the date field) but not the set of option buttons / radio buttons). Actual Results: When using only the TAB key, none of the form fields receive focus; it is impossible to fill the form without using the mouse to put the cursor into the first field or on the set of radio buttons. Expected Results: Using the TAB key should cycle the focus through the form fields in the order in which they are arranged in the document. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.3.2 / LibreOffice Community Build ID: 10(Build:2) CPU threads: 8; OS: Linux 5.5; UI render: default; VCL: kf5 Locale: en-GB (en_GB.utf8); UI: en-GB Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 60469] : Wrong "formulas formating" from excel 2010
https://bugs.documentfoundation.org/show_bug.cgi?id=60469 Aron Budea changed: What|Removed |Added OS|Windows (All) |All Hardware|Other |All Version|unspecified |Inherited From OOo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136610] Clone Button does not exist in LO Draw's Tabbed Interface
https://bugs.documentfoundation.org/show_bug.cgi?id=136610 --- Comment #5 from Commit Notification --- Rafael Lima committed a patch related to this issue. It has been pushed to "libreoffice-7-2": https://git.libreoffice.org/core/commit/3bec2da07a29029489257028adf77e52ad168906 tdf#136610 Add Clone/Clear Direct Format buttons to LO Draw tabbed interface It will be available in 7.2.1. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136610] Clone Button does not exist in LO Draw's Tabbed Interface
https://bugs.documentfoundation.org/show_bug.cgi?id=136610 Commit Notification changed: What|Removed |Added Whiteboard|target:7.3.0|target:7.3.0 target:7.2.1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-2' - sd/uiconfig
sd/uiconfig/sdraw/ui/notebookbar.ui | 165 +++- 1 file changed, 163 insertions(+), 2 deletions(-) New commits: commit 3bec2da07a29029489257028adf77e52ad168906 Author: Rafael Lima AuthorDate: Mon Jul 19 23:58:35 2021 +0200 Commit: Andreas Kainz CommitDate: Wed Aug 11 00:20:15 2021 +0200 tdf#136610 Add Clone/Clear Direct Format buttons to LO Draw tabbed interface Currently LO Draw only shows the "Clone" and "Clear Direct Format" buttons in the tabbed interface when a text object is selected (in the Text tab). With this patch, LO Draw will now show these buttons in the "Draw" tab when shapes are selected, as well as in the Home tab (as it is shown in Impress). Change-Id: I9acf577cc5322d43c18acc366788a5eadda67ff6 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/119183 Tested-by: Jenkins Tested-by: Andreas Kainz Reviewed-by: Andreas Kainz (cherry picked from commit 73fc697d5aac06938cc78f51b4e0d6f3d615447c) Reviewed-on: https://gerrit.libreoffice.org/c/core/+/120249 diff --git a/sd/uiconfig/sdraw/ui/notebookbar.ui b/sd/uiconfig/sdraw/ui/notebookbar.ui index c65aced89a03..4c1b5ea4d0aa 100644 --- a/sd/uiconfig/sdraw/ui/notebookbar.ui +++ b/sd/uiconfig/sdraw/ui/notebookbar.ui @@ -3359,6 +3359,102 @@ 0 + + +True +False +center +True + + +True +False +5 +5 +vertical + + +False +True +5 +0 + + + + +True +False +center +vertical + + +True +True +center +True +both-horiz +False + + +True +False +.uno:FormatPaintbrush + + +False +True + + + + +False +True +0 + + + + +True +True +center +True +both-horiz +False + + +True +False +.uno:SetDefault + + +False +True + + + + +False +True +1 + + + + +False +True +1 + + + ++ + + +False +True +2 + + True @@ -8437,7 +8533,7 @@ both-horiz False - +
[Libreoffice-bugs] [Bug 136808] getting "please install hyphenation package for locale en-US" every time I start Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=136808 Eike Rathke changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120883] [META] Hyphenation bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=120883 Bug 120883 depends on bug 136808, which changed state. Bug 136808 Summary: getting "please install hyphenation package for locale en-US" every time I start Writer https://bugs.documentfoundation.org/show_bug.cgi?id=136808 What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136808] getting "please install hyphenation package for locale en-US" every time I start Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=136808 Eike Rathke changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|UNCONFIRMED --- Comment #5 from Eike Rathke --- Maybe not a duplicate of bug 137742 that is about GDocs documents having a language tag of only 'en'. If the original bug submitter could answer the above question whether it's about opening Google Docs documents? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143781] [META] Development- and code-related bug reports
https://bugs.documentfoundation.org/show_bug.cgi?id=143781 Aron Budea changed: What|Removed |Added Depends on||139734 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=139734 [Bug 139734] Drop redundant asserts after MacrosTest::loadFromDesktop -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139734] Drop redundant asserts after MacrosTest::loadFromDesktop
https://bugs.documentfoundation.org/show_bug.cgi?id=139734 Aron Budea changed: What|Removed |Added Blocks||143781 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143781 [Bug 143781] [META] Development- and code-related bug reports -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136809] getting "please install hyphenation package for locale en-US" every time I start Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=136809 Eike Rathke changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136808] getting "please install hyphenation package for locale en-US" every time I start Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=136808 --- Comment #4 from Eike Rathke --- *** Bug 136809 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136809] getting "please install hyphenation package for locale en-US" every time I start Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=136809 Eike Rathke changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Eike Rathke --- But actually of 136808 ... *** This bug has been marked as a duplicate of bug 136808 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 60167] Database ranges don't get saved when saving to Excel 97/XP/2003
https://bugs.documentfoundation.org/show_bug.cgi?id=60167 Aron Budea changed: What|Removed |Added Hardware|Other |All Version|unspecified |Inherited From OOo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136809] getting "please install hyphenation package for locale en-US" every time I start Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=136809 Eike Rathke changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE |--- --- Comment #3 from Eike Rathke --- Not a duplicate of bug 137742 that is about GDocs documents having a language tag of only 'en'. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143696] Development Tools - Minor glitches and improvements
https://bugs.documentfoundation.org/show_bug.cgi?id=143696 --- Comment #4 from Rafael Lima --- (In reply to Tomaz Vajngerl from comment #3) > 2) The "page n" naming is not part of DevTools, but uses the "Name" property > of the Slide/Page object and for some reason the name is "page n" and not > "slide n" (most likely because the object is SdDrawPage and we don't have a > special case when it represents slides. I thought that might be the case. Thanks for the info. > 3) Renamed... to "Name", which is more consistent how other columns are > named. I liked the choice for "Name" to use in this column. However, the "Methods" tab has a new column named "Method" instead of "Name". How about changing this "Method" column to "Name" as well? > 4) Right, the problem is the order is alphabetical, so the indices should > prepend 0 to be able to sort them correctly. I thought they were sorted using integer indices. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143817] Search Commands deleting contents in Writer when command applied to selected text
https://bugs.documentfoundation.org/show_bug.cgi?id=143817 Rafael Lima changed: What|Removed |Added CC||qui...@gmail.com --- Comment #1 from Rafael Lima --- Tomaz, I found a possible bug in Search Commands. Could you please take a look? Thanks! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143817] New: Search Commands deleting contents in Writer when command applied to selected text
https://bugs.documentfoundation.org/show_bug.cgi?id=143817 Bug ID: 143817 Summary: Search Commands deleting contents in Writer when command applied to selected text Product: LibreOffice Version: 7.2.0.0.beta1+ Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rafael.palma.l...@gmail.com Created attachment 174197 --> https://bugs.documentfoundation.org/attachment.cgi?id=174197=edit Video showing the bug I was running some tests while writing the help page for the "Search Commands" hud and came across a bug when it is used in Writer (see attached video). Steps to reproduce: 1) Open Writer and enter some text 2) Select the text 3) Choose a command to apply to the selected text (e.g. "Bold" or "Italic") 4) Press "Enter" 5) Instead of applying the command to the selected text, the text disappears as though when you press Enter on any selected text However, the expected outcome would be to have the command applied to the selected text without deleting it. The video was recorded in KDE but I tested this issue both in KDE and Windows using the latest alpha on two different PCs. Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: b2130ad3fda841c68a0436fbddf29bcedede0af5 CPU threads: 16; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-08-09_13:03:07 Calc: threaded Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: f98796df322d89912070c8e431c5f6d1283f CPU threads: 12; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win Locale: pt-BR (pt_BR); UI: pt-BR Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142760] FILEOPEN: DOC: Document has 21 pages instead of 6
https://bugs.documentfoundation.org/show_bug.cgi?id=142760 --- Comment #5 from Xisco Faulí --- *** Bug 142757 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142757] FILEOPEN: DOC/DOCX: document has more pages and hangs at import time
https://bugs.documentfoundation.org/show_bug.cgi?id=142757 Xisco Faulí changed: What|Removed |Added Resolution|WORKSFORME |DUPLICATE --- Comment #11 from Xisco Faulí --- (In reply to Dániel Arató (NISZ) from comment #10) > (In reply to Justin L from comment #9) > > However, that commit just triggered an existing layout condition that we > > can't handle. So the revert just masks this again. Oh well, there are so > > many crash/freeze bug reports that there isn't much point in leaving this > > one open. And no point for adding a unit test because there has not been a > > true fix. > > Should we set this bug to WONTFIX perhaps? Actually there are two problem here, the hang and the increase in the number of pages. The hang might be a consequence of the second problem, so let's close this as a duplicate of bug 142760, where the problem of the number of pages was first reported *** This bug has been marked as a duplicate of bug 142760 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142760] FILEOPEN: DOC: Document has 21 pages instead of 6
https://bugs.documentfoundation.org/show_bug.cgi?id=142760 Xisco Faulí changed: What|Removed |Added Resolution|DUPLICATE |FIXED --- Comment #4 from Xisco Faulí --- This got fixed by https://git.libreoffice.org/core/+/d03aaef3dcb5d142955457ae9b8ca4469cfafa38%5E%21 Closing as RESOLVED FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139736] Images and frames in header violate PDF/UA
https://bugs.documentfoundation.org/show_bug.cgi?id=139736 Christophe Strobbe changed: What|Removed |Added CC||c_strobbe-...@yahoo.co.uk --- Comment #4 from Christophe Strobbe --- Adding some background information from the PDF Association's "Tagged PDF Best Practice Guide: Syntax" (Version 1.0, June 2019): Subchapter 3.7.1: Header and footer content Page headers and footers are usually placed automatically as a function of pagination. As such this content is not part of the reading-order of the document and is not considered to be “real content. Subchapter 3.7.2: Page numbers Page numbers must be marked as artifacts in marked-content sequences with a property list entry Pagination (see ISO 32000-1, Table 330 – Property list entries for artifacts) property). Accessible page enumeration is enabled through use of the Page Labels (ISO 32000-1, 12.4.2). It is semantically appropriate to have Page Label values match the visible page number. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141659] FILESAVE: DOC: Shape disappears after RT
https://bugs.documentfoundation.org/show_bug.cgi?id=141659 Aron Budea changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||0798 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103152] [META] Writer image bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103152 Aron Budea changed: What|Removed |Added Depends on||140798 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=140798 [Bug 140798] Image order not respected when copy/pasting images (if not saved before) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108843] [META] Clipboard bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108843 Aron Budea changed: What|Removed |Added Depends on||140798 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=140798 [Bug 140798] Image order not respected when copy/pasting images (if not saved before) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140798] Image order not respected when copy/pasting images (if not saved before)
https://bugs.documentfoundation.org/show_bug.cgi?id=140798 Aron Budea changed: What|Removed |Added CC||ba...@caesar.elte.hu See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||1659 Blocks||108843, 103152 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103152 [Bug 103152] [META] Writer image bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=108843 [Bug 108843] [META] Clipboard bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
