[Libreoffice-bugs] [Bug 86209] MENUS: Reorganize the View menu
https://bugs.documentfoundation.org/show_bug.cgi?id=86209 --- Comment #18 from Monique Balansag --- Thanks for the codes. https://www.abileneconcretepros.com/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103494] [META] Textbox bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103494 BogdanB changed: What|Removed |Added Depends on||146867 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=146867 [Bug 146867] When adding a text box to eventually create a fillable pdf, the font specified in control properties -- font are not properly exported -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146867] When adding a text box to eventually create a fillable pdf, the font specified in control properties -- font are not properly exported
https://bugs.documentfoundation.org/show_bug.cgi?id=146867 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||103494 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103494 [Bug 103494] [META] Textbox bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107237] [META] Notebookbar Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=107237 BogdanB changed: What|Removed |Added Depends on||132816 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=132816 [Bug 132816] Slide "master" option buttons are not updated in tabbed ui -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103460] [META] Master Slides deck/tab of the sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=103460 BogdanB changed: What|Removed |Added Depends on||132816 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=132816 [Bug 132816] Slide "master" option buttons are not updated in tabbed ui -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132816] Slide "master" option buttons are not updated in tabbed ui
https://bugs.documentfoundation.org/show_bug.cgi?id=132816 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||107237, 103460 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103460 [Bug 103460] [META] Master Slides deck/tab of the sidebar https://bugs.documentfoundation.org/show_bug.cgi?id=107237 [Bug 107237] [META] Notebookbar Tabbed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102847] [META] Quick Find, Search and Replace
https://bugs.documentfoundation.org/show_bug.cgi?id=102847 BogdanB changed: What|Removed |Added Depends on||149007 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=149007 [Bug 149007] Search for scientific format fails -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149007] Search for scientific format fails
https://bugs.documentfoundation.org/show_bug.cgi?id=149007 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||102847 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102847 [Bug 102847] [META] Quick Find, Search and Replace -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112182] [META] Text and object selection issues
https://bugs.documentfoundation.org/show_bug.cgi?id=112182 BogdanB changed: What|Removed |Added Depends on||93540 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=93540 [Bug 93540] Selection tool moves selection -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93540] Selection tool moves selection
https://bugs.documentfoundation.org/show_bug.cgi?id=93540 BogdanB changed: What|Removed |Added Blocks||112182 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=112182 [Bug 112182] [META] Text and object selection issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129294] [META] Variable field bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=129294 BogdanB changed: What|Removed |Added Depends on||128041 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=128041 [Bug 128041] Show variable behaves differently to hide text depending on variable -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128041] Show variable behaves differently to hide text depending on variable
https://bugs.documentfoundation.org/show_bug.cgi?id=128041 BogdanB changed: What|Removed |Added Blocks||129294 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=129294 [Bug 129294] [META] Variable field bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 BogdanB changed: What|Removed |Added Depends on||149948 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=149948 [Bug 149948] Frozen logo on first start when "The Bat" email program started before -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149948] Frozen logo on first start when "The Bat" email program started before
https://bugs.documentfoundation.org/show_bug.cgi?id=149948 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||133092 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=133092 [Bug 133092] [META] Crash bugs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156802] New: UI Feature Request: Possibility to hide a page like in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=156802 Bug ID: 156802 Summary: UI Feature Request: Possibility to hide a page like in Impress Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: j.tdhgf...@nurfuerspam.de Description: I would like to hide a page in Draw similar how I can hide a slide in Impress. I use Draw to design fliers and I like to keep different versions of a page in the document for reference. Sometime later often I'll need a particular variation again. So it would be handy to hide the pages I don’t want to print at the moment. Steps to Reproduce: 1. Create a document with several similiar pages 2. Want to indicate that a certain page is not the recent version Actual Results: It's not possible to do this by hiding a page like I can do in Impress. Expected Results: There is an option to a hide a page in the page pane like there is in Impress. A hidden page should be displayed there the same as in Impress: With diagonal gray bars Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.utf-8); UI: de-DE Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103494] [META] Textbox bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103494 BogdanB changed: What|Removed |Added Depends on||136998 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=136998 [Bug 136998] Paragraph line spacing incorrect after saving in a new version -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107833] [META] Writer paragraph style bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107833 BogdanB changed: What|Removed |Added Depends on||136998 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=136998 [Bug 136998] Paragraph line spacing incorrect after saving in a new version -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136998] Paragraph line spacing incorrect after saving in a new version
https://bugs.documentfoundation.org/show_bug.cgi?id=136998 BogdanB changed: What|Removed |Added Summary|string interval incorrect |Paragraph line spacing |after saving in new version |incorrect after saving in a ||new version Blocks||103494, 107833 CC||buzea.bog...@libreoffice.or ||g --- Comment #6 from BogdanB --- Repro in Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b4cbf44e8d5072e79b62e6b4e3b1c2480e4a34f3 CPU threads: 16; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103494 [Bug 103494] [META] Textbox bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=107833 [Bug 107833] [META] Writer paragraph style bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103266] [META] Command line bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103266 BogdanB changed: What|Removed |Added Depends on||132113 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=132113 [Bug 132113] Opening PPS or PPSX slideshow using -o command line, the slideshow still opens in --show mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132113] Opening PPS or PPSX slideshow using -o command line, the slideshow still opens in --show mode
https://bugs.documentfoundation.org/show_bug.cgi?id=132113 BogdanB changed: What|Removed |Added Blocks||103266 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103266 [Bug 103266] [META] Command line bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122755] [META] Formulae in Writer tables bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=122755 BogdanB changed: What|Removed |Added Depends on||137764 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=137764 [Bug 137764] New Writer formula functions should use dedicated namespace in ODF -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137764] New Writer formula functions should use dedicated namespace in ODF
https://bugs.documentfoundation.org/show_bug.cgi?id=137764 BogdanB changed: What|Removed |Added Blocks||122755 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=122755 [Bug 122755] [META] Formulae in Writer tables bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107810] [META] OLE/Embedded object bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107810 BogdanB changed: What|Removed |Added Depends on||145636 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=145636 [Bug 145636] Render empty shapes and objects to show and export the color background -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145636] Render empty shapes and objects to show and export the color background
https://bugs.documentfoundation.org/show_bug.cgi?id=145636 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||107810 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107810 [Bug 107810] [META] OLE/Embedded object bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143781] [META] Development- and code-related bug reports and tasks
https://bugs.documentfoundation.org/show_bug.cgi?id=143781 BogdanB changed: What|Removed |Added Depends on||153825 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153825 [Bug 153825] Unable to create com.sun.star.text.ChainedTextFrame service -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153825] Unable to create com.sun.star.text.ChainedTextFrame service
https://bugs.documentfoundation.org/show_bug.cgi?id=153825 BogdanB changed: What|Removed |Added Summary|Unable to create|Unable to create |com.sun.star.text.ChainedTe |com.sun.star.text.ChainedTe |xtFrame service.|xtFrame service Blocks||143781 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143781 [Bug 143781] [META] Development- and code-related bug reports and tasks -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108254] [META] File format filters (import/export) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108254 BogdanB changed: What|Removed |Added Depends on||135303 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=135303 [Bug 135303] Bitmap Export: Export color bitmap(.bmp) in spite of setting 4bit grayscale -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135303] Bitmap Export: Export color bitmap(.bmp) in spite of setting 4bit grayscale
https://bugs.documentfoundation.org/show_bug.cgi?id=135303 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||108254 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108254 [Bug 108254] [META] File format filters (import/export) bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113335] [META] XLSX (OOXML) hyperlink bug tracker
https://bugs.documentfoundation.org/show_bug.cgi?id=113335 BogdanB changed: What|Removed |Added Depends on||150229 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=150229 [Bug 150229] Links in cells truncated when saved/re-opened (xlxs format) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150229] Links in cells truncated when saved/re-opened (xlxs format)
https://bugs.documentfoundation.org/show_bug.cgi?id=150229 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||113335 Keywords||filter:xlsx Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=113335 [Bug 113335] [META] XLSX (OOXML) hyperlink bug tracker -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 BogdanB changed: What|Removed |Added Depends on||148314 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148314 [Bug 148314] ODS corrupted after crash, not calculating properly -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107659] [META] Macro bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107659 BogdanB changed: What|Removed |Added Depends on||148314 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148314 [Bug 148314] ODS corrupted after crash, not calculating properly -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148314] ODS corrupted after crash, not calculating properly
https://bugs.documentfoundation.org/show_bug.cgi?id=148314 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||133092, 107659 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107659 [Bug 107659] [META] Macro bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=133092 [Bug 133092] [META] Crash bugs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155757] Support Color Filter in "Standard Filter" dialog enhancement - missing background colors choice in filter field. UI not English
https://bugs.documentfoundation.org/show_bug.cgi?id=155757
--- Comment #18 from Aron Budea ---
As I can see the problem here is caused by two instances of the text
"Background color" that are capitalized differently in the French translation.
1. The string SCSTR_FILTER_BACKGROUND_COLOR_COND:
#define SCSTR_FILTER_BACKGROUND_COLOR_COND
NC_("STANDARDFILTERDIALOG_COND", "Background color")
https://opengrok.libreoffice.org/xref/core/sc/inc/strings.hrc?r=bb5e0368#43
Translated as: "Couleur d'arrière-plan"
https://translations.documentfoundation.org/translate/libo_ui-master/scmessages/fr/?checksum=54fb1a3892885776_by=-priority,position
source string description: sGJCz
There's even a comment in the .hrc file:
// This must match the translation of the same strings of
standardfilterdialog|cond
2. Items in standardfilterdialog.ui
Background
color
https://opengrok.libreoffice.org/xref/core/sc/uiconfig/scalc/ui/standardfilterdialog.ui?r=12606799#434
https://opengrok.libreoffice.org/xref/core/sc/uiconfig/scalc/ui/standardfilterdialog.ui?r=12606799#473
https://opengrok.libreoffice.org/xref/core/sc/uiconfig/scalc/ui/standardfilterdialog.ui?r=12606799#512
https://opengrok.libreoffice.org/xref/core/sc/uiconfig/scalc/ui/standardfilterdialog.ui?r=12606799#551
Translated as: "Couleur d'Arrière-plan"
https://translations.documentfoundation.org/translate/libo_ui-master/scmessages/fr/?checksum=c4ed5542833dcf1c_by=-priority,position
source string description: 5Wa7m
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100366] [META] Impress/Draw table bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=100366 BogdanB changed: What|Removed |Added Depends on||151296 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151296 [Bug 151296] FILESAVE: Table new cell contents are not saved if empty -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151296] FILESAVE: Table new cell contents are not saved if empty
https://bugs.documentfoundation.org/show_bug.cgi?id=151296 BogdanB changed: What|Removed |Added Blocks||100366 Summary|FILESAVE: table new cell|FILESAVE: Table new cell |contents are not saved if |contents are not saved if |empty |empty CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=100366 [Bug 100366] [META] Impress/Draw table bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142695] Add info about double-click making commands sticky to all affected commands' tooltips
https://bugs.documentfoundation.org/show_bug.cgi?id=142695 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||143781 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143781 [Bug 143781] [META] Development- and code-related bug reports and tasks -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143781] [META] Development- and code-related bug reports and tasks
https://bugs.documentfoundation.org/show_bug.cgi?id=143781 BogdanB changed: What|Removed |Added Depends on||142695 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=142695 [Bug 142695] Add info about double-click making commands sticky to all affected commands' tooltips -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146192] Extrusion-viewpoint value (3472, -3472, 25000) is not written to file, although it is not default value
https://bugs.documentfoundation.org/show_bug.cgi?id=146192 BogdanB changed: What|Removed |Added Summary|extrusion-viewpoint value |Extrusion-viewpoint value |(3472, -3472, 25000) is not |(3472, -3472, 25000) is not |written to file, although |written to file, although |it is not default value |it is not default value CC||buzea.bog...@libreoffice.or ||g Blocks||103759 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103759 [Bug 103759] [META] 3D model bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103759] [META] 3D model bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103759 BogdanB changed: What|Removed |Added Depends on||146192 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=146192 [Bug 146192] Extrusion-viewpoint value (3472, -3472, 25000) is not written to file, although it is not default value -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109362] [META] Custom/object animation bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109362 BogdanB changed: What|Removed |Added Depends on||151769 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151769 [Bug 151769] Text disappearing from slide after saving presentation with animation -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151769] Text disappearing from slide after saving presentation with animation
https://bugs.documentfoundation.org/show_bug.cgi?id=151769 BogdanB changed: What|Removed |Added Blocks||109362 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=109362 [Bug 109362] [META] Custom/object animation bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100288] First line after inserted picture is not justified
https://bugs.documentfoundation.org/show_bug.cgi?id=100288 BogdanB changed: What|Removed |Added Blocks||107833 Summary|first line after inserted |First line after inserted |picture is not justified|picture is not justified CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107833 [Bug 107833] [META] Writer paragraph style bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107833] [META] Writer paragraph style bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107833 BogdanB changed: What|Removed |Added Depends on||100288 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=100288 [Bug 100288] First line after inserted picture is not justified -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: vcl/source
vcl/source/treelist/svtabbx.cxx | 10 +++--- 1 file changed, 7 insertions(+), 3 deletions(-) New commits: commit e59c026c561da4ae0b9bd1a33fcee3fbc724dece Author: Michael Weghorn AuthorDate: Thu Aug 17 17:25:47 2023 +0200 Commit: Michael Weghorn CommitDate: Fri Aug 18 06:06:07 2023 +0200 vcl a11y: Fix nullptr deref in SvHeaderTabListBox::calcHeaderRect While working on tdf#156561 and tdf#141101, I experienced a crash with the below backtrace on Windows at some point. Potentially a regression from: commit 0e8b7dd7a013dffe080148baac926a698f36ad85 Date: Wed Jul 19 15:19:28 2023 +0200 split GetWindowExtentsRelative asunder Use the `GetWindowExtentsAbsolute` variant when screen coordinates are wanted, as is done elsewhere since the above commit. Backtrace: 1 std::unique_ptr>::operator-> memory 3295 0x7fffa807a02a 2 vcl::Window::GetWindowExtentsRelative window.cxx 2953 0x7fffa82b7132 3 SvHeaderTabListBox::calcHeaderRect svtabbx.cxx 771 0x7fffa850a1a6 4 accessibility::AccessibleBrowseBoxHeaderBar::implGetBoundingBoxOnScreen AccessibleBrowseBoxHeaderBar.cxx 311 0x7fffa41b2728 5 accessibility::AccessibleBrowseBoxBase::getBoundingBoxOnScreen AccessibleBrowseBoxBase.cxx 408 0x7fffa41ada97 6 accessibility::AccessibleBrowseBoxBase::getLocationOnScreen AccessibleBrowseBoxBase.cxx 228 0x7fffa41ae134 7 CMAccessible::accHitTest MAccessible.cxx 988 0x7fffbf8d7fad 8 NdrSendReceive RPCRT40x7ff81155b4b3 9 NdrSendReceive RPCRT40x7ff81155a282 10 NdrStubCall2 RPCRT40x7ff8114fe1ca 11 NdrStubCall3 RPCRT40x7ff8114fd494 12 CStdStubBuffer_Invoke combase 0x7ff812295f1c 13 CStdStubBuffer_Invoke RPCRT40x7ff81153a74b 14 CoWaitForMultipleHandles combase 0x7ff81226bad3 15 CoWaitForMultipleHandles combase 0x7ff81226b85e 16 HSTRING_UserSize combase 0x7ff81229aaa6 17 RoGetActivatableClassRegistration combase 0x7ff812211283 18 CoWaitForMultipleHandles combase 0x7ff812269d7d 19 SetErrorInfo combase 0x7ff812205036 20 CoMarshalInterface combase 0x7ff8122635fa 21 CallWindowProcW USER320x7ff8126be858 22 DispatchMessageW USER320x7ff8126be299 23 ImplSalDispatchMessage salinst.cxx 474 0x7fffa48301d8 24 ImplSalYield salinst.cxx 551 0x7fffa48308fd 25 WinSalInstance::DoYield salinst.cxx 580 0x7fffa482fe01 26 ImplYield svapp.cxx352 0x7fffa891790d 27 Application::Yield svapp.cxx437 0x7fffa891b862 28 Application::Execute svapp.cxx330 0x7fffa8914c4a 29 desktop::Desktop::Main app.cxx 1601 0x7fffc71696b2 30 ImplSVMain svmain.cxx 204 0x7fffa892d08c 31 SVMain
[Libreoffice-commits] core.git: include/vcl vcl/source
include/vcl/vclenum.hxx|3 +--
vcl/source/window/dockmgr.cxx | 20
vcl/source/window/floatwin.cxx | 15 ---
3 files changed, 5 insertions(+), 33 deletions(-)
New commits:
commit 230789766b364bf995e6659dd589cdf902c69f2c
Author: Michael Weghorn
AuthorDate: Thu Aug 17 15:39:10 2023 +0200
Commit: Michael Weghorn
CommitDate: Fri Aug 18 06:05:49 2023 +0200
tdf#156561 tdf#141101 Revert "tdf#140762 tdf#152671 Make dock win ..." et al
Revert
commit dc0706cabfe39ddb6ea23d60ccfb756f2b9e6efb
Author: Michael Weghorn
Date: Wed Mar 15 17:00:27 2023 +0100
tdf#140762 tdf#152671 Make dock win visible before showing popup
and 2 follow-up commits, since it's no longer necessary to
have the window visible already when the popup shows in order
for NVDA on Windows to announce the content.
This unifies the code path between gtk and non-gtk again,
as already pointed out in
commit 3bb762c53ea79f8915a1b8fa39f3f5f57aa68c84
Date: Tue Aug 1 09:44:56 2023 +0200
tdf#156100 tdf#156561 Revert to previous behavior for gtk popups
> Further analysis of the root causes is planned in the context of
> tdf#156561, so hopefully the code paths can be unified again in
> the future.
The underlying issues have now been addressed by these
commits instead now:
commit 1d92445fcac1c51c17d8dbfd1a4017430fe7bc46
Author: Michael Weghorn
Date: Tue Aug 1 09:26:37 2023 +0100
tdf#156561 wina11y: Handle CHILD event
Change-Id I83cf5732bfc9d4886e4f7fa75d4ff462e4d4af6d
tdf#141101 tdf#156561 a11y: Handle a11y child events in win parent
Change-Id I69c6066127c8b853a27cc1f692f139572541f8eb
tdf#156561 a11y: Create VCLXTopWindow peer for border win frame
Change-Id If374032387babf41b28067d5df54d5f6ce682c48
tdf#156561 a11y: Don't ignore child events in AccessibleListBox
Change-Id Ifbe27de01739103d1da04951475db32aa50d429d
tdf#156561 svtools, a11y: Return created popup win for focus handling
Together with the above-mentioned commits, this also makes NVDA
announce the font color popup in the "Character" (character style)
dialog. (Announcement starts as soon as Tab is pressed once,
not yet for the initially focused item right away.)
Reverted commits:
commit 3bb762c53ea79f8915a1b8fa39f3f5f57aa68c84
Date: Tue Aug 1 09:44:56 2023 +0200
tdf#156100 tdf#156561 Revert to previous behavior for gtk popups
commit 70642bb7afd2cee6f7ae6eff2936a35978bd0597
Date: Thu Apr 6 15:07:15 2023 +0100
tdf#154470 try moving the Show of the client to after the float
positioning
commit dc0706cabfe39ddb6ea23d60ccfb756f2b9e6efb
Date: Wed Mar 15 17:00:27 2023 +0100
tdf#140762 tdf#152671 Make dock win visible before showing popup
Change-Id: Ic621b4344311679af2d13b5a80220e1daf411061
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155803
Tested-by: Jenkins
Reviewed-by: Michael Weghorn
diff --git a/include/vcl/vclenum.hxx b/include/vcl/vclenum.hxx
index 4b754d1b66b1..5ea0c77127d6 100644
--- a/include/vcl/vclenum.hxx
+++ b/include/vcl/vclenum.hxx
@@ -333,11 +333,10 @@ enum class FloatWinPopupFlags
NoMouseUpClose = 0x000200,
GrabFocus= 0x000400,
NoHorzPlacement = 0x000800,
-MakeClientWindowVisibleBeforePopup = 0x001000,
};
namespace o3tl
{
-template<> struct typed_flags :
is_typed_flags {};
+template<> struct typed_flags :
is_typed_flags {};
}
// Flags for Window::Show()
diff --git a/vcl/source/window/dockmgr.cxx b/vcl/source/window/dockmgr.cxx
index cc122a71dd0d..ba9aa2aa9450 100644
--- a/vcl/source/window/dockmgr.cxx
+++ b/vcl/source/window/dockmgr.cxx
@@ -821,21 +821,8 @@ void ImplDockingWindowWrapper::StartPopupMode( ToolBox
*pParentToolBox, FloatWin
if( pParentToolBox->IsKeyEvent() )
nFlags |= FloatWinPopupFlags::GrabFocus;
-// tdf#140762, tdf#152671, tdf#154470, tdf#156100: Without client window
being visible
-// before showing popup, at least NVDA on Windows does not announce items
in the popup,
-// so make the client window visible first. This is problematic for gtk
VCL plugins though,
-// so don't do it there and use different code paths for now.
-// For further analysis of the root causes, there's tdf#156561.
-const OUString sToolkit = Application::GetToolkitName();
-if (sToolkit == "gtk3" || sToolkit == "gtk4")
-{
-mpFloatWin->StartPopupMode( pParentToolBox, nFlags);
-GetWindow()->Show();
-}
-else
-{
-mpFloatWin->StartPopupMode( pParentToolBox, nFlags |
FloatWinPopupFlags::MakeClientWindowVisibleBeforePopup);
-}
+
[Libreoffice-commits] core.git: 2 commits - accessibility/inc accessibility/source svtools/source
accessibility/inc/extended/accessiblelistbox.hxx|1 - accessibility/source/extended/accessiblelistbox.cxx | 19 --- svtools/source/uno/popupwindowcontroller.cxx|1 + 3 files changed, 1 insertion(+), 20 deletions(-) New commits: commit e8028cbc11661effbb38ecb6146b9a9557b650da Author: Michael Weghorn AuthorDate: Thu Aug 17 14:12:56 2023 +0100 Commit: Michael Weghorn CommitDate: Fri Aug 18 06:05:40 2023 +0200 tdf#156561 svtools, a11y: Return created popup win for focus handling Actually return the popup window created in `PopupWindowController::createPopupWindow` instead of just an empty reference. With this in place, the popup window is initially announced by NVDA on Windows for the "Borders" toolbar item when expanded even after reverting commit dc0706cabfe39ddb6ea23d60ccfb756f2b9e6efb Author: Michael Weghorn Date: Wed Mar 15 17:00:27 2023 +0100 tdf#140762 tdf#152671 Make dock win visible before showing popup , because the focus event is now sent when focus is set via `XWindow::setFocus` in `framework::ToolBarManager::OnDropdownClick` (s. frame 41 below), while the above commit previously ensured that the window was already visible earlier and thus the corresponding event would be sent earlier already. Related backtrace for the winaccessibility case: 1 AccObjectWinManager::NotifyAccEvent AccObjectWinManager.cxx 185 0x7fffaac46118 2 AccComponentEventListener::FireStateFocusedChange AccComponentEventListener.cxx 308 0x7fffaac4fddb 3 AccComponentEventListener::SetComponentState AccComponentEventListener.cxx 171 0x7fffaac50c14 4 AccEventListener::HandleStateChangedEvent AccEventListener.cxx 166 0x7fffaac4ea44 5 AccEventListener::notifyEvent AccEventListener.cxx 72 0x7fffaac4faaa 6 AccComponentEventListener::notifyEvent AccComponentEventListener.cxx 82 0x7fffaac5123c 7 AccDescendantManagerEventListener::notifyEvent AccDescendantManagerEventListener.cxx 70 0x7fffaac56686 8 AccListEventListener::notifyEvent AccListEventListener.cxx 66 0x7fffaac56ca2 9 ValueSetAcc::FireAccessibleEvent valueacc.cxx 430 0x7fffbad4578d 10 ValueSetAcc::GetFocus valueacc.cxx 452 0x7fffbad458ed 11 ValueSet::GetFocusvalueset.cxx 271 0x7fffbad4f6b8 12 weld::CustomWeld::DoGetFocus customweld.cxx 72 0x7fffaf12b2ed 13 weld::CustomWeld::LinkStubDoGetFocus customweld.cxx 72 0x7fffaf12b726 14 Link::Call link.hxx 111 0x7fffaf16be63 15 SalInstanceWidget::HandleEventListenersalvtables.cxx 736 0x7fffaf16f436 16 SalInstanceDrawingArea::HandleEventListener salvtables.cxx 6167 0x7fffaf16f3c7 17 SalInstanceWidget::EventListener salvtables.cxx 824 0x7fffaf16e805 18 SalInstanceWidget::LinkStubEventListener salvtables.cxx 821 0x7fffaf170b86 19 Link::Call link.hxx 111 0x7fffaea625c3 20 vcl::Window::CallEventListeners event.cxx 263 0x7fffaea62970 21 vcl::Window::PreNotifyevent.cxx 71 0x7fffaea649a3 22 vcl::Window::CompatPreNotify window.cxx 3921 0x7fffaeb730e8 23 ImplCallPreNotify winproc.cxx 70 0x7fffaeb8eb00 24 vcl::Window::ImplGrabFocusmouse.cxx 383 0x7fffaeacff8c 25 vcl::Window::ImplControlFocus dlgctrl.cxx 560 0x7fffaea391b6 26 vcl::Window::EventNotify event.cxx 210 0x7fffaea633a5 27 DockingWindow::EventNotifydockwin.cxx 528 0x7fffaea58d21 28 vcl::Window::CompatNotify window.cxx 3929 0x7fffaeb73058 29 vcl::Window::GetFocus window.cxx 1852 0x7fffaeb75e94 30 InterimToolbarPopup::GetFocus toolbarmenu.cxx 187
[Libreoffice-commits] core.git: 2 commits - toolkit/source
toolkit/source/awt/vclxaccessiblecomponent.cxx |8 +++-
toolkit/source/helper/unowrapper.cxx |7 +++
2 files changed, 14 insertions(+), 1 deletion(-)
New commits:
commit 2cd1408dd7d6688357257f4a58a8b467628b1884
Author: Michael Weghorn
AuthorDate: Thu Aug 17 13:15:46 2023 +0100
Commit: Michael Weghorn
CommitDate: Fri Aug 18 06:05:23 2023 +0200
tdf#156561 a11y: Create VCLXTopWindow peer for border win frame
If a border window is a "native frame", i.e. a top level
window, then also create a `VCLXTopWindow` for it instead
of just a simple `VCLXWindow`.
This also addresses another cause why the Calc autofilter
popup would not be announced by the NVDA screen reader
before
commit dc0706cabfe39ddb6ea23d60ccfb756f2b9e6efb
Author: Michael Weghorn
Date: Wed Mar 15 17:00:27 2023 +0100
tdf#140762 tdf#152671 Make dock win visible before showing popup
For winaccessibility, an accessible event listener
is registered for an object when either
`AccTopWindowListener::windowOpened` gets an event
with the top level window set or the parent of
the window sends an `AccessibleEventId::CHILD` event
for the child object.
In case of the autofilter popup in Calc, the top-level
border window of the work window (created and set in
`WorkWindow::ImplInit` and retrieved via `Window::GetFrameWeld`
in `ScGridWindow::LaunchAutoFilterMenu`) is set as the
parent window of the popup, but since it is a top-level
window and was so far not considered as such due to its
peer/component interface not implementing `XTopWindow`
(s. `Window::IsTopWindow` and the corresponding check
in `VCLXToolkit::callTopWindowListeners`), it would
not have any accessible listener set, and thus no
child event for its new popup child would be sent
to the winaccessibility layer. Therefore, no
accessible events would be sent for the popup
and it's children either, resulting in NVDA not
announcing any focus changes, etc.
With this change in place, NVDA announces focused
items in the auto filter popup even with a revert
of the above-mentioned commit (and follow-up commits),
except for submenu entries (which still suffer from
another problem that will be addressed separately).
Change-Id: I69c6066127c8b853a27cc1f692f139572541f8eb
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155800
Tested-by: Jenkins
Reviewed-by: Michael Weghorn
diff --git a/toolkit/source/helper/unowrapper.cxx
b/toolkit/source/helper/unowrapper.cxx
index e2aaa55dbe63..82b4dd17338a 100644
--- a/toolkit/source/helper/unowrapper.cxx
+++ b/toolkit/source/helper/unowrapper.cxx
@@ -91,6 +91,13 @@ static rtl::Reference CreateXWindow( vcl::Window
const * pWindow )
case WindowType::HEADERBAR: return new VCLXHeaderBar;
+case WindowType::BORDERWINDOW:
+{
+if (pWindow->IsNativeFrame())
+return new VCLXTopWindow;
+return new VCLXWindow(true);
+}
+
// case WindowType::FIXEDLINE:
// case WindowType::FIXEDBITMAP:
// case WindowType::DATEBOX:
commit 4d27d2c5f9d83112b6db9b6234e2ae617ffced22
Author: Michael Weghorn
AuthorDate: Thu Aug 17 11:51:11 2023 +0100
Commit: Michael Weghorn
CommitDate: Fri Aug 18 06:05:14 2023 +0200
tdf#141101 tdf#156561 a11y: Handle a11y child events in win parent
`VCLXAccessibleComponent::ProcessWindowChildEvent` was only
processing `WindowShow` and `WindowHide` events when the
`vcl::Window::GetAccessibleParent()` for the window sent in
the event would return the window that the `VCLXAccessibleComponent`
refers to.
This generally seems reasonable, but when the child events
are sent for the corresponding window, the window's hierarchy
is iterated over using `vcl::Window::GetParent()`, so if the
accessible window is not in that hierarchy, no window would
take care of the child events.
(Note e.g. how `Window::GetParent` uses `mpWindowImpl->mpRealParent`
while `Window::getAccessibleParentWindow` uses `mpWindowImpl->mpParent`
and has some special handling.)
Due to the way that `ImplDockingWindowWrapper::ImplPreparePopupMode`
reparents the windows, this is at least the case for the auto
filter popup in Calc and the font color popup in Writer's "Character"
dialog, so the `VclEventId::WindowShow` event would not be forwarded
to the a11y layer as an `AccessibleEventId::CHILD` event, and thus no
listener would be registered for the children. As a result, the NVDA
screen reader would not announce these objects when they receive
focus.
Make sure that the child event gets handled by making
`VCLXAccessibleComponent::GetChildAccessible` also take
into account the `vcl::Window::GetParent()`.
This
[Libreoffice-bugs] [Bug 141101] The font color popup is not accessible to screen readers on Windows
https://bugs.documentfoundation.org/show_bug.cgi?id=141101 Michael Weghorn changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |m.wegh...@posteo.de |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103479] [META] Word and character count bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103479 BogdanB changed: What|Removed |Added Depends on||156801 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156801 [Bug 156801] Inconsistent updating of selected character count -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156801] Inconsistent updating of selected character count
https://bugs.documentfoundation.org/show_bug.cgi?id=156801 BogdanB changed: What|Removed |Added Blocks||103479 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103479 [Bug 103479] [META] Word and character count bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: 3 commits - include/vcl vcl/source
include/vcl/window.hxx |2 +-
vcl/source/window/accessibility.cxx | 22 +++---
vcl/source/window/brdwin.cxx|9 +++--
vcl/source/window/window.cxx|2 +-
vcl/source/window/window2.cxx | 12
5 files changed, 20 insertions(+), 27 deletions(-)
New commits:
commit eb812cb94f20dd04fa4cf3ec89df8bb813811359
Author: Michael Weghorn
AuthorDate: Wed Aug 16 19:07:54 2023 +0200
Commit: Michael Weghorn
CommitDate: Fri Aug 18 06:04:44 2023 +0200
Rename Window::ImplIsAccessibleNativeFrame and make it public
The way to determine whether this window is a "native frame"
doesn't look particularly specific to a11y, so rename it
to just `Window::IsNativeFrame` and make it public in order
to reuse it in a follow-up commit.
Also move the implementation out of the source file that
implements accessibility-specific Window methods for
consistency.
Change-Id: I980f251cacce6a601e86fc6261a231b799b30317
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155798
Tested-by: Jenkins
Reviewed-by: Michael Weghorn
diff --git a/include/vcl/window.hxx b/include/vcl/window.hxx
index 2d64be451370..0f9c6f3f45b5 100644
--- a/include/vcl/window.hxx
+++ b/include/vcl/window.hxx
@@ -779,6 +779,7 @@ public:
boolIsDialog() const;
boolIsMenuFloatingWindow() const;
boolIsToolbarFloatingWindow() const;
+boolIsNativeFrame() const;
boolIsTopWindow() const;
SystemWindow* GetSystemWindow() const;
@@ -1187,7 +1188,6 @@ protected:
private:
SAL_DLLPRIVATE bool ImplIsAccessibleCandidate() const;
-SAL_DLLPRIVATE bool ImplIsAccessibleNativeFrame() const;
///@}
/*
diff --git a/vcl/source/window/accessibility.cxx
b/vcl/source/window/accessibility.cxx
index 0656720b6986..3c6103ac31d9 100644
--- a/vcl/source/window/accessibility.cxx
+++ b/vcl/source/window/accessibility.cxx
@@ -95,24 +95,12 @@ bool Window::ImplIsAccessibleCandidate() const
if( !mpWindowImpl->mbBorderWin )
return true;
-return ImplIsAccessibleNativeFrame();
-}
-
-bool Window::ImplIsAccessibleNativeFrame() const
-{
-if( mpWindowImpl->mbFrame )
-// #101741 do not check for WB_CLOSEABLE because undecorated floaters
(like menus!) are closeable
-if( mpWindowImpl->mnStyle & (WB_MOVEABLE | WB_SIZEABLE) )
-return true;
-else
-return false;
-else
-return false;
+return IsNativeFrame();
}
vcl::Window* Window::GetAccessibleParentWindow() const
{
-if (!mpWindowImpl || ImplIsAccessibleNativeFrame())
+if (!mpWindowImpl || IsNativeFrame())
return nullptr;
vcl::Window* pParent = mpWindowImpl->mpParent;
@@ -327,7 +315,7 @@ sal_uInt16 Window::getDefaultAccessibleRole() const
case WindowType::BORDERWINDOW:
case WindowType::SYSTEMCHILDWINDOW:
default:
-if (ImplIsAccessibleNativeFrame() )
+if (IsNativeFrame() )
nRole = accessibility::AccessibleRole::FRAME;
else if( IsScrollable() )
nRole = accessibility::AccessibleRole::SCROLL_PANE;
diff --git a/vcl/source/window/window.cxx b/vcl/source/window/window.cxx
index f7920f793f43..869516b45902 100644
--- a/vcl/source/window/window.cxx
+++ b/vcl/source/window/window.cxx
@@ -157,7 +157,7 @@ void Window::dispose()
CallEventListeners( VclEventId::ObjectDying );
// do not send child events for frames that were registered as native
frames
-if( !ImplIsAccessibleNativeFrame() && mpWindowImpl->mbReallyVisible )
+if( !IsNativeFrame() && mpWindowImpl->mbReallyVisible )
if ( ImplIsAccessibleCandidate() && GetAccessibleParentWindow() )
GetAccessibleParentWindow()->CallEventListeners(
VclEventId::WindowChildDestroyed, this );
diff --git a/vcl/source/window/window2.cxx b/vcl/source/window/window2.cxx
index 5e9ffd2ef529..c9720139585d 100644
--- a/vcl/source/window/window2.cxx
+++ b/vcl/source/window/window2.cxx
@@ -1040,6 +1040,18 @@ bool Window::IsToolbarFloatingWindow() const
return mpWindowImpl && mpWindowImpl->mbToolbarFloatingWindow;
}
+bool Window::IsNativeFrame() const
+{
+if( mpWindowImpl->mbFrame )
+// #101741 do not check for WB_CLOSEABLE because undecorated floaters
(like menus!) are closeable
+if( mpWindowImpl->mnStyle & (WB_MOVEABLE | WB_SIZEABLE) )
+return true;
+else
+return false;
+else
+return false;
+}
+
void Window::EnableAllResize()
{
mpWindowImpl->mbAllResize = true;
commit 756febf9a889cc969c3c7812806ef999d0befb95
Author: Michael Weghorn
AuthorDate: Wed Aug 16 18:02:27 2023 +0200
Commit: Michael Weghorn
[Libreoffice-bugs] [Bug 156787] docx format not entirely correct
https://bugs.documentfoundation.org/show_bug.cgi?id=156787 --- Comment #2 from hoang.hano...@gmail.com --- Your website address is actually https://www.ictergezocht.nl (you missed the last letter l so I have to guess that). I cannot register for a free account on that website for testing (even with proxy enabled, the website just pops up FALSE error). Could you register a test account on this website (and you could send that account information for me over this email address) so that I can test my hypothesis with the website by myself? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156586] Mailing Labels, navigation & inserting of columns
https://bugs.documentfoundation.org/show_bug.cgi?id=156586 Dieter changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156598] Custom list numbering from DOCX import is not available in UI
https://bugs.documentfoundation.org/show_bug.cgi?id=156598 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 156586] Mailing Labels, navigation & inserting of columns
https://bugs.documentfoundation.org/show_bug.cgi?id=156586 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 156599] Error message when load a form. System works correct after confirming the message
https://bugs.documentfoundation.org/show_bug.cgi?id=156599 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 156598] Custom list numbering from DOCX import is not available in UI
https://bugs.documentfoundation.org/show_bug.cgi?id=156598 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 148208] Can't insert image in LibreOffice Calc or not anchored correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=148208 --- Comment #5 from QA Administrators --- Dear scoccac, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107993] FORMATTING: Free space filling broken with thousands separator
https://bugs.documentfoundation.org/show_bug.cgi?id=107993 --- Comment #10 from QA Administrators --- Dear Benoît Thébaudeau, 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 156801] Inconsistent updating of selected character count
https://bugs.documentfoundation.org/show_bug.cgi?id=156801 hoang.hano...@gmail.com changed: What|Removed |Added Version|7.5.3.2 release |6.0.7.3 release Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from hoang.hano...@gmail.com --- It's interesting to track again old version in how differently they count these statistics (compared to your 14-step procedure with 4 incorrect counts): 1. Version 4.0.6.2 (Build ID: 2e2573268451a50806fcd60ae2d9fe01dd0ce24) (count words only, 14 steps, no incorrect): In this version, it counts only number of words, and does not count number of characters. Applying your procedure results in all correct counts for number of words. 2. Version 5.2.7.2 Build ID: 2b7f1e640c46ceb28adf43ee075a6e8b8439ed10 CPU Threads: 8; OS Version: Linux 6.1; UI Render: default; VCL: gtk2; Locale: en-US (en_US.UTF-8); Calc: group (count words and characters, 14 steps with 4 incorrect counts, for counting characters inside words) In this version, it does update the number of words when you getting first character after space. However, it does not update number of selected characters after you keep moving to the right in the same word. 3. Version: 6.0.7.3 Build ID: dc89aa7a9eabfd848af146d5086077aeed2ae4a5 CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: gtk2; Locale: en-US (en_US.UTF-8); Calc: group This is the first version I observed the same reproducible behaviors like your 7.5.3.2. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149336] Support aligning CJK texts with BASE table
https://bugs.documentfoundation.org/show_bug.cgi?id=149336 Volga changed: What|Removed |Added See Also||https://github.com/harfbuzz ||/harfbuzz/issues/4311 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 156789] CALC FORMATTING: Cell background color not rendered when OS high contrast display mode is on
https://bugs.documentfoundation.org/show_bug.cgi?id=156789
ady changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
--- Comment #15 from ady ---
(In reply to V Stuart Foote from comment #13)
> OK, now I see the perceived issue. Perceived in that LO is handling HC theme
> exactly as it should, with the UI rendered in a reduced color palette as
> passed in from the os/DE.
>
> User applied colors in the UI are ignored when os/DE signals HC in use and
> instead follows the HC theme provided.
>
> Believe this is by design HC theme handling.
>
> Not clear we need do more as it would need a whole new theming logic to
> selectively adjust UI elements to "complement" the HC theme in use--where
> now such elements are ignored.
How users are supposed to understand how to ("correctly") use the color palette
for the background color of a cell in Calc with this setting enabled?
If there is some limitation based on OS/DE, then:
* users have no way to know how to select the "compatible" colors in LO/Calc
(if there is really such a thing); and,
* users cannot share documents/spreadsheets, if the colors are not seen by some
other OS/DE (in the intended way, or at all); and,
* users have no idea whether some OS setting needs to be changed in order to be
able to use this feature in LO/Calc.
If the only standard colors that are clearly-usable are black and white, then I
don't understand the purpose of having a "High contrast" setting. I might be
misunderstanding this feature.
If this setting depends/needs/complements some OS setting, it is not clearly
understood from LO/Calc's (options) UI/UX.
FWIW, as mentioned in comment 0, this issue is not new, and it is also seen in
recent LO Dev 24.2 versions on MS Windows too.
Setting to NEW (again), so these points can be addressed. This might not be a
bug from the POV of how it was intended by developers, but at least a lot of
tool-tips, help content and/or wiki pages seem to be needed for users to be
able to "correctly" use this feature (or, even better, improve the feature
itself). For instance, maybe the "High contrast" label should mention something
about "OS-related" in some way; I'll leave the adequate term to UX team.
Quoting from Help content:
"
The cell background color is ignored then.
"
... which would mean _no_ color palette is supported, at all. What's the point
of "High Contrast" then? Perhaps it should be named Black/White (Contrast)
only? I'm at least confused.
IOW, the feature (and its UI text) is far from clear/intuitive/understandable
for users ATM.
--
You are receiving this mail because:
You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 156789] CALC FORMATTING: Cell background color not rendered when OS high contrast display mode is on
https://bugs.documentfoundation.org/show_bug.cgi?id=156789
ady changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
--- Comment #15 from ady ---
(In reply to V Stuart Foote from comment #13)
> OK, now I see the perceived issue. Perceived in that LO is handling HC theme
> exactly as it should, with the UI rendered in a reduced color palette as
> passed in from the os/DE.
>
> User applied colors in the UI are ignored when os/DE signals HC in use and
> instead follows the HC theme provided.
>
> Believe this is by design HC theme handling.
>
> Not clear we need do more as it would need a whole new theming logic to
> selectively adjust UI elements to "complement" the HC theme in use--where
> now such elements are ignored.
How users are supposed to understand how to ("correctly") use the color palette
for the background color of a cell in Calc with this setting enabled?
If there is some limitation based on OS/DE, then:
* users have no way to know how to select the "compatible" colors in LO/Calc
(if there is really such a thing); and,
* users cannot share documents/spreadsheets, if the colors are not seen by some
other OS/DE (in the intended way, or at all); and,
* users have no idea whether some OS setting needs to be changed in order to be
able to use this feature in LO/Calc.
If the only standard colors that are clearly-usable are black and white, then I
don't understand the purpose of having a "High contrast" setting. I might be
misunderstanding this feature.
If this setting depends/needs/complements some OS setting, it is not clearly
understood from LO/Calc's (options) UI/UX.
FWIW, as mentioned in comment 0, this issue is not new, and it is also seen in
recent LO Dev 24.2 versions on MS Windows too.
Setting to NEW (again), so these points can be addressed. This might not be a
bug from the POV of how it was intended by developers, but at least a lot of
tool-tips, help content and/or wiki pages seem to be needed for users to be
able to "correctly" use this feature (or, even better, improve the feature
itself). For instance, maybe the "High contrast" label should mention something
about "OS-related" in some way; I'll leave the adequate term to UX team.
Quoting from Help content:
"
The cell background color is ignored then.
"
... which would mean _no_ color palette is supported, at all. What's the point
of "High Contrast" then? Perhaps it should be named Black/White (Contrast)
only? I'm at least confused.
IOW, the feature (and its UI text) is far from clear/intuitive/understandable
for users ATM.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155757] Support Color Filter in "Standard Filter" dialog enhancement - missing background colors choice in filter field. UI not English
https://bugs.documentfoundation.org/show_bug.cgi?id=155757 Aron Budea changed: What|Removed |Added Keywords||haveBacktrace -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155757] Support Color Filter in "Standard Filter" dialog enhancement - missing background colors choice in filter field. UI not English
https://bugs.documentfoundation.org/show_bug.cgi?id=155757 Aron Budea changed: What|Removed |Added CC||aron.bu...@gmail.com --- Comment #17 from Aron Budea --- Created attachment 189017 --> https://bugs.documentfoundation.org/attachment.cgi?id=189017=edit Backtrace When opening Standard Filter in the autofilter in French language, I get the following assert in a debug build: sc/source/ui/dbgui/filtdlg.cxx :117 : ScFilterDlg::ScFilterDlg(SfxBindings*, SfxChildWindow*, weld::Window*, const SfxItemSet&): l'assertion « m_xLbCond1->find_text(aStrBackgroundColor) != -1 » a échoué. Since there is no assertion failure when using English language, it seems to be related to the reported problem. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156780] Libre Office crashes during Find and Replace
https://bugs.documentfoundation.org/show_bug.cgi?id=156780 twentyjazzfunkgre...@hotmail.com changed: What|Removed |Added Ever confirmed|1 |0 Assignee|libreoffice-b...@lists.free |twentyjazzfunkgreats@hotmai |desktop.org |l.com CC||twentyjazzfunkgreats@hotmai ||l.com Status|NEEDINFO|UNCONFIRMED --- Comment #2 from twentyjazzfunkgre...@hotmail.com --- Created attachment 189015 --> https://bugs.documentfoundation.org/attachment.cgi?id=189015=edit Libre writer file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137222] Wrong format of text in cell A81
https://bugs.documentfoundation.org/show_bug.cgi?id=137222 Aaron changed: What|Removed |Added CC||aaronth...@gmail.com --- Comment #7 from Aaron --- The bug is still present in Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-AU (fr_FR); UI: en-US Calc: threaded This is quite a strange bug. After a bit of testing I noticed that typing the word 'Novaservis' into A81 produces the bug. Also copying from certain cells do not produce the bug. For example, copying from A73 produces the bug but copying from A72 does not. The behaviour is very inconsistent. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106165] UI: Dismissed status bar re-appears while pasting unformatted text.
https://bugs.documentfoundation.org/show_bug.cgi?id=106165 --- Comment #9 from Zeytin Fidanı --- https://www.egezeytinyagi.net/;>Sızma zeytinyağı https://www.zeytinfidani.net/;>zeytin fidanı -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142424] Chart x-Axis Formatting dialog should show the time in addition to the date
https://bugs.documentfoundation.org/show_bug.cgi?id=142424 --- Comment #5 from Commit Notification --- Xisco Fauli committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/8b9643960117612b7e1cae1ed8325c2630232d0f tdf#142424: Revert "related tdf#156579: just break for switch element" 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-ux-advise] [Bug 142424] Chart x-Axis Formatting dialog should show the time in addition to the date
https://bugs.documentfoundation.org/show_bug.cgi?id=142424 --- Comment #5 from Commit Notification --- Xisco Fauli committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/8b9643960117612b7e1cae1ed8325c2630232d0f tdf#142424: Revert "related tdf#156579: just break for switch element" 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 on the CC list for the bug.
[Libreoffice-bugs] [Bug 142424] Chart x-Axis Formatting dialog should show the time in addition to the date
https://bugs.documentfoundation.org/show_bug.cgi?id=142424 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-ux-advise] [Bug 142424] Chart x-Axis Formatting dialog should show the time in addition to the date
https://bugs.documentfoundation.org/show_bug.cgi?id=142424 Commit Notification changed: What|Removed |Added Whiteboard||target:24.2.0 -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-commits] core.git: svgio/qa svgio/source
svgio/qa/cppunit/SvgImportTest.cxx| 21 +
svgio/qa/cppunit/data/tdf117920.svg |7 +++
svgio/source/svgreader/svgdocumenthandler.cxx |7 +--
3 files changed, 29 insertions(+), 6 deletions(-)
New commits:
commit 8b9643960117612b7e1cae1ed8325c2630232d0f
Author: Xisco Fauli
AuthorDate: Thu Aug 17 09:24:18 2023 +0200
Commit: Xisco Fauli
CommitDate: Fri Aug 18 01:09:04 2023 +0200
tdf#142424: Revert "related tdf#156579: just break for switch element"
This reverts commit e222f60ac2a71032dbdf62d7c7e28978b5a0b19c.
To make the switch element behave like a
group as least, so the transform attribute is parsed
Change-Id: Id8c21ac6da217d8f7bc350ff41022335bf1e0f1f
Change-Id: If1e53f9baad8995f26f9b885cfef6265040736bc
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155758
Tested-by: Jenkins
Reviewed-by: Xisco Fauli
diff --git a/svgio/qa/cppunit/SvgImportTest.cxx
b/svgio/qa/cppunit/SvgImportTest.cxx
index 31e5bdb3ef13..2297367ee778 100644
--- a/svgio/qa/cppunit/SvgImportTest.cxx
+++ b/svgio/qa/cppunit/SvgImportTest.cxx
@@ -991,6 +991,27 @@ CPPUNIT_TEST_FIXTURE(Test, testNoneColor)
assertXPath(pDocument,
"/primitive2D/transform/mask/polypolygonstroke/line", "width", "3");
}
+CPPUNIT_TEST_FIXTURE(Test, testTdf117920)
+{
+Primitive2DSequence aSequence =
parseSvg(u"/svgio/qa/cppunit/data/tdf117920.svg");
+CPPUNIT_ASSERT_EQUAL(1, static_cast(aSequence.getLength()));
+
+drawinglayer::Primitive2dXmlDump dumper;
+xmlDocUniquePtr pDocument =
dumper.dumpAndParse(Primitive2DContainer(aSequence));
+
+CPPUNIT_ASSERT (pDocument);
+
+assertXPath(pDocument, "/primitive2D/transform/transform", "xy11", "1");
+assertXPath(pDocument, "/primitive2D/transform/transform", "xy12", "0");
+assertXPath(pDocument, "/primitive2D/transform/transform", "xy13", "-18");
+assertXPath(pDocument, "/primitive2D/transform/transform", "xy21", "0");
+assertXPath(pDocument, "/primitive2D/transform/transform", "xy22", "1");
+assertXPath(pDocument, "/primitive2D/transform/transform", "xy23", "-6");
+assertXPath(pDocument, "/primitive2D/transform/transform", "xy31", "0");
+assertXPath(pDocument, "/primitive2D/transform/transform", "xy32", "0");
+assertXPath(pDocument, "/primitive2D/transform/transform", "xy33", "1");
+}
+
CPPUNIT_TEST_FIXTURE(Test, testTdf97936)
{
// check that both rectangles are rendered in the viewBox
diff --git a/svgio/qa/cppunit/data/tdf117920.svg
b/svgio/qa/cppunit/data/tdf117920.svg
new file mode 100644
index ..487e0f6cb925
--- /dev/null
+++ b/svgio/qa/cppunit/data/tdf117920.svg
@@ -0,0 +1,7 @@
+http://www.w3.org/2000/svg;
+ xmlns:xlink="http://www.w3.org/1999/xlink;>
+
+
+
+
diff --git a/svgio/source/svgreader/svgdocumenthandler.cxx
b/svgio/source/svgreader/svgdocumenthandler.cxx
index 0b66a4bb44da..9c8ab88f2f62 100644
--- a/svgio/source/svgreader/svgdocumenthandler.cxx
+++ b/svgio/source/svgreader/svgdocumenthandler.cxx
@@ -199,6 +199,7 @@ namespace
mpTarget->parseAttributes(xAttribs);
break;
}
+case SVGToken::Switch: //TODO: Support switch element
case SVGToken::Defs:
case SVGToken::G:
{
@@ -442,12 +443,6 @@ namespace
break;
}
-case SVGToken::Switch:
-{
-//TODO: Support switch element
-break;
-}
-
default:
{
mpTarget = new SvgNode(SVGToken::Unknown, maDocument,
mpTarget);
[Libreoffice-bugs] [Bug 137753] [META] Regressions from "ooxml import: supprt cropping to shape"
https://bugs.documentfoundation.org/show_bug.cgi?id=137753 Bug 137753 depends on bug 156663, which changed state. Bug 156663 Summary: FILEOPEN PPTX: Skewed images shown with different aspect ratio and different clipping https://bugs.documentfoundation.org/show_bug.cgi?id=156663 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139902] [META] PPTX Image issues
https://bugs.documentfoundation.org/show_bug.cgi?id=139902 Bug 139902 depends on bug 156663, which changed state. Bug 156663 Summary: FILEOPEN PPTX: Skewed images shown with different aspect ratio and different clipping https://bugs.documentfoundation.org/show_bug.cgi?id=156663 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156663] FILEOPEN PPTX: Skewed images shown with different aspect ratio and different clipping
https://bugs.documentfoundation.org/show_bug.cgi?id=156663 Gerald Pfeifer changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3008 --- Comment #3 from Gerald Pfeifer --- This has been fixed by https://git.libreoffice.org/core/+/6c06c8a2be3d8cbbcb8ab1aaaeb04db95114dfcb%5E%21 Verified with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 5fecd865303b3f0a2eeb0b9466d2bcf23cfce068 CPU threads: 8; OS: Linux 6.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156793] Protect sheet and cell protection cannot be undone
https://bugs.documentfoundation.org/show_bug.cgi?id=156793 --- Comment #3 from software.v9...@slmail.me --- There is a cell protection. If you highlight all cells and try to remove the cell protection, it doesn't work. I guess this is because there is a matrix formula in it and it may be automatically protected? The sheet protection was my misunderstanding: if the check box "protect this sheet and the contents of the protected cells" is checked, then I thought it is already protected. So I tried to uncheck it to unprotect. Wrong logic. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156783] LO crash selecting table with the whole document and changing table border
https://bugs.documentfoundation.org/show_bug.cgi?id=156783 László Németh changed: What|Removed |Added Summary|LO crash if In Hide Changes |LO crash selecting table |mode, select a table by |with the whole document and |pressing Ctrl-A and then|changing table border |select the border around| |the table in the local m| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156783] LO crash if In Hide Changes mode, select a table by pressing Ctrl-A and then select the border around the table in the local m
https://bugs.documentfoundation.org/show_bug.cgi?id=156783 --- Comment #3 from László Németh --- Commit description: tdf#156783 sw tracked table column: fix crash setting border or border padding without correct table cursor. Table formatting is allowed on text selections starting with tables, but adding border or border padding resulted crashing. This regression became more visible with hidden deleted table columns, where SelectTable (e.g. Ctrl-A) doesn't select the whole table, but only the text content of the visible cells, and in the case of hidden right table columns, without table cursor. Manual test: insert two tables in the document, and in the first cell of the first table, select the whole document by pressing Ctrl-A 2 times or more. In table settings, enable table border or modify padding to crash LibreOffice. Regression since version 7.5. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156783] LO crash if In Hide Changes mode, select a table by pressing Ctrl-A and then select the border around the table in the local m
https://bugs.documentfoundation.org/show_bug.cgi?id=156783 László Németh changed: What|Removed |Added Status|ASSIGNED|RESOLVED Keywords||bibisectRequest Assignee|nem...@numbertext.org |libreoffice-b...@lists.free ||desktop.org Resolution|--- |FIXED Version|24.2.0.0 alpha0+ Master |7.5.5.2 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143002] [META] Tracked Changes of tables
https://bugs.documentfoundation.org/show_bug.cgi?id=143002 Bug 143002 depends on bug 156783, which changed state. Bug 156783 Summary: LO crash if In Hide Changes mode, select a table by pressing Ctrl-A and then select the border around the table in the local m https://bugs.documentfoundation.org/show_bug.cgi?id=156783 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/qa sw/source
sw/qa/uitest/writer_tests7/tdf156783.py | 63
sw/source/core/crsr/crsrsh.cxx |2 -
2 files changed, 64 insertions(+), 1 deletion(-)
New commits:
commit e79f0f65ab06baafc7e8a6aeb1d89ca748087b24
Author: László Németh
AuthorDate: Wed Aug 16 21:41:26 2023 +0200
Commit: László Németh
CommitDate: Fri Aug 18 00:06:43 2023 +0200
tdf#156783 sw tracked table column: fix crash setting border
or border padding without correct table cursor.
Table formatting is allowed on text selections starting
with tables, but adding border or border padding
resulted crashing. This regression became more visible
with hidden deleted table columns, where SelectTable
(e.g. Ctrl-A) doesn't select the whole table, but only
the text content of the visible cells, and in the case
of hidden right table columns, without table cursor.
Manual test: insert two tables in the document, and in the
first cell of the first table, select the whole document
by pressing Ctrl-A 2 times or more. In table settings,
enable table border or modify padding to crash LibreOffice.
Regression since version 7.5.
Change-Id: If8ebb52c7662ff37ac42348c8f412549b793b6d9
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155749
Tested-by: Jenkins
Reviewed-by: László Németh
diff --git a/sw/qa/uitest/writer_tests7/tdf156783.py
b/sw/qa/uitest/writer_tests7/tdf156783.py
new file mode 100644
index ..2ccdb7dcf6e1
--- /dev/null
+++ b/sw/qa/uitest/writer_tests7/tdf156783.py
@@ -0,0 +1,63 @@
+# -*- tab-width: 4; indent-tabs-mode: nil; py-indent-offset: 4 -*-
+#
+# This file is part of the LibreOffice project.
+#
+# This Source Code Form is subject to the terms of the Mozilla Public
+# License, v. 2.0. If a copy of the MPL was not distributed with this
+# file, You can obtain one at http://mozilla.org/MPL/2.0/.
+#
+from uitest.framework import UITestCase
+from uitest.uihelper.common import get_state_as_dict
+from libreoffice.uno.propertyvalue import mkPropertyValues
+from uitest.uihelper.common import select_pos
+from uitest.uihelper.common import get_url_for_data_file
+
+# Bug 156783 - crash fix: setting table border on a table without correct
table cursor
+
+class tdf156783(UITestCase):
+def test_tdf156783(self):
+with
self.ui_test.load_file(get_url_for_data_file("TC-table-del-add.docx")) as
self.document:
+
+xToolkit =
self.xContext.ServiceManager.createInstance('com.sun.star.awt.Toolkit')
+
+# accept all tracked changes
+self.xUITest.executeCommand(".uno:AcceptAllTrackedChanges")
+
+# select all tables
+self.xUITest.executeCommand(".uno:SelectAll")
+self.xUITest.executeCommand(".uno:SelectAll")
+self.xUITest.executeCommand(".uno:SelectAll")
+
+# dialog Table Properties - Borders
+with
self.ui_test.execute_dialog_through_command(".uno:TableDialog",
close_button="ok") as xDialog:
+tabcontrol = xDialog.getChild("tabcontrol")
+select_pos(tabcontrol, "3")
+
+sync = xDialog.getChild("sync")
+rightmf = xDialog.getChild("rightmf")
+leftmf = xDialog.getChild("leftmf")
+topmf = xDialog.getChild("topmf")
+bottommf = xDialog.getChild("bottommf")
+sync.executeAction("CLICK", tuple())
+
+rightmf.executeAction("TYPE",
mkPropertyValues({"KEYCODE":"CTRL+A"}))
+rightmf.executeAction("TYPE",
mkPropertyValues({"KEYCODE":"BACKSPACE"}))
+rightmf.executeAction("TYPE",
mkPropertyValues({"TEXT":"72pt"}))
+leftmf.executeAction("TYPE",
mkPropertyValues({"KEYCODE":"CTRL+A"}))
+leftmf.executeAction("TYPE",
mkPropertyValues({"KEYCODE":"BACKSPACE"}))
+leftmf.executeAction("TYPE", mkPropertyValues({"TEXT":"72pt"}))
+topmf.executeAction("TYPE",
mkPropertyValues({"KEYCODE":"CTRL+A"}))
+topmf.executeAction("TYPE",
mkPropertyValues({"KEYCODE":"BACKSPACE"}))
+topmf.executeAction("TYPE", mkPropertyValues({"TEXT":"72pt"}))
+bottommf.executeAction("TYPE",
mkPropertyValues({"KEYCODE":"CTRL+A"}))
+bottommf.executeAction("TYPE",
mkPropertyValues({"KEYCODE":"BACKSPACE"}))
+bottommf.executeAction("TYPE",
mkPropertyValues({"TEXT":"72pt"}))
+
+self.assertEqual(get_state_as_dict(rightmf)["Text"], u"72pt")
+self.assertEqual(get_state_as_dict(leftmf)["Text"], u"72pt")
+self.assertEqual(get_state_as_dict(topmf)["Text"], u"72pt")
+self.assertEqual(get_state_as_dict(bottommf)["Text"], u"72pt")
+
+# Without the fix in place, this test would have crashed here
+
+# vim: set shiftwidth=4 softtabstop=4 expandtab:
diff --git
[Libreoffice-ux-advise] [Bug 156789] CALC FORMATTING: Cell background color not rendered when OS high contrast display mode is on
https://bugs.documentfoundation.org/show_bug.cgi?id=156789 --- Comment #14 from Balázs --- Created attachment 189014 --> https://bugs.documentfoundation.org/attachment.cgi?id=189014=edit Additional content examples (In reply to V Stuart Foote from comment #13) > Believe this is by design HC theme handling. > > Not clear we need do more as it would need a whole new theming logic to > selectively adjust UI elements to "complement" the HC theme in use--where > now such elements are ignored. If this is by design, it certainly is very confusing. I checked some more user content and HC display behavior is very inconsistent (colors not always ignored) - font colors are retained - background colors are ignored - conditional background colors, however are retained - border colors are replaced by gray - arrows lose arrowheads - bars in charts are invisible see new examples attached when viewed with HC. I am not sure it is a good idea to adjust anything on user objects. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 156789] CALC FORMATTING: Cell background color not rendered when OS high contrast display mode is on
https://bugs.documentfoundation.org/show_bug.cgi?id=156789 --- Comment #14 from Balázs --- Created attachment 189014 --> https://bugs.documentfoundation.org/attachment.cgi?id=189014=edit Additional content examples (In reply to V Stuart Foote from comment #13) > Believe this is by design HC theme handling. > > Not clear we need do more as it would need a whole new theming logic to > selectively adjust UI elements to "complement" the HC theme in use--where > now such elements are ignored. If this is by design, it certainly is very confusing. I checked some more user content and HC display behavior is very inconsistent (colors not always ignored) - font colors are retained - background colors are ignored - conditional background colors, however are retained - border colors are replaced by gray - arrows lose arrowheads - bars in charts are invisible see new examples attached when viewed with HC. I am not sure it is a good idea to adjust anything on user objects. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151059] Can't type "^" character with AltGr+3 using Slovenian keyboard, opening Gallery instead
https://bugs.documentfoundation.org/show_bug.cgi?id=151059 Caolán McNamara changed: What|Removed |Added CC||caolan.mcnamara@collabora.c ||om, kelem...@ubuntu.com --- Comment #4 from Caolán McNamara --- Ctrl+Alt+3 for "Open the Gallery Deck" is set in officecfg/registry/data/org/openoffice/Office/Accelerators.xcu in I10N SHORTCUTS - NO TRANSLATE .uno:SidebarDeck.GalleryDeck I think adding I think adding would at least not use this shortcut for those languages. No idea if there is anything available based on "3" like ctrl+shift+alt+3 which could be used as an alternative without causing a similar problem? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: vcl/skia
vcl/skia/salbmp.cxx |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
New commits:
commit 5ca28013a5ceb1b633fd4df8f9451778be5f1734
Author: Mike Kaganski
AuthorDate: Thu Aug 17 17:33:22 2023 +0300
Commit: Mike Kaganski
CommitDate: Thu Aug 17 22:27:44 2023 +0200
Skia: Avoid assertion failure inside ProcessAndBlurAlphaMask
As seen opening https://bugs.documentfoundation.org/attachment.cgi?id=182024
from tdf#150610.
The upscale is pending, and SkiaSalBitmap::mImage is empty here;
EnsureBitmapData call works correctly in this case.
Change-Id: I71575b09b3b4513b06b55271f6440688785cfb84
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155792
Tested-by: Mike Kaganski
Reviewed-by: Mike Kaganski
diff --git a/vcl/skia/salbmp.cxx b/vcl/skia/salbmp.cxx
index b5da2e4bd432..eac913671384 100644
--- a/vcl/skia/salbmp.cxx
+++ b/vcl/skia/salbmp.cxx
@@ -235,7 +235,8 @@ BitmapBuffer* SkiaSalBitmap::AcquireBuffer(BitmapAccessMode
nMode)
// set otherwise exporting the following animated .png image will
// fail:
// https://bugs.documentfoundation.org/attachment.cgi?id=188792
-if ((mPixelsSize != mSize || getenv("SAL_FORCE_HIDPI_SCALING")) &&
mImage)
+static const bool bForceHiDPIScaling =
getenv("SAL_FORCE_HIDPI_SCALING") != nullptr;
+if (mPixelsSize != mSize || (bForceHiDPIScaling && mImage))
EnsureBitmapData();
assert(mPixelsSize == mSize);
break;
[Libreoffice-bugs] [Bug 135303] Bitmap Export: Export color bitmap(.bmp) in spite of setting 4bit grayscale
https://bugs.documentfoundation.org/show_bug.cgi?id=135303 --- Comment #10 from LeroyG --- See: https://ask.libreoffice.org/t/libreoffice-draw-export-as-image-only-black-and-white/94714 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 156795] Avoid using typesetter language "widow" and "orphan"
https://bugs.documentfoundation.org/show_bug.cgi?id=156795 --- Comment #14 from Mike Kaganski --- (In reply to Kazinator from comment #13) > > Please! The OP in tdf#156109 had *never* asked for a rename. They may have > > absolutely no desire to rename these; you don't even know, maybe they would > > *oppose* this new idea. But you effectively destroy that request. It would > > be OK to close it WF if so decided - but this action masks, hides the > > request; in the end, it could pretend to *implement* that request... > > > > Please do not! > > I am that OP, and that is not true. I share the exact opinion of the OP of > this bug. Somewhere in #156109, I wrote these words, which are exactly the > topic of this item: > > Kazinator> Orphan and Widow are some kind of typesetting jargon whose > metaphor not > Kazinator> everyone might understand[.] The point was not that you will *definitely* oppose. The point was: that bug was about a *different* thing. We *should never* merge bugs like that: even now, when you wrote that you agree with this bug, your original one does not become a dupe of this one: they have different ideas. In other words: in a year, someone comes, who agrees with, say, tdf#156795, but disagrees with tdf#156109. As long as such a scenario is possible, these are *different* bugs; with a potential of *different* further destiny (e.g., one might get questioned, discussed, reverted at some point, while another could stay). So *they are NOT "the same topic"*. And merging them creates havoc, makes bugzilla unmanageable. Thinking that merging them keeps bugzilla "neat" destroys its value as a tool of tracking ideas, bugs, and so on. Please note, that at no point I disagree with either of the ideas myself - I'm actually neutral. I only post data points that I know, like the Word screemshot, or the (false) memory of a setting needed for the dialog tooltip ;) -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 35538] Handling of fonts with more than 4 styles (R/B/I/BI) is suboptimal
https://bugs.documentfoundation.org/show_bug.cgi?id=35538 --- Comment #81 from João Paulo --- Created attachment 189013 --> https://bugs.documentfoundation.org/attachment.cgi?id=189013=edit Screenshot showing all variants in Merriweather Sans typeface family (in PT-BR locale with mixed EN-US names) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 35538] Handling of fonts with more than 4 styles (R/B/I/BI) is suboptimal
https://bugs.documentfoundation.org/show_bug.cgi?id=35538 --- Comment #80 from João Paulo --- (In reply to Eyal Rozenberg from comment #78) > (In reply to João Paulo from comment #77) > Not quite following you... There is no "Book" variant at the link you gave. > LO splits Merriweather Sans into 3 families: the original name, "ExtraBold" > and "Light", with the ExtraBold having two styles (ExtraBold and ExtraBold > Italic) with the others having 4 styles (R/B/I/BI). > > (PS - At the link, it tells you to follow a link to a newer and up-to-date > version of the fonts: https://github.com/SorkinType/Merriweather-Sans ) Maybe it's because I'm on PT-BR locale, but to me it shows Regular / Livro (Book) / Negrito (Bold) / ExtraBold / Itálico (Italic) / BookItalic / Itálico Negrito (Bold Italic) / ExtraBold Italic, as in the screenshot I'll send now. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 35538] Handling of fonts with more than 4 styles (R/B/I/BI) is suboptimal
https://bugs.documentfoundation.org/show_bug.cgi?id=35538 --- Comment #79 from Volga --- So LibreOffice have to jump out of GDI and CoreText for fix, and probably need to implement additional interface to let user choose font weight. https://www.digitaling.com/articles/956220.html https://zhuanlan.zhihu.com/p/647925453 https://mattesontypographics.com/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156789] CALC FORMATTING: Cell background color not rendered when OS high contrast display mode is on
https://bugs.documentfoundation.org/show_bug.cgi?id=156789 V Stuart Foote changed: What|Removed |Added Version|7.5.5.2 release |Inherited From OOo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 156789] CALC FORMATTING: Cell background color not rendered when OS high contrast display mode is on
https://bugs.documentfoundation.org/show_bug.cgi?id=156789 V Stuart Foote changed: What|Removed |Added Version|7.5.5.2 release |Inherited From OOo -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 156789] CALC FORMATTING: Cell background color not rendered when OS high contrast display mode is on
https://bugs.documentfoundation.org/show_bug.cgi?id=156789 V Stuart Foote changed: What|Removed |Added Severity|normal |enhancement CC||caolan.mcnamara@collabora.c ||om, ||libreoffice-ux-advise@lists ||.freedesktop.org Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #13 from V Stuart Foote --- OK, now I see the perceived issue. Perceived in that LO is handling HC theme exactly as it should, with the UI rendered in a reduced color palette as passed in from the os/DE. User applied colors in the UI are ignored when os/DE signals HC in use and instead follows the HC theme provided. Believe this is by design HC theme handling. Not clear we need do more as it would need a whole new theming logic to selectively adjust UI elements to "complement" the HC theme in use--where now such elements are ignored. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 156789] CALC FORMATTING: Cell background color not rendered when OS high contrast display mode is on
https://bugs.documentfoundation.org/show_bug.cgi?id=156789 V Stuart Foote changed: What|Removed |Added Severity|normal |enhancement CC||caolan.mcnamara@collabora.c ||om, ||libreoffice-ux-advise@lists ||.freedesktop.org Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #13 from V Stuart Foote --- OK, now I see the perceived issue. Perceived in that LO is handling HC theme exactly as it should, with the UI rendered in a reduced color palette as passed in from the os/DE. User applied colors in the UI are ignored when os/DE signals HC in use and instead follows the HC theme provided. Believe this is by design HC theme handling. Not clear we need do more as it would need a whole new theming logic to selectively adjust UI elements to "complement" the HC theme in use--where now such elements are ignored. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156801] New: Inconsistent updating of selected character count
https://bugs.documentfoundation.org/show_bug.cgi?id=156801 Bug ID: 156801 Summary: Inconsistent updating of selected character count Product: LibreOffice Version: 7.5.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: will.fried...@gmail.com Description: When selecting text, the number of selected characters should update as more characters are selected, no matter what the selected character is. This behavior is inconsistent, however, when word boundaries are crossed or non-letters are present. Below I give an example with punctuation, but equally-strange if not stranger behavior occurs if there are numbers in the words (e.g., try selecting character-by-character the string "Wo1 Wo2 Wo3"). This bug makes this feature useless for actually counting characters. Steps to Reproduce: 1. Open a new document. 2. Write "ab cd! ef" 3. Position the cursor at the beginning of the text. 4. Press shift-right to select the first character. Bottom bar reads correctly: "Selected: 1 word, 1 character." 5. Press shift-right again. The characters "ab" should be selected. Bottom bar reads correctly: "Selected: 1 word, 2 characters." 6. Press shift-right again. The characters "ab " should be selected. Bottom bar reads correctly: "Selected: 1 word, 3 characters." 7. Press shift-right again. The characters "ab c" should be selected. Bottom bar reads *incorrectly*: "Selected: 1 word, 3 characters." 8. Press shift-right again. The characters "ab cd" should be selected. Bottom bar reads *incorrectly*: "Selected: 1 word, 3 characters." 9. Press shift-right again. The characters "ab cd!" should be selected. Bottom bar reads correctly: "Selected: 2 words, 6 characters." 10. Press shift-right again. The characters "ab cd! " should be selected. Bottom bar reads correctly: "Selected: 2 words, 7 characters." 11. Press shift-right again. The characters "ab cd! e" should be selected. Bottom bar reads *incorrectly*: "Selected: 2 words, 7 characters." 12. Press shift-right again. The characters "ab cd! ef" should be selected. Bottom bar reads correctly: "Selected: 3 words, 9 characters." 13. Press shift-left. The characters: "ab cd! e" should be selected. Bottom bar reads correctly: "Selected 3 words, 8 characters." 14. Press shift-left. The characters: "ab cd! " should be selected. Bottom bar reads *incorrectly*: "Selected: 3 words, 8 characters." Actual Results: Bottom bar incorrectly reports the number of characters selected in certain circumstances. Expected Results: Bottom bar should correctly report the number of characters selected in all circumstances. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156800] No way to change selection colour in Libo on 7.6.0 release ?
https://bugs.documentfoundation.org/show_bug.cgi?id=156800 --- Comment #3 from nouvo09 --- Will do. I keep you posted. Btw I'm with Xfce. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 156795] Avoid using typesetter language "widow" and "orphan"
https://bugs.documentfoundation.org/show_bug.cgi?id=156795 --- Comment #13 from Kazinator --- > Please! The OP in tdf#156109 had *never* asked for a rename. They may have > absolutely no desire to rename these; you don't even know, maybe they would > *oppose* this new idea. But you effectively destroy that request. It would > be OK to close it WF if so decided - but this action masks, hides the > request; in the end, it could pretend to *implement* that request... > > Please do not! I am that OP, and that is not true. I share the exact opinion of the OP of this bug. Somewhere in #156109, I wrote these words, which are exactly the topic of this item: Kazinator> Orphan and Widow are some kind of typesetting jargon whose metaphor not Kazinator> everyone might understand[.] This like when the UI in Android phones warns the user that a SD card was not unmounted before being removed, expecting the population to be familiar with Unix jargon and commands. :) However, it is true that I did not make terminology the focus of #156109. The terminology, as such, is fine. Software can play a role in teaching users concepts and terminology. You can have "widow" and "orphan" if there is some tooltip, "learn more ..." link or whatever where they can get an explanation what that means. If you're a domain expert writing software, you can use its user interface and documentation to educate users in that domain (alongside having the software perform it "payload" tasks). You don't have to dumb down all the terminology so that other domain experts are confused or find it ridiculous, and you don't have to alienate users who don't understand the jargon. Where do you draw the line between typesetting jargon that is acceptable to Joe Sixpack and that is too advanced? How about "hanging indentation", "margin", "justification", "drop caps", "kerning" ... -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 156795] Avoid using typesetter language "widow" and "orphan"
https://bugs.documentfoundation.org/show_bug.cgi?id=156795 --- Comment #12 from Mike Kaganski --- Created attachment 189012 --> https://bugs.documentfoundation.org/attachment.cgi?id=189012=edit Widow/Orphan Control in Wird 2016 (In reply to jan d from comment #11) > > Note that Word, InDesign avoid using the terms "Orphan" and "Widow" too. > > What do they use instead? No idea about InDesign; and no idea about newer Word; but here is the Widow/Orphan Control checkbox in Word 2016. -- You are receiving this mail because: You are on the CC list for the bug.
