[Libreoffice-commits] core.git: sw/inc sw/source sw/uiconfig
sw/inc/AccessibilityCheckStrings.hrc |2
sw/source/uibase/sidebar/A11yCheckIssuesPanel.cxx | 164 +-
sw/source/uibase/sidebar/A11yCheckIssuesPanel.hxx | 29 ++
sw/uiconfig/swriter/ui/a11ycheckissuespanel.ui| 251 +-
4 files changed, 432 insertions(+), 14 deletions(-)
New commits:
commit ee8405d7567c35ae240e014fe1da289b4bb1abe2
Author: Samuel Mehrbrodt
AuthorDate: Mon Jun 5 14:20:37 2023 +0200
Commit: Samuel Mehrbrodt
CommitDate: Thu Jun 8 07:56:16 2023 +0200
tdf#155505 Group issues by type in a11y sidebar panel
Change-Id: I87349e9d3f5680751a91264e055e4579c97fa93e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152617
Tested-by: Jenkins
Reviewed-by: Samuel Mehrbrodt
diff --git a/sw/inc/AccessibilityCheckStrings.hrc
b/sw/inc/AccessibilityCheckStrings.hrc
index cb461b1013f8..12e2e1fa2b8d 100644
--- a/sw/inc/AccessibilityCheckStrings.hrc
+++ b/sw/inc/AccessibilityCheckStrings.hrc
@@ -13,7 +13,7 @@
#define NC_(Context, String) TranslateId(Context, reinterpret_cast(u8##String))
-#define STR_NO_ALT NC_("STR_NO_ALT", "No alt or
description text for graphic “%OBJECT_NAME%”.")
+#define STR_NO_ALT NC_("STR_NO_ALT", "%OBJECT_NAME%")
#define STR_TABLE_MERGE_SPLIT NC_("STR_TABLE_MERGE_SPLIT", "Table
“%OBJECT_NAME%” contains merges or splits.")
#define STR_FAKE_NUMBERING NC_("STR_FAKE_NUMBERING", "Simulated
numbering “%NUMBERING%”.")
#define STR_HYPERLINK_TEXT_IS_LINK NC_("STR_HYPERLINK_TEXT_IS_LINK",
"Hyperlink text is the same as the link address “%LINK%”.")
diff --git a/sw/source/uibase/sidebar/A11yCheckIssuesPanel.cxx
b/sw/source/uibase/sidebar/A11yCheckIssuesPanel.cxx
index c0c8595408c6..1728ed58e266 100644
--- a/sw/source/uibase/sidebar/A11yCheckIssuesPanel.cxx
+++ b/sw/source/uibase/sidebar/A11yCheckIssuesPanel.cxx
@@ -69,7 +69,24 @@ std::unique_ptr
A11yCheckIssuesPanel::Create(weld::Widget* pParent,
A11yCheckIssuesPanel::A11yCheckIssuesPanel(weld::Widget* pParent, SfxBindings*
pBindings)
: PanelLayout(pParent, "A11yCheckIssuesPanel",
"modules/swriter/ui/a11ycheckissuespanel.ui")
-, m_xAccessibilityCheckBox(m_xBuilder->weld_box("accessibilityCheckBox"))
+, m_xExpanderDocument(m_xBuilder->weld_expander("expand_document"))
+, m_xExpanderStyles(m_xBuilder->weld_expander("expand_styles"))
+, m_xExpanderNoAlt(m_xBuilder->weld_expander("expand_no_alt"))
+, m_xExpanderTable(m_xBuilder->weld_expander("expand_table"))
+, m_xExpanderFormatting(m_xBuilder->weld_expander("expand_formatting"))
+, m_xExpanderHyperlink(m_xBuilder->weld_expander("expand_hyperlink"))
+, m_xExpanderFakes(m_xBuilder->weld_expander("expand_fakes"))
+, m_xExpanderNumbering(m_xBuilder->weld_expander("expand_numbering"))
+, m_xExpanderOther(m_xBuilder->weld_expander("expand_other"))
+, m_xBoxDocument(m_xBuilder->weld_box("box_document"))
+, m_xBoxStyles(m_xBuilder->weld_box("box_styles"))
+, m_xBoxNoAlt(m_xBuilder->weld_box("box_no_alt"))
+, m_xBoxTable(m_xBuilder->weld_box("box_table"))
+, m_xBoxFormatting(m_xBuilder->weld_box("box_formatting"))
+, m_xBoxHyperlink(m_xBuilder->weld_box("box_hyperlink"))
+, m_xBoxFakes(m_xBuilder->weld_box("box_fakes"))
+, m_xBoxNumbering(m_xBuilder->weld_box("box_numbering"))
+, m_xBoxOther(m_xBuilder->weld_box("box_other"))
, mpBindings(pBindings)
, mpDoc(nullptr)
, maA11yCheckController(FN_STAT_ACCESSIBILITY_CHECK, *pBindings, *this)
@@ -108,7 +125,24 @@ void A11yCheckIssuesPanel::ImplDestroy()
batch->commit();
mpBindings->Invalidate(SID_ACCESSIBILITY_CHECK_ONLINE);
}
-m_xAccessibilityCheckBox.reset();
+m_xExpanderDocument.reset();
+m_xExpanderStyles.reset();
+m_xExpanderNoAlt.reset();
+m_xExpanderTable.reset();
+m_xExpanderFormatting.reset();
+m_xExpanderHyperlink.reset();
+m_xExpanderFakes.reset();
+m_xExpanderNumbering.reset();
+m_xExpanderOther.reset();
+m_xBoxDocument.reset();
+m_xBoxStyles.reset();
+m_xBoxNoAlt.reset();
+m_xBoxTable.reset();
+m_xBoxFormatting.reset();
+m_xBoxHyperlink.reset();
+m_xBoxFakes.reset();
+m_xBoxNumbering.reset();
+m_xBoxOther.reset();
}
A11yCheckIssuesPanel::~A11yCheckIssuesPanel() {
suppress_fun_call_w_exception(ImplDestroy()); }
@@ -122,23 +156,133 @@ void A11yCheckIssuesPanel::populateIssues()
m_aIssueCollection = aCheck.getIssueCollection();
// Remove old issue widgets
-for (auto const& xEntry : m_aAccessibilityCheckEntries)
-m_xAccessibilityCheckBox->move(xEntry->get_widget(), nullptr);
+for (auto const& xEntry : m_aDocumentEntries)
+m_xBoxDocument->move(xEntry->get_widget(), nullptr);
+for (auto const& xEntry : m_aStylesEntries)
+m_xBoxStyles->move(xEntry->get_widget(), nullptr);
+for (auto const& xEntry : m_aNoAltEntries)
+
[Libreoffice-bugs] [Bug 152432] File > Recent Recordings displays empty list when saving document
https://bugs.documentfoundation.org/show_bug.cgi?id=152432 --- Comment #5 from Mark C --- Okay. I did the Help>Menu>Restart in safe mode. I followed the steps I documented. This time I used the ppt equivalent (I think you call it Draw). I observed EXACTLY the same issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: 2 commits - include/docmodel oox/qa sw/CppunitTest_sw_ooxml_theme_export.mk sw/Library_msword.mk sw/Module_sw.mk sw/qa sw/source writerfilter/source
include/docmodel/color/ComplexColor.hxx |1
include/docmodel/theme/ThemeColorType.hxx |7
oox/qa/unit/export.cxx |4
sw/CppunitTest_sw_ooxml_theme_export.mk | 53 +
sw/Library_msword.mk|1
sw/Module_sw.mk |1
sw/qa/core/theme/ThemeTest.cxx | 12
sw/qa/extras/ooxmlexport/data/Test_ThemePortionLevel_CharColor.docx |binary
sw/qa/extras/ooxmlexport/data/Test_ThemePortionLevel_CharColor.fodt | 420
++
sw/qa/extras/ooxmlexport/ooxml_ThemeExport.cxx | 56 +
sw/source/filter/ww8/docxattributeoutput.cxx| 119 ++
sw/source/filter/ww8/docxexport.cxx | 37
writerfilter/source/dmapper/DomainMapper.cxx|8
writerfilter/source/dmapper/TDefTableHandler.cxx| 16
writerfilter/source/dmapper/TDefTableHandler.hxx|1
15 files changed, 679 insertions(+), 57 deletions(-)
New commits:
commit fcccb8f8d67dd7deec772746661d2d6dff2c14a3
Author: Tomaž Vajngerl
AuthorDate: Thu Jun 8 12:37:21 2023 +0900
Commit: Tomaž Vajngerl
CommitDate: Thu Jun 8 07:45:21 2023 +0200
sw: use ThemeExport instead of grab bag
Change-Id: I68d300d58aaa1e5da374a8ddea4ff37e9a1e1819
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152723
Tested-by: Jenkins
Reviewed-by: Tomaž Vajngerl
diff --git a/sw/source/filter/ww8/docxexport.cxx
b/sw/source/filter/ww8/docxexport.cxx
index af9979a1d660..f7258952a541 100644
--- a/sw/source/filter/ww8/docxexport.cxx
+++ b/sw/source/filter/ww8/docxexport.cxx
@@ -48,11 +48,14 @@
#include
#include
#include
+#include
#include
#include
#include
#include
+#include
+
#include
#include
#include
@@ -62,6 +65,7 @@
#include
#include
#include
+#include
#include
#include
#include "wrtww8.hxx"
@@ -74,6 +78,7 @@
#include
#include
#include
+#include
#include
#include
@@ -1466,35 +1471,15 @@ void DocxExport::WriteSettings()
void DocxExport::WriteTheme()
{
-uno::Reference< beans::XPropertySet > xPropSet(
m_rDoc.GetDocShell()->GetBaseModel(), uno::UNO_QUERY_THROW );
-
-uno::Reference< beans::XPropertySetInfo > xPropSetInfo =
xPropSet->getPropertySetInfo();
-OUString aName = UNO_NAME_MISC_OBJ_INTEROPGRABBAG;
-if ( !xPropSetInfo->hasPropertyByName( aName ) )
+SdrPage* pPage =
m_rDoc.getIDocumentDrawModelAccess().GetDrawModel()->GetPage(0);
+auto const& pTheme = pPage->getSdrPageProperties().GetTheme();
+if (!pTheme)
return;
-uno::Reference themeDom;
-uno::Sequence< beans::PropertyValue > propList;
-xPropSet->getPropertyValue( aName ) >>= propList;
-auto pProp = std::find_if(std::cbegin(propList), std::cend(propList),
-[](const beans::PropertyValue& rProp) { return rProp.Name ==
"OOXTheme"; });
-if (pProp != std::cend(propList))
-pProp->Value >>= themeDom;
-
-// no theme dom to write
-if ( !themeDom.is() )
-return;
-
-m_rFilter.addRelation( m_pDocumentFS->getOutputStream(),
-oox::getRelationship(Relationship::THEME),
-u"theme/theme1.xml" );
+m_rFilter.addRelation(m_pDocumentFS->getOutputStream(),
oox::getRelationship(Relationship::THEME), u"theme/theme1.xml" );
-uno::Reference< xml::sax::XSAXSerializable > serializer( themeDom,
uno::UNO_QUERY );
-uno::Reference< xml::sax::XWriter > writer = xml::sax::Writer::create(
comphelper::getProcessComponentContext() );
-writer->setOutputStream( GetFilter().openFragmentStream(
"word/theme/theme1.xml",
-"application/vnd.openxmlformats-officedocument.theme+xml" ) );
-serializer->serialize( uno::Reference< xml::sax::XDocumentHandler >(
writer, uno::UNO_QUERY_THROW ),
-uno::Sequence< beans::StringPair >() );
+oox::ThemeExport aThemeExport(_rFilter, oox::drawingml::DOCUMENT_DOCX);
+aThemeExport.write(u"word/theme/theme1.xml", *pTheme);
}
// See OOXMLDocumentImpl::resolveGlossaryStream
commit 17105fc44bceea61ff8876686cc1362aa787ead2
Author: Tomaž Vajngerl
AuthorDate: Wed Jun 7 23:29:05 2023 +0900
Commit: Tomaž Vajngerl
CommitDate: Thu Jun 8 07:45:13 2023 +0200
sw: remove char color GrabBag and fix export, fix tint/shade calc.
Don't store values from grab bag when exporting character theme
colors and tint/shade values. The values could be wrong now and
aren't needed anyway as we support the values in the model.
Add proper export support for char color theme information with
correct conversion of values into tint/shade values in 0-255
inverted interval.
This also fixes the import of tint/shade values whcih calculation
was slightly off. We
[Libreoffice-bugs] [Bug 155726] Calc - change the location of the 'Sort by Color' option in the automatic filter menu
https://bugs.documentfoundation.org/show_bug.cgi?id=155726 --- Comment #1 from kabilo --- Created attachment 187775 --> https://bugs.documentfoundation.org/attachment.cgi?id=187775=edit change the location of the Sort by Color option -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155726] New: Calc - change the location of the 'Sort by Color' option in the automatic filter menu
https://bugs.documentfoundation.org/show_bug.cgi?id=155726 Bug ID: 155726 Summary: Calc - change the location of the 'Sort by Color' option in the automatic filter menu Product: LibreOffice Version: 7.6.0.0 alpha1+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: minute.visit...@gmail.com Description: change the location of the 'Sort by Color' option in the automatic filter menu. The option is located in the filter group. Steps to Reproduce: 1. show auto filter menu Actual Results: The 'Sort by Color' option is located in the filter group. Expected Results: The 'Sort by Color' option should be displayed in the sort group Reproducible: Always User Profile Reset: No Additional Info: -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - sd/inc sd/source
sd/inc/sdgrffilter.hxx |1
sd/source/filter/grf/sdgrffilter.cxx | 85 +--
2 files changed, 54 insertions(+), 32 deletions(-)
New commits:
commit 844a97295444b30147ac484166353fba21c582c0
Author: rash419
AuthorDate: Wed Jun 7 11:25:00 2023 +0530
Commit: Tomaž Vajngerl
CommitDate: Thu Jun 8 07:08:34 2023 +0200
tdf#155444 added support for multi image tiff file
Signed-off-by: rash419
Change-Id: I188aebae9c853e87dc50ffda5b7d88228559a7c7
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152693
Tested-by: Jenkins CollaboraOffice
Reviewed-by: Tomaž Vajngerl
diff --git a/sd/inc/sdgrffilter.hxx b/sd/inc/sdgrffilter.hxx
index dc9027f94ca3..28ce9de6dd29 100644
--- a/sd/inc/sdgrffilter.hxx
+++ b/sd/inc/sdgrffilter.hxx
@@ -34,6 +34,7 @@ public:
bool Export() override;
static void HandleGraphicFilterError(ErrCode nFilterError, ErrCode
nStreamError);
+static void InsertSdrGrafObj(Graphic pGraphic, SdPage* pPage);
};
/* vim:set shiftwidth=4 softtabstop=4 expandtab: */
diff --git a/sd/source/filter/grf/sdgrffilter.cxx
b/sd/source/filter/grf/sdgrffilter.cxx
index 71f9221ab055..693f297a19c6 100644
--- a/sd/source/filter/grf/sdgrffilter.cxx
+++ b/sd/source/filter/grf/sdgrffilter.cxx
@@ -156,50 +156,71 @@ bool SdGRFFilter::Import()
if( mrDocument.GetPageCount() == 0 )
mrDocument.CreateFirstPages();
-SdPage* pPage = mrDocument.GetSdPage( 0, PageKind::Standard );
-Point aPos;
-SizeaPagSize( pPage->GetSize() );
-SizeaGrfSize( OutputDevice::LogicToLogic(
aGraphic.GetPrefSize(),
-aGraphic.GetPrefMapMode(),
MapMode(MapUnit::Map100thMM)));
-
-aPagSize.AdjustWidth( -(pPage->GetLeftBorder() +
pPage->GetRightBorder()) );
-aPagSize.AdjustHeight( -(pPage->GetUpperBorder() +
pPage->GetLowerBorder()) );
-
-// scale to fit page
-if ( ( ( aGrfSize.Height() > aPagSize.Height() ) || ( aGrfSize.Width()
> aPagSize.Width() ) ) &&
-aGrfSize.Height() && aPagSize.Height() )
+GfxLink aGfxLink = aGraphic.GetGfxLink();
+if( aGfxLink.GetType() == GfxLinkType::NativeTif &&
aGraphic.IsAnimated() )
{
-double fGrfWH = static_cast(aGrfSize.Width()) /
aGrfSize.Height();
-double fWinWH = static_cast(aPagSize.Width()) /
aPagSize.Height();
-
-// adjust graphic to page size (scales)
-if( fGrfWH < fWinWH )
+Animation aAnim( aGraphic.GetAnimation() );
+const auto nImages = aAnim.Count();
+for (size_t i = 0; i < nImages - 1; ++i)
{
-aGrfSize.setWidth( static_cast( aPagSize.Height()
* fGrfWH ) );
-aGrfSize.setHeight( aPagSize.Height() );
+mrDocument.DuplicatePage(0);
}
-else if( fGrfWH > 0.F )
+for (size_t nPageIndex = 0; nPageIndex < nImages; ++nPageIndex)
{
-aGrfSize.setWidth( aPagSize.Width() );
-aGrfSize.setHeight( static_cast( aPagSize.Width()
/ fGrfWH ) );
+Graphic pGraphic = aAnim.Get(nPageIndex).maBitmapEx;
+SdPage* pPage = mrDocument.GetSdPage(nPageIndex,
PageKind::Standard);
+InsertSdrGrafObj(pGraphic, pPage);
}
}
-
-// set output rectangle for graphic
-aPos.setX( ( ( aPagSize.Width() - aGrfSize.Width() ) >> 1 ) +
pPage->GetLeftBorder() );
-aPos.setY( ( ( aPagSize.Height() - aGrfSize.Height() ) >> 1 ) +
pPage->GetUpperBorder() );
-
-pPage->InsertObject(
-new SdrGrafObj(
-pPage->getSdrModelFromSdrPage(),
-aGraphic,
-::tools::Rectangle(aPos, aGrfSize)));
+else
+{
+SdPage* pPage = mrDocument.GetSdPage(0, PageKind::Standard);
+InsertSdrGrafObj(aGraphic, pPage);
+}
bRet = true;
}
return bRet;
}
+void SdGRFFilter::InsertSdrGrafObj(Graphic pGraphic, SdPage* pPage)
+{
+Point aPos;
+Size aPagSize(pPage->GetSize());
+Size aGrfSize(OutputDevice::LogicToLogic(pGraphic.GetPrefSize(),
pGraphic.GetPrefMapMode(),
+ MapMode(MapUnit::Map100thMM)));
+
+aPagSize.AdjustWidth(-(pPage->GetLeftBorder() + pPage->GetRightBorder()));
+aPagSize.AdjustHeight(-(pPage->GetUpperBorder() +
pPage->GetLowerBorder()));
+
+// scale to fit page
+if (((aGrfSize.Height() > aPagSize.Height()) || (aGrfSize.Width() >
aPagSize.Width()))
+&& aGrfSize.Height() && aPagSize.Height())
+{
+double fGrfWH = static_cast(aGrfSize.Width()) /
aGrfSize.Height();
+double fWinWH = static_cast(aPagSize.Width()) /
aPagSize.Height();
+
+// adjust graphic to page size (scales)
+if (fGrfWH < fWinWH)
+{
+
[Libreoffice-bugs] [Bug 154583] Split button Color Picker regression, attempting a color pick now opens the Line or Area object dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=154583 Aron Budea changed: What|Removed |Added Whiteboard||target:24.2.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136991] Open RTF with colored text slower from 4.1 and 4.2
https://bugs.documentfoundation.org/show_bug.cgi?id=136991 --- Comment #22 from BogdanB --- Telesto, Pit Hauge, can you test again this bug using 7.6? Maybe even using Mac? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 33687] FORMATTING: index text (TOC) does not flow in linked frames
https://bugs.documentfoundation.org/show_bug.cgi?id=33687 --- Comment #18 from markmor --- Means that Still reproduces on windows 7/64 & Version: 4.4.1.1 https://dynamonsworld.com I will try it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155476] 'Store on server' garbles filenames from unixoid sources (Linux & probably MacOSX, xxxBSD)
https://bugs.documentfoundation.org/show_bug.cgi?id=155476 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 155477] outline export to xhtml fails to preserve indentation
https://bugs.documentfoundation.org/show_bug.cgi?id=155477 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 155427] filters.add 423 property not found
https://bugs.documentfoundation.org/show_bug.cgi?id=155427 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 155696] Clicking on selected object no longer enters rotation mode
https://bugs.documentfoundation.org/show_bug.cgi?id=155696 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155451] LibreOffice splash screen should remain active until main LibreOffice window becomes usable
https://bugs.documentfoundation.org/show_bug.cgi?id=155451 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 155696] Clicking on selected object no longer enters rotation mode
https://bugs.documentfoundation.org/show_bug.cgi?id=155696 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152433] wrong cross-reference
https://bugs.documentfoundation.org/show_bug.cgi?id=152433 --- Comment #2 from QA Administrators --- Dear Geletina, 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 147038] Drag & drop behaviour is off after putting an image to different page & restoring it with undo
https://bugs.documentfoundation.org/show_bug.cgi?id=147038 --- Comment #4 from QA Administrators --- Dear Telesto, 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 152442] Writer:: Navigator can't be pinned to the left
https://bugs.documentfoundation.org/show_bug.cgi?id=152442 --- Comment #2 from QA Administrators --- Dear pulsar14, 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 152432] File > Recent Recordings displays empty list when saving document
https://bugs.documentfoundation.org/show_bug.cgi?id=152432 --- Comment #4 from QA Administrators --- Dear Mark C, 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 147036] Inconsistency deleting to character anchors in document with backspace/delete
https://bugs.documentfoundation.org/show_bug.cgi?id=147036 --- Comment #7 from QA Administrators --- Dear Telesto, 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 61950] Change Presentation Minimizer and Report Builder from bundled extensions to plain code
https://bugs.documentfoundation.org/show_bug.cgi?id=61950 --- Comment #39 from QA Administrators --- Dear Stephan Bergmann, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142581] Insert row in impress creates a odd row height distribution
https://bugs.documentfoundation.org/show_bug.cgi?id=142581 --- Comment #3 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142425] Page flow after hiding track changes differently between ODT & exported DOCX and DOC
https://bugs.documentfoundation.org/show_bug.cgi?id=142425 --- Comment #5 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130697] Print preview of SVG images rendered pixelated (macOS-only) and crash with LO from master branch
https://bugs.documentfoundation.org/show_bug.cgi?id=130697 --- Comment #10 from QA Administrators --- Dear Thorsten Wagner, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117876] [EXPORT] Bad export to EPS
https://bugs.documentfoundation.org/show_bug.cgi?id=117876 --- Comment #6 from QA Administrators --- Dear Olivier Hallot, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117510] Firebird: Migration: Data unavailable when migration is run against HSQL ODB opened in Beamer (from Writer or Calc)
https://bugs.documentfoundation.org/show_bug.cgi?id=117510 --- Comment #9 from QA Administrators --- Dear Drew Jensen, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113029] EDITING: AutoInput doesn't recognise RC references and autocompletes with a formula
https://bugs.documentfoundation.org/show_bug.cgi?id=113029 --- Comment #5 from QA Administrators --- Dear John Russell, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155725] spaces at end of lines don't appear on screen
https://bugs.documentfoundation.org/show_bug.cgi?id=155725 --- Comment #1 from Telesto --- Sounds like bug 104683. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 68997] FILEOPEN Equation: Import from Word2010 not correctly rendered
https://bugs.documentfoundation.org/show_bug.cgi?id=68997 Justin L changed: What|Removed |Added Hardware|Other |All Summary|FILEOPEN: Import from |FILEOPEN Equation: Import |Word2010 not correctly |from Word2010 not correctly |rendered|rendered -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154583] Split button Color Picker regression, attempting a color pick now opens the Line or Area object dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=154583 Tomaz Vajngerl changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #19 from Tomaz Vajngerl --- Fixed with [1].. I put the duplicate bug number in the git comment by mistake. [1] https://gerrit.libreoffice.org/c/core/+/152713 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 85184] [META] Color picker toolbar, dialog and sidebar drop-down widget bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=85184 Bug 85184 depends on bug 154583, which changed state. Bug 154583 Summary: Split button Color Picker regression, attempting a color pick now opens the Line or Area object dialog https://bugs.documentfoundation.org/show_bug.cgi?id=154583 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155725] New: spaces at end of lines don't appear on screen
https://bugs.documentfoundation.org/show_bug.cgi?id=155725 Bug ID: 155725 Summary: spaces at end of lines don't appear on screen Product: LibreOffice Version: 7.1.3.2 release Hardware: Other OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: l...@leegass.com Beginning today, with Libre Office7.1.3.2, composing a text document a problem started bugging me. With one kind of writing I do, I use centred text format and create new lines with linefeeds (return). Normally, if I enter a space that space registers on the screen, and that does happen within lines. But if I add a space at the end of a line, it doesn't register on the screen. That means I must keep track of how many spaces I've entered, and if I don't remember it right I either jam words up against each other or Libre complains that I have too many spaces. I think ensuring all spaces entered appear on the screen would save me much time, effort, and frustration. Thanks, Lee Gass -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 66458] FILEOPEN: DOCX imports 'ptab' as 'tab' instead of its own type
https://bugs.documentfoundation.org/show_bug.cgi?id=66458 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=78 ||144 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 78144] FILEOPEN: WPS DOC - Incorrect alignment of page number in footer due to wrong position of tab stop (needs w:ptab equivalent)
https://bugs.documentfoundation.org/show_bug.cgi?id=78144 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=66 ||458 --- Comment #17 from Justin L --- Good information and code pointers in bug 66458. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 78144] FILEOPEN: WPS DOC - Incorrect alignment of page number in footer due to wrong position of tab stop (needs w:ptab equivalent)
https://bugs.documentfoundation.org/show_bug.cgi?id=78144 Justin L changed: What|Removed |Added CC||rattles2...@gmail.com --- Comment #16 from Justin L --- *** Bug 66458 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 104520] [META] DOCX (OOXML) bug tracker
https://bugs.documentfoundation.org/show_bug.cgi?id=104520 Bug 104520 depends on bug 66458, which changed state. Bug 66458 Summary: FILEOPEN: DOCX imports 'ptab' as 'tab' instead of its own type https://bugs.documentfoundation.org/show_bug.cgi?id=66458 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 66458] FILEOPEN: DOCX imports 'ptab' as 'tab' instead of its own type
https://bugs.documentfoundation.org/show_bug.cgi?id=66458 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #12 from Justin L --- *** This bug has been marked as a duplicate of bug 78144 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93675] FILESAVE DOCX Grouped shapes text in Word is attached to different shapes than in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=93675 --- Comment #38 from Dave Gilbert --- (In reply to Regina Henschel from comment #37) > The reason of the rotation trouble is, that a shape gets attached a frame on > import to be able to contain complex texts like char anchored images and > tables. And these frames are not able to rotate. > > At that time, when this happens, there is no simple way to detect, whether > the contained content is a complex text or a simple text. > > You will likely find other bug reports about the missing ability of frames > to rotate. Hi Regina, Thanks for the reply. So is that a new issue? - I thought the rotation used to work, and the screenshot from 2021-07-26 seems to suggest it did. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94728] Shadow color in DOCX is different from Word
https://bugs.documentfoundation.org/show_bug.cgi?id=94728 --- Comment #9 from Justin L --- repro 7.6 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149672] FILEOPEN DOCX IF field complex content not imported correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=149672 Justin L changed: What|Removed |Added Version|7.5.0.0 alpha0+ |unspecified -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135569] FILEOPEN DOCX Inner margins are rotated with textbox
https://bugs.documentfoundation.org/show_bug.cgi?id=135569 Justin L changed: What|Removed |Added Whiteboard|target:7.5.0 target:7.4.1 | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123110] FILEOPEN DOCX Text in shape has wrong color
https://bugs.documentfoundation.org/show_bug.cgi?id=123110 --- Comment #9 from Justin L --- repro 7.6 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138699] FILESAVE: DOCX: Drop-Down Form Field bookmark data is lost on save
https://bugs.documentfoundation.org/show_bug.cgi?id=138699 --- Comment #5 from Justin L --- repro 7.6 (I think). There is no bookmark name seen in MSO when opening up the field dialog. It should be "field1" and "field2". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146383] ODT->DOCX export: Wrap triggered around image after DOCX export
https://bugs.documentfoundation.org/show_bug.cgi?id=146383 Justin L changed: What|Removed |Added Severity|normal |minor Priority|medium |low Summary|DOCX export: Wrap triggered |ODT->DOCX export: Wrap |around image after DOCX |triggered around image |export |after DOCX export Version|7.3.0.0 alpha0+ |7.3.0.0.alpha1+ --- Comment #9 from Justin L --- repro 7.6 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138366] Vertical text position within a text box doesn't set correct spacing
https://bugs.documentfoundation.org/show_bug.cgi?id=138366 --- Comment #6 from Justin L --- repro 7.6 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93675] FILESAVE DOCX Grouped shapes text in Word is attached to different shapes than in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=93675 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de --- Comment #37 from Regina Henschel --- The reason of the rotation trouble is, that a shape gets attached a frame on import to be able to contain complex texts like char anchored images and tables. And these frames are not able to rotate. At that time, when this happens, there is no simple way to detect, whether the contained content is a complex text or a simple text. You will likely find other bug reports about the missing ability of frames to rotate. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145854] Fileopen: DOCX table should still fit the page even if "Preferred width" in MSO is larger than page
https://bugs.documentfoundation.org/show_bug.cgi?id=145854 --- Comment #7 from Justin L --- repro 7.6 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155724] -env:UserInstallation= broken on Windows
https://bugs.documentfoundation.org/show_bug.cgi?id=155724 --- Comment #1 from Jim Avera --- I'm sorry (copy-paste mistake), the .ini file contains UserInstallation=$SYSUSERCONFIG/LibreOffice/4 Also, the batch file name should end in .bat not .bad -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155724] New: -env:UserInstallation= broken on Windows
https://bugs.documentfoundation.org/show_bug.cgi?id=155724 Bug ID: 155724 Summary: -env:UserInstallation= broken on Windows Product: LibreOffice Version: 7.5.3.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Installation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jim.av...@gmail.com The documented UserInstallation mechanism for specifying a profile directory does not work on Windows. I think the reason is that 'UserInstallation' is defined in "C:\Program Files\LibreOffice\program\bootstrap.ini" and it can not be over-ridden with an environment variable or using the documented command line option -env:UserInstallation=file://... Can LO be made to ignore the setting in .ini if the user explicitly over-rides it with a command line option? --- details --- This prevents safely using LO as a batch tool to convert files (--convert-to option etc.) because if the user has an interactive session running then random aborts will occur. https://wiki.documentfoundation.org/UserProfile says the following will start LO with a different user profile: For Windows: soffice.com -env:UserInstallation=file:///c:/my-test-profile Initially, that fails because .../program/ was not registered by the installer to be in PATH, so "soffice.com" is not found. If the fully-qualified path is specified, then a pop-up error says The application cannot be started. The configuration file "C:\Program Files\LibreOffice\program\bootstrap.ini" is corrupt. That .ini file does contain "C:\Program Files\LibreOffice\program\bootstrap.ini" which seems to cause this conflict. STEPS TO REPRODUCE: 1. Using Vim or Notepad, create a file "test.bad" containing the following two lines (change the paths appropriately): mkdir "C:\Users\Admin0\AppData\Local\Temp\TestProfile" "C:\Program Files\LibreOffice\program\soffice.com" "-env:UserInstallation=file://C:\Users\Admin0\AppData\Local\Temp\TestProfile" 2. Type the name/path of the script (e.g. "test.bat") RESULTS: The "corrupted" error pop-up appears and LO stalls waiting for the user to click ok. - Note: There is no such problem on Linux. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149538] OOXML DOCX bad import, export and rendering for property "upright"
https://bugs.documentfoundation.org/show_bug.cgi?id=149538 Justin L changed: What|Removed |Added OS|Windows (All) |All Hardware|x86-64 (AMD64) |All Version|7.4.0.0 alpha0+ |unspecified -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134670] FILEOPEN DOCX : The use of vertical and horizontal typesetting results in the loss of text content and typesetting style
https://bugs.documentfoundation.org/show_bug.cgi?id=134670 --- Comment #5 from Justin L --- repro 7.6+ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148834] Line numbering for specific paragraphs gets lost after saving to ODT->.docx file format
https://bugs.documentfoundation.org/show_bug.cgi?id=148834 Justin L changed: What|Removed |Added CC||jl...@mail.com Summary|Line numbering for specific |Line numbering for specific |paragraphs gets lost after |paragraphs gets lost after |saving to .docx file format |saving to ODT->.docx file ||format Priority|medium |low Version|3.3.0 release |Inherited From OOo Severity|normal |minor --- Comment #2 from Justin L --- Low priority: Things designed in Word seem to round-trip well. Things designed in LO using simple styles seem to work well also. MS Word has line numbering tied to a section. All paragraphs in a section participate, and require an explicit "suppress line numbers" paragraph property to avoid being numbered. LO does not tie numbering to page styles or sections AFAICS. It is just on or off for the whole document. But that sounds like it all should work. What is the problem then? I assume that the property is not written when it is false. Yup - here it is: if ( !rNumbering.IsCount( ) ) m_pSerializer->singleElementNS(XML_w, XML_suppressLineNumbers); Generally, that is a good thing, but not when it needs to override an inherited value (like in this case where the style says suppress, but the direct formatting says don't suppress). See ExportPoolItemsToCHP for some ideas on how to check that. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155723] New: Regular Pentagon tool draws pentagons, not regular pentagons
https://bugs.documentfoundation.org/show_bug.cgi?id=155723 Bug ID: 155723 Summary: Regular Pentagon tool draws pentagons, not regular pentagons Product: LibreOffice Version: 7.4.7.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dmatsch...@quietriding.com The Basic Shapes toolbar has a tool named "Regular Pentagon". However, the tool actually draws simple pentagons, not "regular" pentagons. A pentagon is a shape with 5 sides. A regular pentagon has 5 equal sides and 5 equal angles. For accuracy, and to avoid confusion, the name of this tool should be changed from "Regular Pentagon" to simply "Pentagon". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93675] FILESAVE DOCX Grouped shapes text in Word is attached to different shapes than in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=93675 --- Comment #36 from Dave Gilbert --- Here's a diff of the (xmllint'd) word/document.xml from the unzip'd docx, other than a one pixel shift in x coords for some wierd reason, the diff is pretty much just the removal of that vertical line, so something in there must be confusing the heck out of word: [dg@dalek unpacked-diagram-2015-08-noline]$ diff ../unpacked-mod/word/document-linted.xml word/document-linted.xml 1090c1090 < --- > 1094,1096c1094,1096 < < < --- > > > 1100c1100 < --- > 1461c1461 < --- > 1464c1464 < --- > 1484,1527d1483 < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < WOabcdefghijklm < < < < < < < < < 1724c1680 < --- > 1727c1683 < --- > 2235c2191 < --- > path="m2794,99c2196,0,1896,300,1398,500c0,2398,1164,5990,1198,8786c1198,9185,356,9181,223,9380e" > stroked="t" o:allowincell="f" > style="position:absolute;left:1729;top:2894;width:1457;height:5272"> 2387c2343 < --- > path="m0,0c1397,1498,2825,1280,2825,1280l8347,1289e" stroked="t" > o:allowincell="f" > style="position:absolute;left:1373;top:5743;width:4731;height:731"> 2392,2413d2347 < < < < < < < < < < < < < < abcdefghijklm < < < < < < < < 2515c2449 < --- > path="m0,4003c99,1709,1997,1,3100,0l8623,10e" stroked="t" o:allowincell="f" > style="position:absolute;left:1157;top:2670;width:4887;height:2268"> -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93675] FILESAVE DOCX Grouped shapes text in Word is attached to different shapes than in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=93675 --- Comment #35 from Dave Gilbert --- Deleting the thin line from c->b and then save-as docx gives me a file that's displayed with all the right text in the right place in OneDrive/word. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: svx/sdi svx/source
svx/sdi/xoitems.sdi| 16 +++--
svx/source/tbxctrls/PaletteManager.cxx |2 +
svx/source/xoutdev/xattr.cxx | 40 +
3 files changed, 56 insertions(+), 2 deletions(-)
New commits:
commit 5a2c6f4df7149f8c1f543f120fe19bd66abfc189
Author: Tomaž Vajngerl
AuthorDate: Thu Jun 8 01:36:27 2023 +0900
Commit: Tomaž Vajngerl
CommitDate: Thu Jun 8 01:21:44 2023 +0200
tdf#155404 handle ComplexColor as JSON for XLineColor and XFillColor
This adds support for MID_COMPLEX_COLOR_JSON attribute for
XLineColorItem and XFillColorItem, which makes it possible to set
a theme colors from the UI also for fills and lines.
In addition this resolved the issue tdf#155404 which had the effect
that unsupported "Color" attribute for the UNO call resulted that
the dialog was opened. This is now not the case anymore as the
"Color" argument for XLineColorItem and XFillColorItem was added
in addition to "ComplexColorJSON" argument.
Change-Id: I8876942b07aba453cbe1422b76a1608c78e42109
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152713
Tested-by: Jenkins
Reviewed-by: Tomaž Vajngerl
diff --git a/svx/sdi/xoitems.sdi b/svx/sdi/xoitems.sdi
index 015ead6e0d72..50db129a6434 100644
--- a/svx/sdi/xoitems.sdi
+++ b/svx/sdi/xoitems.sdi
@@ -24,7 +24,13 @@ struct XFillBitmap
};
item XFillBitmap XFillBitmapItem;
-item INT32 XFillColorItem; // XColorItem
+struct XFillColor
+{
+INT32 Color MID_COLOR_RGB;
+String ComplexColorJSON MID_COMPLEX_COLOR_JSON;
+};
+
+item XFillColor XFillColorItem; // XColorItem
enum SvxGradientStyle
{
@@ -84,7 +90,13 @@ item SvxFillStyle XFillStyleItem;
//item String XLineAttrSetItem; SfxSetItem!
-item INT32 XLineColorItem;
+struct XLineColor
+{
+INT32 Color MID_COLOR_RGB;
+String ComplexColorJSON MID_COMPLEX_COLOR_JSON;
+};
+
+item XLineColor XLineColorItem;
enum SvxDashStyle
{
diff --git a/svx/source/tbxctrls/PaletteManager.cxx
b/svx/source/tbxctrls/PaletteManager.cxx
index b56248825600..141938d145d7 100644
--- a/svx/source/tbxctrls/PaletteManager.cxx
+++ b/svx/source/tbxctrls/PaletteManager.cxx
@@ -427,6 +427,8 @@ void PaletteManager::DispatchColorCommand(const OUString&
aCommand, const NamedC
comphelper::makePropertyValue(aObj.GetURLPath()+ ".Color",
sal_Int32(rColor.m_aColor)),
};
+printf ("Sending: %s\n", aObj.GetURLPath().toUtf8().getStr());
+
if (rColor.m_nThemeIndex != -1)
{
model::ComplexColor aComplexColor;
diff --git a/svx/source/xoutdev/xattr.cxx b/svx/source/xoutdev/xattr.cxx
index 4860373836a8..d3fd73f5fa04 100644
--- a/svx/source/xoutdev/xattr.cxx
+++ b/svx/source/xoutdev/xattr.cxx
@@ -37,6 +37,7 @@
#include
#include
#include
+#include
#include
#include
#include
@@ -1002,6 +1003,11 @@ bool XLineColorItem::QueryValue( css::uno::Any& rVal,
sal_uInt8 nMemberId) const
rVal <<= xComplexColor;
break;
}
+case MID_COMPLEX_COLOR_JSON:
+{
+rVal <<=
OStringToOUString(model::color::convertToJSON(getComplexColor()),
RTL_TEXTENCODING_UTF8);
+break;
+}
default:
{
rVal <<= GetColorValue().GetRGBColor();
@@ -1024,6 +1030,20 @@ bool XLineColorItem::PutValue( const css::uno::Any&
rVal, sal_uInt8 nMemberId)
setComplexColor(model::color::getFromXComplexColor(xComplexColor));
}
break;
+case MID_COMPLEX_COLOR_JSON:
+{
+OUString sComplexColorJson;
+if (!(rVal >>= sComplexColorJson))
+return false;
+
+if (sComplexColorJson.isEmpty())
+return false;
+model::ComplexColor aComplexColor;
+OString aJSON = OUStringToOString(sComplexColorJson,
RTL_TEXTENCODING_ASCII_US);
+model::color::convertFromJSON(aJSON, aComplexColor);
+setComplexColor(aComplexColor);
+}
+break;
default:
{
sal_Int32 nValue;
@@ -1985,6 +2005,11 @@ bool XFillColorItem::QueryValue( css::uno::Any& rVal,
sal_uInt8 nMemberId ) cons
rVal <<= xComplexColor;
break;
}
+case MID_COMPLEX_COLOR_JSON:
+{
+rVal <<=
OStringToOUString(model::color::convertToJSON(getComplexColor()),
RTL_TEXTENCODING_UTF8);
+break;
+}
default:
{
rVal <<= GetColorValue().GetRGBColor();
@@ -2034,6 +2059,21 @@ bool XFillColorItem::PutValue( const css::uno::Any&
rVal, sal_uInt8 nMemberId )
setComplexColor(model::color::getFromXComplexColor(xComplexColor));
}
break;
+case MID_COMPLEX_COLOR_JSON:
+{
+OUString sComplexColorJson;
+if (!(rVal >>= sComplexColorJson))
+return false;
+
+if (sComplexColorJson.isEmpty())
+
[Libreoffice-bugs] [Bug 155404] Toolbar: choosing a color in the color picker opens the Area dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=155404 --- Comment #3 from Commit Notification --- Tomaž Vajngerl committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/5a2c6f4df7149f8c1f543f120fe19bd66abfc189 tdf#155404 handle ComplexColor as JSON for XLineColor and XFillColor It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155404] Toolbar: choosing a color in the color picker opens the Area dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=155404 Commit Notification changed: What|Removed |Added Whiteboard||target:24.2.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96506] The "Use Styles From Another Document" feature doesn't work if the other document is a .fodt one
https://bugs.documentfoundation.org/show_bug.cgi?id=96506 --- Comment #11 from Ganton --- The bug still exists using Libreoffice 7.5.3.2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154994] Functions sidebar should be searchable as soon as it is focused
https://bugs.documentfoundation.org/show_bug.cgi?id=154994 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||5283 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122718] Sidebar Functions panel misses search like Function Wizard
https://bugs.documentfoundation.org/show_bug.cgi?id=122718 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||5283 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 155283] Need ability to filter sidebar style list by typing
https://bugs.documentfoundation.org/show_bug.cgi?id=155283 Stéphane Guillou (stragu) changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4994, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||2718 Keywords||needsUXEval --- Comment #5 from Stéphane Guillou (stragu) --- (In reply to Eyal Rozenberg from comment #4) > 1. I want this without having clicked a list item first, although that's not > a critical part of the ask. Reminds me of bug 154994. There's the question of "should toggling a UI element move the keyboard focus off the page?" As I noted in bug 154994 comment 2, the Gallery and Navigator decks already do that. > 2. When I click a list item and type, the list scrolls to the first match > for what I've typed, it doesn't filter. Similar to bug 122718 for functions. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 155283] Need ability to filter sidebar style list by typing
https://bugs.documentfoundation.org/show_bug.cgi?id=155283 Stéphane Guillou (stragu) changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4994, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||2718 Keywords||needsUXEval --- Comment #5 from Stéphane Guillou (stragu) --- (In reply to Eyal Rozenberg from comment #4) > 1. I want this without having clicked a list item first, although that's not > a critical part of the ask. Reminds me of bug 154994. There's the question of "should toggling a UI element move the keyboard focus off the page?" As I noted in bug 154994 comment 2, the Gallery and Navigator decks already do that. > 2. When I click a list item and type, the list scrolls to the first match > for what I've typed, it doesn't filter. Similar to bug 122718 for functions. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155492] .DOC and .DOCX files do not display correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=155492 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|FIXED |WORKSFORME --- Comment #5 from Stéphane Guillou (stragu) --- Thanks Tim. Setting the resolution to "works for me" instead, as "fixed" is for when a code patch fixes the issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150419] FILESAVE ODT->DOCX page style writing direction "left-to-right (vertical)" is wrongly exported
https://bugs.documentfoundation.org/show_bug.cgi?id=150419 Justin L changed: What|Removed |Added Summary|FILESAVE DOCX page writing |FILESAVE ODT->DOCX page |direction "left-to-right|style writing direction |(vertical)" is wrongly |"left-to-right (vertical)" |exported|is wrongly exported --- Comment #5 from Justin L --- This looks like it was fixed in LO 7.5 with commit c70ee4a6b9071468255e5d4fdb893e9c9bdf4fad Author: Regina Henschel on Wed Aug 17 02:31:44 2022 +0200 tdf#149551 use 'WritingMode' instead of TextPreRotateAngle -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121508] FILESAVE ODT->DOCX Shape in frame is lost after export
https://bugs.documentfoundation.org/show_bug.cgi?id=121508 Justin L changed: What|Removed |Added Summary|FILESAVE DOCX Shape in |FILESAVE ODT->DOCX Shape in |frame is lost after export |frame is lost after export --- Comment #8 from Justin L --- I don't actually see a lost frame in Frame-Paragraph-Shape.odt (tested 7.2), but I do see it in the duplicate www (6) (2) (5).odt (tested 7.6) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134635] FILEOPEN DOCX : Set the page to a stationery grid and save docx, then open the grid line can not be aligned
https://bugs.documentfoundation.org/show_bug.cgi?id=134635 --- Comment #5 from Justin L --- It looks fixed to me in LO 7.0.6 with commit c9e5640c8fcad7beb42a66f9bee0252eee9fe323 Author: Xisco Fauli on Thu Mar 18 00:48:49 2021 +0100 tdf#118693: no need to use convertMm100ToTwip() for line shapes anymore -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155722] New: Footers and Pagebreaks are never saved when I edit a saved Spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=155722 Bug ID: 155722 Summary: Footers and Pagebreaks are never saved when I edit a saved Spreadsheet Product: LibreOffice Version: 7.5.3.2 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ianjbis...@gmail.com Description: I have a Spreadsheet I use for work which I update every couple of weeks or so. I'm doing small editing like adding or deleting items in the spreadsheet. Adding and/or removing page breaks and editing the footer notes. In the footer notes, I have the Month and Year eg:(June 2023) and the page numbers. I will save the spreadsheet and export a pdf which I show to clients, but if I need to go back and edit the spreadsheet, my pagebreaks are all screwed up and my footer notes are different. For example: I will save the footer as "June 2023" then when I go back into the spreadsheet to edit again, it will say "January 2023" and this happens all the time for some reason. Steps to Reproduce: 1.Edit foot notes and save 2.Edit pagebreaks and save 3.Open spreadsheet and the above are not saved. Actual Results: The footnotes and pagebreaks are not saved. Expected Results: Save the exact way I left and saved the document. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: SpreadsheetDocument [Information guessed from browser] OS: Mac OS X (All) OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93675] FILESAVE DOCX Grouped shapes text in Word is attached to different shapes than in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=93675 --- Comment #34 from Dave Gilbert --- observation on the wrong text: a) I confirmed that both LO and Onedrive are showing the DML/non-fallback version of the drawing in the file b) It's a 'after this point' error in the output file, that is if you look at the order of items in the output file we have: ... Host 2 More hosts b FIRST MISPLACE abcdefghijklm Da da da de de de yabba yabba yabba Yabba yabba yabba Stuff going this way Data going around bend a all the items upto the 'b' end up in the right place, but everything after end up wrong. It's the stuff that should be vertical text on the thin line between 'b' and 'c' -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94657] borders not visible on loading docx
https://bugs.documentfoundation.org/show_bug.cgi?id=94657 Justin L changed: What|Removed |Added Priority|medium |low Severity|normal |enhancement Hardware|Other |All --- Comment #14 from Justin L --- repro 7.6+ Yeah, LO doesn't have "art" available as a page border. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - xmloff/qa
xmloff/qa/unit/style.cxx |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit 23a321d256ec868dcc2011de12c24da931e1dae6
Author: Miklos Vajna
AuthorDate: Wed Jun 7 15:21:41 2023 +0200
Commit: Andras Timar
CommitDate: Wed Jun 7 23:00:27 2023 +0200
CppunitTest_xmloff_style: fix testAxialTransparencyCompatible on this branch
master gave up on validating DOCX files in commit
58ab2f002fd27974b474151b01287dac221dc102 (SwModelTestBase: get rid of
mustValidate, 2023-05-31), manual skip is still needed on this branch.
Change-Id: I74cc344fafd4ec5f2e829f36463b1a84acfbb7f5
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152702
Tested-by: Jenkins CollaboraOffice
Reviewed-by: Andras Timar
diff --git a/xmloff/qa/unit/style.cxx b/xmloff/qa/unit/style.cxx
index 471b3eada79b..69579938821e 100644
--- a/xmloff/qa/unit/style.cxx
+++ b/xmloff/qa/unit/style.cxx
@@ -641,7 +641,7 @@ CPPUNIT_TEST_FIXTURE(XmloffStyleTest,
testAxialTransparencyCompatible)
//Round-trip through OOXML.
// FixMe tdf#153183, and error in charSpace and in CharacterSet
-//skipValidation();
+skipValidation();
saveAndReload("Office Open XML Text");
saveAndReload("writer8");
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - writerfilter/source
writerfilter/source/dmapper/DomainMapper.cxx | 20 ---
writerfilter/source/dmapper/DomainMapperTableManager.cxx |3 --
writerfilter/source/dmapper/DomainMapperTableManager.hxx |5 ---
3 files changed, 28 deletions(-)
New commits:
commit 6c67853b0798cf20fef02fcffd383e7f95cb66bd
Author: Miklos Vajna
AuthorDate: Tue Jun 6 08:22:53 2023 +0200
Commit: Andras Timar
CommitDate: Wed Jun 7 22:59:02 2023 +0200
sw floattable, DOCX import: clean up not needed dmapper-level anchor insert
This was added in commit 1c99616f86f7d5b83b91edc225fc95fec227d710 (sw
floattable, crashtesting: fix PDF export of forum-mso-en3-26783.docx,
2023-05-02) to ensure that in case a floating table is not followed by a
text node, then inject one at a dmapper level.
Later commit 01ad8ec4bb5425446e95dbada81de435646824b4 (sw floattable:
fix lost tables around a floating table from DOCX, 2023-06-05) did the
same at a tokenizer level, as doing it in dmapper is too late in some
cases.
So keep the testcase from the first commit, but the changes to dmapper
can be dropped.
(cherry picked from commit 4c5438b2c447403194420b69311a81ea7d36e157)
Change-Id: If5b702d99e81a3f939491b7ff9de1128da765cbf
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152694
Tested-by: Jenkins CollaboraOffice
Reviewed-by: Andras Timar
diff --git a/writerfilter/source/dmapper/DomainMapper.cxx
b/writerfilter/source/dmapper/DomainMapper.cxx
index 593cf813c3e3..c6a11e38b74a 100644
--- a/writerfilter/source/dmapper/DomainMapper.cxx
+++ b/writerfilter/source/dmapper/DomainMapper.cxx
@@ -3164,17 +3164,6 @@ void DomainMapper::sprmWithProps( Sprm& rSprm, const
PropertyMapPtr& rContext )
break;
case NS_ooxml::LN_tblStart:
{
-if (m_pImpl->hasTableManager())
-{
-if (m_pImpl->getTableManager().IsFloating())
-{
-// We're starting a new table, but the previous table was
floating. Insert a dummy
-// paragraph to ensure that the floating table is not anchored
inside the next
-// table.
-finishParagraph();
-}
-}
-
if (m_pImpl->hasTableManager())
{
bool bTableStartsAtCellStart = m_pImpl->m_nTableDepth > 0 &&
m_pImpl->m_nTableCellDepth > m_pImpl->m_nLastTableCellParagraphDepth + 1;
@@ -4756,15 +4745,6 @@ void DomainMapper::finishParagraph(const bool bRemove,
const bool bNoNumbering)
if (m_pImpl->m_pSdtHelper->getControlType() == SdtControlType::datePicker)
m_pImpl->m_pSdtHelper->createDateContentControl();
m_pImpl->finishParagraph(m_pImpl->GetTopContextOfType(CONTEXT_PARAGRAPH),
bRemove, bNoNumbering);
-if (m_pImpl->m_nTableDepth == 0)
-{
-if (m_pImpl->hasTableManager())
-{
-// Non-table content, possibly after a table. Forget that such a
previous table was
-// floating.
-m_pImpl->getTableManager().SetFloating(false);
-}
-}
}
void DomainMapper::commentProps(const OUString& sId, const CommentProperties&
rProps)
diff --git a/writerfilter/source/dmapper/DomainMapperTableManager.cxx
b/writerfilter/source/dmapper/DomainMapperTableManager.cxx
index bf3c78dcebee..004f34971b6a 100644
--- a/writerfilter/source/dmapper/DomainMapperTableManager.cxx
+++ b/writerfilter/source/dmapper/DomainMapperTableManager.cxx
@@ -334,9 +334,6 @@ bool DomainMapperTableManager::sprm(Sprm & rSprm)
break;
case NS_ooxml::LN_CT_TblPrBase_tblpPr:
{
-// Remember that this will be a floating table.
-m_bIsFloating = true;
-
writerfilter::Reference::Pointer_t pProperties
= rSprm.getProps();
// Ignore in shape text, those tables should be
always non-floating ones.
if (!m_bIsInShape && pProperties)
diff --git a/writerfilter/source/dmapper/DomainMapperTableManager.hxx
b/writerfilter/source/dmapper/DomainMapperTableManager.hxx
index 955ccfafc963..a2e492936b96 100644
--- a/writerfilter/source/dmapper/DomainMapperTableManager.hxx
+++ b/writerfilter/source/dmapper/DomainMapperTableManager.hxx
@@ -42,8 +42,6 @@ class DomainMapperTableManager : public TableManager
sal_Int32 m_nTableWidth; //might be set directly or has to be
calculated from the column positions
/// Are we in a shape (text append stack is not empty) or in the body
document?
bool m_bIsInShape;
-/// Is the current table floating?
-bool m_bIsFloating = false;
std::vector< OUString > m_aTableStyleNames;
/// Moved table (in moveRangeFromStart...moveRangeFromEnd or
moveRangeToStart...moveRangeToEnd)
std::vector< OUString > m_aMoved;
@@ -167,9 +165,6 @@ public:
return OUString();
}
-bool IsFloating() const { return m_bIsFloating; }
-
-void
[Libreoffice-bugs] [Bug 132092] DOCX import: a generated document has black text highlighting, where in Word, the background is white (OK if resaved in MSO)
https://bugs.documentfoundation.org/show_bug.cgi?id=132092 Justin L changed: What|Removed |Added Summary|DOCX import: a generated|DOCX import: a generated |document has black text |document has black text |highlighting, where in |highlighting, where in |Word, the background is |Word, the background is |white |white (OK if resaved in ||MSO) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104444] [META] DOCX (OOXML) table-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=10 Bug 10 depends on bug 134891, which changed state. Bug 134891 Summary: FILEOPEN DOCX : Compatibility problem of slash table-header https://bugs.documentfoundation.org/show_bug.cgi?id=134891 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 51665] Writer: support diagonal borders in tables
https://bugs.documentfoundation.org/show_bug.cgi?id=51665 Justin L changed: What|Removed |Added CC||leiy...@kylinos.cn --- Comment #26 from Justin L --- *** Bug 134891 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 134891] FILEOPEN DOCX : Compatibility problem of slash table-header
https://bugs.documentfoundation.org/show_bug.cgi?id=134891 Justin L changed: What|Removed |Added Resolution|--- |DUPLICATE Version|4.4 all versions|Inherited From OOo Status|NEW |RESOLVED --- Comment #4 from Justin L --- *** This bug has been marked as a duplicate of bug 51665 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104520] [META] DOCX (OOXML) bug tracker
https://bugs.documentfoundation.org/show_bug.cgi?id=104520 Bug 104520 depends on bug 36999, which changed state. Bug 36999 Summary: DOCX import: For hidden ActiveX control, the replacement wmf is always shown https://bugs.documentfoundation.org/show_bug.cgi?id=36999 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 36999] DOCX import: For hidden ActiveX control, the replacement wmf is always shown
https://bugs.documentfoundation.org/show_bug.cgi?id=36999 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #22 from Justin L --- bug document no longer available from link - access denied. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155434] Several Calc menu commands are available in Read-Only mode
https://bugs.documentfoundation.org/show_bug.cgi?id=155434 ady changed: What|Removed |Added Keywords||needsUXEval -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/qa
sw/qa/extras/uiwriter/data/tdf155685.docx |binary
sw/qa/extras/uiwriter/uiwriter3.cxx | 21 +
2 files changed, 21 insertions(+)
New commits:
commit e995fc61cef8fad6076212a0d7e8e357e5db1793
Author: Xisco Fauli
AuthorDate: Wed Jun 7 13:30:16 2023 +0200
Commit: Xisco Fauli
CommitDate: Wed Jun 7 22:42:06 2023 +0200
tdf#155685: sw_uiwriter3: Add unittest
Change-Id: I13bde9aec9455d38435e6fd0d17d24544d9d0952
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152701
Tested-by: Jenkins
Reviewed-by: Xisco Fauli
diff --git a/sw/qa/extras/uiwriter/data/tdf155685.docx
b/sw/qa/extras/uiwriter/data/tdf155685.docx
new file mode 100644
index ..ed45d7adc6cc
Binary files /dev/null and b/sw/qa/extras/uiwriter/data/tdf155685.docx differ
diff --git a/sw/qa/extras/uiwriter/uiwriter3.cxx
b/sw/qa/extras/uiwriter/uiwriter3.cxx
index ef6de9c8e660..2d202567896d 100644
--- a/sw/qa/extras/uiwriter/uiwriter3.cxx
+++ b/sw/qa/extras/uiwriter/uiwriter3.cxx
@@ -84,6 +84,27 @@ CPPUNIT_TEST_FIXTURE(SwUiWriterTest3, testTdf151974)
}
}
+CPPUNIT_TEST_FIXTURE(SwUiWriterTest3, testTdf155685)
+{
+createSwDoc("tdf155685.docx");
+
+CPPUNIT_ASSERT_EQUAL(8, getShapes());
+CPPUNIT_ASSERT_EQUAL(1, getPages());
+
+dispatchCommand(mxComponent, ".uno:SelectAll", {});
+
+dispatchCommand(mxComponent, ".uno:Cut", {});
+
+CPPUNIT_ASSERT_EQUAL(0, getShapes());
+CPPUNIT_ASSERT_EQUAL(1, getPages());
+
+// Without the fix in place, this test would have crashed here
+dispatchCommand(mxComponent, ".uno:Undo", {});
+
+CPPUNIT_ASSERT_EQUAL(8, getShapes());
+CPPUNIT_ASSERT_EQUAL(1, getPages());
+}
+
CPPUNIT_TEST_FIXTURE(SwUiWriterTest3, testTdf145731)
{
createSwDoc("tdf145731.odt");
[Libreoffice-bugs] [Bug 51665] Writer: support diagonal borders in tables
https://bugs.documentfoundation.org/show_bug.cgi?id=51665 Justin L changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=14 | |5945| CC||jl...@mail.com Summary|Support diagonal borders in |Writer: support diagonal |TABLEs |borders in tables -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145945] FILEOPEN DOCX: diagonal borders isn't displayed on the table.
https://bugs.documentfoundation.org/show_bug.cgi?id=145945 Justin L changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=51 | |665 | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104444] [META] DOCX (OOXML) table-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=10 Bug 10 depends on bug 145945, which changed state. Bug 145945 Summary: FILEOPEN DOCX: diagonal borders isn't displayed on the table. https://bugs.documentfoundation.org/show_bug.cgi?id=145945 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 51665] Support diagonal borders in TABLEs
https://bugs.documentfoundation.org/show_bug.cgi?id=51665 Justin L changed: What|Removed |Added CC||20001...@ymail.ne.jp --- Comment #25 from Justin L --- *** Bug 145945 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 145945] FILEOPEN DOCX: diagonal borders isn't displayed on the table.
https://bugs.documentfoundation.org/show_bug.cgi?id=145945 Justin L changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #9 from Justin L --- *** This bug has been marked as a duplicate of bug 51665 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: config_host.mk.in configure.ac desktop/CustomTarget_soffice.mk desktop/Module_desktop.mk lo.xcent.in solenv/bin
config_host.mk.in |1 +
configure.ac |9 -
desktop/CustomTarget_soffice.mk | 19 +++
desktop/Module_desktop.mk |2 +-
lo.xcent.in |1 +
solenv/bin/macosx-codesign-app-bundle | 16 ++--
solenv/bin/modules/installer/simplepackage.pm |5 -
7 files changed, 44 insertions(+), 9 deletions(-)
New commits:
commit 67b808eea02219ef51324f560e673e33e736
Author: Patrick Luby
AuthorDate: Sat May 20 08:50:12 2023 -0400
Commit: Patrick Luby
CommitDate: Wed Jun 7 22:08:50 2023 +0200
Set entitlements in non-release in $(INSTROOTBASE) and .dmg package
Also, when building a .dmg for macOS, skip codesigning for non-release
builds, both with and without the macOS sandbox, if there is no identity
set but set entitlements to allow Xcode's Instruments application to
connect to the application.
Lastly, add entitlements when building soffice in $(INSTROOTBASE) if
this is a non-release build.
Change-Id: I764bf5bd5d44e878669c4287906e6efd6aac593f
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152655
Tested-by: Jenkins
Reviewed-by: Patrick Luby
diff --git a/config_host.mk.in b/config_host.mk.in
index 8b809bf9141f..6a120c2098cc 100644
--- a/config_host.mk.in
+++ b/config_host.mk.in
@@ -760,6 +760,7 @@ export ZLIB_CFLAGS=$(gb_SPACE)@ZLIB_CFLAGS@
export ZLIB_LIBS=$(gb_SPACE)@ZLIB_LIBS@
export ZMF_CFLAGS=$(gb_SPACE)@ZMF_CFLAGS@
export ZMF_LIBS=$(gb_SPACE)@ZMF_LIBS@
+export GET_TASK_ALLOW_ENTITLEMENT=@GET_TASK_ALLOW_ENTITLEMENT@
# lang-related stuff
include $(BUILDDIR)/config_$(gb_Side)_lang.mk
diff --git a/configure.ac b/configure.ac
index 9d70be6200b6..d281d48ba8f0 100644
--- a/configure.ac
+++ b/configure.ac
@@ -2852,14 +2852,13 @@ AC_MSG_CHECKING([whether build target is Release Build])
if test "$enable_release_build" = "" -o "$enable_release_build" = "no"; then
AC_MSG_RESULT([no])
ENABLE_RELEASE_BUILD=
-GET_TASK_ALLOW_ENTITLEMENT='
-
-com.apple.security.get-task-allow
-'
+dnl Pu the value on one line as make (at least on macOS) seems to ignore
+dnl the newlines and then complains about spaces.
+GET_TASK_ALLOW_ENTITLEMENT='com.apple.security.get-task-allow'
else
AC_MSG_RESULT([yes])
ENABLE_RELEASE_BUILD=TRUE
-GET_TASK_ALLOW_ENTITLEMENT=''
+GET_TASK_ALLOW_ENTITLEMENT=
fi
AC_SUBST(ENABLE_RELEASE_BUILD)
AC_SUBST(GET_TASK_ALLOW_ENTITLEMENT)
diff --git a/desktop/CustomTarget_soffice.mk b/desktop/CustomTarget_soffice.mk
index d56f571628fe..4df29fc3cae3 100644
--- a/desktop/CustomTarget_soffice.mk
+++ b/desktop/CustomTarget_soffice.mk
@@ -9,6 +9,23 @@
$(eval $(call gb_CustomTarget_CustomTarget,desktop/soffice))
+ifeq ($(OS), MACOSX)
+
+ifeq (,$(ENABLE_RELEASE_BUILD))
+
+# Add entitlements if this is a non-release build. Just to be safe,
+# this target will always be run and MACOSX_CODESIGNING_IDENTITY is
+# set to empty as we don't want to sign $(INSTROOTBASE). Ignore
+# failures as it appears that setting only entitlements can fail
+# with certain macOS SDKs.
+$(call gb_CustomTarget_get_target,desktop/soffice) : \
+ $(INSTROOT)/$(LIBO_BIN_FOLDER)/soffice
+ -MACOSX_CODESIGNING_IDENTITY=
$(SRCDIR)/solenv/bin/macosx-codesign-app-bundle $(INSTROOTBASE)
+
+endif
+
+else
+
$(call gb_CustomTarget_get_target,desktop/soffice) : \
$(call gb_CustomTarget_get_workdir,desktop/soffice)/soffice.sh
@@ -25,4 +42,6 @@ else
endif
$(call gb_Trace_EndRange,$(subst $(WORKDIR)/,,$@),SED)
+endif
+
# vim:set shiftwidth=4 tabstop=4 noexpandtab:
diff --git a/desktop/Module_desktop.mk b/desktop/Module_desktop.mk
index fff879c83b0c..de56f3bd139f 100644
--- a/desktop/Module_desktop.mk
+++ b/desktop/Module_desktop.mk
@@ -46,7 +46,7 @@ $(eval $(call gb_Module_add_targets,desktop,\
Pagein_impress \
Pagein_writer \
) \
-$(if $(filter-out MACOSX WNT,$(OS)),CustomTarget_soffice) \
+$(if $(filter-out WNT,$(OS)),CustomTarget_soffice) \
))
ifeq ($(USING_X11),TRUE)
diff --git a/lo.xcent.in b/lo.xcent.in
index 4b7303876e6b..09a8df9b6fb5 100644
--- a/lo.xcent.in
+++ b/lo.xcent.in
@@ -23,5 +23,6 @@
@SDREMOTE_ENTITLEMENT@
@MACOSX_PROVISIONING_INFO@
+@GET_TASK_ALLOW_ENTITLEMENT@
diff --git a/solenv/bin/macosx-codesign-app-bundle
b/solenv/bin/macosx-codesign-app-bundle
index b1b17dbf7393..eceb5dd6 100755
--- a/solenv/bin/macosx-codesign-app-bundle
+++ b/solenv/bin/macosx-codesign-app-bundle
@@ -15,8 +15,7 @@ test $# = 1 || { echo Usage: $0 app-bundle; exit 1; }
for V in \
BUILDDIR \
-MACOSX_BUNDLE_IDENTIFIER \
-MACOSX_CODESIGNING_IDENTITY; do
+MACOSX_BUNDLE_IDENTIFIER; do
if test -z "$(eval echo '$'$V)"; then
echo No '$'$V "environment variable! This should be run in a build only"
exit 1
@@
[Libreoffice-commits] core.git: vcl/inc vcl/osx
vcl/inc/osx/a11yfactory.h|6
vcl/inc/osx/a11ywrapper.h| 16 +
vcl/inc/osx/salframeview.h | 44
vcl/inc/quartz/salgdi.h |2
vcl/osx/a11yactionwrapper.h |1
vcl/osx/a11yactionwrapper.mm | 19 +
vcl/osx/a11yfactory.mm | 57 -
vcl/osx/a11ywrapper.mm | 435 +--
vcl/osx/salframe.cxx |7
vcl/osx/salframeview.mm | 374
vcl/osx/salgdiutils.cxx | 36 +++
11 files changed, 918 insertions(+), 79 deletions(-)
New commits:
commit 75dc3a54fca8b2dc775ba007190d8c2e188f1c0a
Author: Patrick Luby
AuthorDate: Wed Jun 7 13:53:39 2023 -0400
Commit: Patrick Luby
CommitDate: Wed Jun 7 21:48:54 2023 +0200
Partial fix tdf#155376 use NSAccessibilityElement instead of NSView
On macOS, accessibility is implemented by creating a native NSView
for each C++ accessible element. The problem with using an NSView
for each element is that NSViews are very slow to add to or remove from
an NSWindow once the number of NSViews is more than a thousand or so.
Fortunately, Apple added a protocol that allows adding a native
accessible element using the lightweight NSAccessiblityElement class.
The topmost NSAccessiblityElement elements are connected to the single
SalFrameView in each NSWindow but since NSAccessiblityElements are not
NSViews, they are not connected to any of NSWindow's event or draw
dispatching. This makes NSAccessiblityElements significantly faster to
add to or remove from an NSWindow with no apparent loss in functionality.
Note: this change is a subset of the LibreOffice 4.4 code changes that I
wrote for NeoOffice.
Change-Id: I408108d57217db407512dfa3457fe26d2ab455de
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152717
Tested-by: Jenkins
Reviewed-by: Noel Grandin
Reviewed-by: Patrick Luby
diff --git a/vcl/inc/osx/a11yfactory.h b/vcl/inc/osx/a11yfactory.h
index cec49bf93b6d..9ef837dfaa9d 100644
--- a/vcl/inc/osx/a11yfactory.h
+++ b/vcl/inc/osx/a11yfactory.h
@@ -26,14 +26,14 @@
@interface AquaA11yFactory : NSObject
{
}
-+(void)insertIntoWrapperRepository: (NSView *) viewElement
forAccessibleContext: (css::uno::Reference <
css::accessibility::XAccessibleContext >) rxAccessibleContext;
++(void)insertIntoWrapperRepository: (AquaA11yWrapper *) element
forAccessibleContext: (css::uno::Reference <
css::accessibility::XAccessibleContext >) rxAccessibleContext;
+(AquaA11yWrapper *)wrapperForAccessible: (css::uno::Reference <
css::accessibility::XAccessible >) rxAccessible;
+(AquaA11yWrapper *)wrapperForAccessibleContext: (css::uno::Reference <
css::accessibility::XAccessibleContext >) rxAccessibleContext;
+(AquaA11yWrapper *)wrapperForAccessibleContext: (css::uno::Reference <
css::accessibility::XAccessibleContext >) rxAccessibleContext
createIfNotExists:(BOOL) bCreate;
+(AquaA11yWrapper *)wrapperForAccessibleContext: (css::uno::Reference <
css::accessibility::XAccessibleContext >) rxAccessibleContext
createIfNotExists:(BOOL) bCreate asRadioGroup:(BOOL) asRadioGroup;
+(void)removeFromWrapperRepositoryFor: (css::uno::Reference <
css::accessibility::XAccessibleContext >) rxAccessibleContext;
-+(void)registerView: (NSView *) theView;
-+(void)revokeView: (NSView *) theViewt;
++(void)registerWrapper: (AquaA11yWrapper *) theWrapper;
++(void)revokeWrapper: (AquaA11yWrapper *) theWrapper;
@end
diff --git a/vcl/inc/osx/a11ywrapper.h b/vcl/inc/osx/a11ywrapper.h
index 469e50820e19..1eb4039c57e9 100644
--- a/vcl/inc/osx/a11ywrapper.h
+++ b/vcl/inc/osx/a11ywrapper.h
@@ -50,7 +50,19 @@ struct ReferenceWrapper
css::uno::Reference < css::accessibility::XAccessibleTextMarkup >
rAccessibleTextMarkup;
};
-@interface AquaA11yWrapper : NSView
+@interface AquaA11yWrapper : NSAccessibilityElement
+
{
ReferenceWrapper maReferenceWrapper;
BOOL mActsAsRadioGroup;
@@ -68,6 +80,7 @@ struct ReferenceWrapper
-(id)accessibilityFocusedUIElement;
-(NSString *)accessibilityActionDescription:(NSString *)action;
-(void)accessibilityPerformAction:(NSString *)action;
+-(BOOL)performAction:(NSString *)action;
-(NSArray *)accessibilityActionNames;
-(id)accessibilityHitTest:(NSPoint)point;
// Attribute values
@@ -86,6 +99,7 @@ struct ReferenceWrapper
-(void)setActsAsRadioGroup:(BOOL)actsAsRadioGroup;
-(BOOL)actsAsRadioGroup;
-(NSWindow*)windowForParent;
+-(id)init;
-(id)initWithAccessibleContext: (css::uno::Reference <
css::accessibility::XAccessibleContext >) anAccessibleContext;
-(void) setDefaults: (css::uno::Reference <
css::accessibility::XAccessibleContext >) rxAccessibleContext;
+(void)setPopupMenuOpen:(BOOL)popupMenuOpen;
diff --git a/vcl/inc/osx/salframeview.h b/vcl/inc/osx/salframeview.h
index 1282eb10cbee..f9eca27e305c 100644
--- a/vcl/inc/osx/salframeview.h
+++ b/vcl/inc/osx/salframeview.h
@@ -70,11 +70,22 @@ enum class SalEvent;
[Libreoffice-bugs] [Bug 69515] FILEOPEN: Table in DOCX floating frame wrongly positioned (framePr ignored, regression)
https://bugs.documentfoundation.org/show_bug.cgi?id=69515 Gabor Kelemen (allotropia) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||7788 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137788] FILEOPEN DOCX: wrongly positioned block Table (not wrapped in w:p) framed via framePr with another paragraph
https://bugs.documentfoundation.org/show_bug.cgi?id=137788 Gabor Kelemen (allotropia) changed: What|Removed |Added CC||kelem...@ubuntu.com See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=69 ||515 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-qa] Minutes from the UX/design meeting 2023-Jun-07
Present: Eyal, John, Heiko Comments: Mike, Andre, Stuart Tickets/Topics * [Character styles] Make more clear that the font used is from the paragraph style + https://bugs.documentfoundation.org/show_bug.cgi?id=153623 + part of bug 88559 "Display of inherited attributes from parent styles in Styles dialog" (Mike) + visual clue that an attribute has not been explicitly set or unset is needed (Andre) + show an indicator on altered attributes (Eyal) + could be similar to system settings at KDE (Heiko) + not showing the actual attributes from the PS is a bug (Eyal, John) + changing the character format inline for multiple paragraphs empties the varying fields, which is easy to follow; otherwise it takes the value from the PS, again easy to understand => comment * WRITER: Can't define a character style for Regular font variant + https://bugs.documentfoundation.org/show_bug.cgi?id=155113 + starting from a PS with italic font, this attribute is taken into the CS and can be changed into regular, meaning it could be solved with the above (Heiko) + there are some reasons to create a CS not based on any PS (Eyal) + show the indicator in a greyed-out appearance if an attribute is changed and allow to make this sticky; clicking on the indicator toggles from on to off (removing individual attributes from a style) => easy to understand * Remove (or change functionality and label) of "Default" button in Styles tab of Insert Index dialog (see c1,c6,c7) + https://bugs.documentfoundation.org/show_bug.cgi?id=153653 + decision for c6 & c7 needed (renaming proposals) + make style selection likewise the B dialog (Eyal) + does not work as this dialog has way less attributes to assign => go with context menus and maybe a trashbin-symbol in the middle for the factory setting * I want to choose my Notebookbar without changing my whole User Interface + https://bugs.documentfoundation.org/show_bug.cgi?id=148123 + merits as MUFFIN proposal (Stuart) + power users may like this, average users don't need it (John) + if the UI is customized (Notebookbar + Toolbars) it should be persistent (John) + menubar on/off is remembered + low priority (Eyal) => fix the bug OpenPGP_signature Description: OpenPGP digital signature
Minutes from the UX/design meeting 2023-Jun-07
Present: Eyal, John, Heiko Comments: Mike, Andre, Stuart Tickets/Topics * [Character styles] Make more clear that the font used is from the paragraph style + https://bugs.documentfoundation.org/show_bug.cgi?id=153623 + part of bug 88559 "Display of inherited attributes from parent styles in Styles dialog" (Mike) + visual clue that an attribute has not been explicitly set or unset is needed (Andre) + show an indicator on altered attributes (Eyal) + could be similar to system settings at KDE (Heiko) + not showing the actual attributes from the PS is a bug (Eyal, John) + changing the character format inline for multiple paragraphs empties the varying fields, which is easy to follow; otherwise it takes the value from the PS, again easy to understand => comment * WRITER: Can't define a character style for Regular font variant + https://bugs.documentfoundation.org/show_bug.cgi?id=155113 + starting from a PS with italic font, this attribute is taken into the CS and can be changed into regular, meaning it could be solved with the above (Heiko) + there are some reasons to create a CS not based on any PS (Eyal) + show the indicator in a greyed-out appearance if an attribute is changed and allow to make this sticky; clicking on the indicator toggles from on to off (removing individual attributes from a style) => easy to understand * Remove (or change functionality and label) of "Default" button in Styles tab of Insert Index dialog (see c1,c6,c7) + https://bugs.documentfoundation.org/show_bug.cgi?id=153653 + decision for c6 & c7 needed (renaming proposals) + make style selection likewise the B dialog (Eyal) + does not work as this dialog has way less attributes to assign => go with context menus and maybe a trashbin-symbol in the middle for the factory setting * I want to choose my Notebookbar without changing my whole User Interface + https://bugs.documentfoundation.org/show_bug.cgi?id=148123 + merits as MUFFIN proposal (Stuart) + power users may like this, average users don't need it (John) + if the UI is customized (Notebookbar + Toolbars) it should be persistent (John) + menubar on/off is remembered + low priority (Eyal) => fix the bug OpenPGP_signature Description: OpenPGP digital signature
[Libreoffice-bugs] [Bug 155721] [FILEOPEN] ODS office:annotation color
https://bugs.documentfoundation.org/show_bug.cgi?id=155721 SheetJS changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from SheetJS --- 7.6.0 alpha1 uses the correct color -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155713] Text position in Dimension line dialog does not work as expected
https://bugs.documentfoundation.org/show_bug.cgi?id=155713 Regina Henschel changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||rb.hensc...@t-online.de --- Comment #1 from Regina Henschel --- I confirm the problem exists in Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 70fd835b4cf75e386ee115c705241a4059fb68a8 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded. I know that the problem exists in older versions, but I have currently no time to look for the oldest one. I could not find an existing bug report. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97161] Size of Dimension line objects in small scales are buggy
https://bugs.documentfoundation.org/show_bug.cgi?id=97161 --- Comment #10 from Regina Henschel --- An option is missing to set the two reference points of the dimension line is missing. Bug 145969 contains a proposal how to change and extend the "Position and Size" dialog to allow setting object specific values. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97161] Size of Dimension line objects in small scales are buggy
https://bugs.documentfoundation.org/show_bug.cgi?id=97161 Regina Henschel changed: What|Removed |Added CC||ville...@t-online.de --- Comment #9 from Regina Henschel --- *** Bug 141382 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 141382] Dimension line width is displayed incorrectly in Position and Size dialog after using the dialog to adjust it
https://bugs.documentfoundation.org/show_bug.cgi?id=141382 --- Comment #6 from Regina Henschel --- *** This bug has been marked as a duplicate of bug 97161 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141382] Dimension line width is displayed incorrectly in Position and Size dialog after using the dialog to adjust it
https://bugs.documentfoundation.org/show_bug.cgi?id=141382 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #5 from Regina Henschel --- The 'Position and Size' dialog does not show the distance between the reference points of the dimension line but the position and size of the bounding box of the object, including the text. An option to set the reference points directly is missing. *** This bug has been marked as a duplicate of bug 97191 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135431] Position and Size of dimension lines depend on each other
https://bugs.documentfoundation.org/show_bug.cgi?id=135431 Regina Henschel changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #7 from Regina Henschel --- I collect all similar reports to bug 97161 to make the problem better visible. *** This bug has been marked as a duplicate of bug 97161 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97161] Size of Dimension line objects in small scales are buggy
https://bugs.documentfoundation.org/show_bug.cgi?id=97161 --- Comment #8 from Regina Henschel --- *** Bug 135431 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 155721] [FILEOPEN] ODS office:annotation color
https://bugs.documentfoundation.org/show_bug.cgi?id=155721 Maxim Monastirsky changed: What|Removed |Added CC||momonas...@gmail.com --- Comment #2 from Maxim Monastirsky --- Should be fixed already by commit 0ee9501c0b7dc1a291715fff9c1934b1c08cb654. Please retest with a recent 7.6/master build. -- You are receiving this mail because: You are the assignee for the bug.
