[Libreoffice-bugs] [Bug 151438] SIDEBAR: Cannot select a different style category by keyboard
https://bugs.documentfoundation.org/show_bug.cgi?id=151438 --- Comment #8 from Dieter --- Problem with my user profile. In SafeMode it works. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103427] [META] Styles and Formatting sidebar deck and floating window
https://bugs.documentfoundation.org/show_bug.cgi?id=103427 Bug 103427 depends on bug 151438, which changed state. Bug 151438 Summary: SIDEBAR: Cannot select a different style category by keyboard https://bugs.documentfoundation.org/show_bug.cgi?id=151438 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=98259 Bug 98259 depends on bug 151438, which changed state. Bug 151438 Summary: SIDEBAR: Cannot select a different style category by keyboard https://bugs.documentfoundation.org/show_bug.cgi?id=151438 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151438] SIDEBAR: Cannot select a different style category by keyboard
https://bugs.documentfoundation.org/show_bug.cgi?id=151438 V Stuart Foote changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151438] SIDEBAR: Cannot select a different style category by keyboard
https://bugs.documentfoundation.org/show_bug.cgi?id=151438 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org --- Comment #7 from V Stuart Foote --- Sequence as for *all* movements between elements is F10 -> F6 (and F6 cycle to Sidebar)--hardcoding the F10, F6 movement shortcuts is our primary Assistive Technology support. Alternative, the F11 shortcut will place UI Focus into the Styles deck of the Sidebar. Once on Sidebar it is and cursor There is "packing" within any elements on the Content panels. / will move between the element blocks. Cursor then advances for elements with listboxes. Version: 7.4.2.3 (x64) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151419] Crash in LO 7.4.1 MacOS aarch64 Writer when closing the formula editor
https://bugs.documentfoundation.org/show_bug.cgi?id=151419 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||6832 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146832] LO crashes on entering-leaving OLE-obj in MacOS on Apple Silicon
https://bugs.documentfoundation.org/show_bug.cgi?id=146832 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1419 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151419] Crash in LO 7.4.1 MacOS aarch64 Writer when closing the formula editor
https://bugs.documentfoundation.org/show_bug.cgi?id=151419 Dieter changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||dgp-m...@gmx.de Ever confirmed|0 |1 --- Comment #1 from Dieter --- Marcus, thank you for reporting the bug. To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile (https://wiki.documentfoundation.org/UserProfile) and re-test? Could you please also check, if it is a duplicate of bug 146832? => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103427] [META] Styles and Formatting sidebar deck and floating window
https://bugs.documentfoundation.org/show_bug.cgi?id=103427 Dieter changed: What|Removed |Added Depends on||151438 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151438 [Bug 151438] SIDEBAR: Cannot select a different style category by keyboard -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=98259 Dieter changed: What|Removed |Added Depends on||151438 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151438 [Bug 151438] SIDEBAR: Cannot select a different style category by keyboard -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151438] SIDEBAR: Cannot select a different style category by keyboard
https://bugs.documentfoundation.org/show_bug.cgi?id=151438 Dieter changed: What|Removed |Added Summary|Cannot change style by |SIDEBAR: Cannot select a |keyboard|different style category by ||keyboard CC||dgp-m...@gmx.de Blocks||98259, 103427 Severity|trivial |minor Priority|medium |low --- Comment #6 from Dieter --- Leroy, how do you switch to the other styles (character, frame, page, list, table). I've found no way to do so. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=98259 [Bug 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=103427 [Bug 103427] [META] Styles and Formatting sidebar deck and floating window -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115665] Format in the CTRL+H search affects the CTRL+F search
https://bugs.documentfoundation.org/show_bug.cgi?id=115665 --- Comment #11 from V Stuart Foote --- A bit off topic, but in context of doing something with Search support. It would be nice to have ICU lib RegEx available to use from Find Bar ( bug 119200 ) but the consistency of no bleed over from the F dialog is better--as stated elsewhere no configuration of the Find Bar search that doesn't include visible control in the UI for it. So, can make a case that establishing a consolidated search deck for the Sidebar ( bug 95405 ) would be a good way to move forward. To expose the UI controls of the F dialog as content panels to fully configure the search. With a content panel to input the search strings. And content panels to hold results and reposition the canvas to focus at the results. Reuse the good stuff that Jim R. has been adding to SB Navigator deck. Would add that for a SB based Search it would be better UX to have ability to detach the deck from the SB, like current secondary Navigator. Or possibly to finally implement the SB framework needed ( bug 85905 ) to support detachable "tear away" SB decks. And eliminate the need for the Navigator duplicate, or any need to duplicate a new "Search" deck as for here. Instead just one of each but they could be torn away to float or to dock as user prefered. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151708] Unsaved documents are no longer recovered
https://bugs.documentfoundation.org/show_bug.cgi?id=151708 --- Comment #9 from Matt --- Pic numbers in description no longer relate to attachments. There should be a way to edit the bug report, but I don't see one. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151708] Unsaved documents are no longer recovered
https://bugs.documentfoundation.org/show_bug.cgi?id=151708 --- Comment #8 from Matt --- Created attachment 183212 --> https://bugs.documentfoundation.org/attachment.cgi?id=183212=edit unsaved files are NOT recovered -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151708] Unsaved documents are no longer recovered
https://bugs.documentfoundation.org/show_bug.cgi?id=151708 --- Comment #7 from Matt --- Created attachment 183211 --> https://bugs.documentfoundation.org/attachment.cgi?id=183211=edit saved file is recovered -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151708] Unsaved documents are no longer recovered
https://bugs.documentfoundation.org/show_bug.cgi?id=151708 --- Comment #6 from Matt --- Created attachment 183210 --> https://bugs.documentfoundation.org/attachment.cgi?id=183210=edit recovery says that it's successful -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151708] Unsaved documents are no longer recovered
https://bugs.documentfoundation.org/show_bug.cgi?id=151708 --- Comment #5 from Matt --- Created attachment 183209 --> https://bugs.documentfoundation.org/attachment.cgi?id=183209=edit recovery begins -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151708] Unsaved documents are no longer recovered
https://bugs.documentfoundation.org/show_bug.cgi?id=151708 --- Comment #4 from Matt --- Created attachment 183208 --> https://bugs.documentfoundation.org/attachment.cgi?id=183208=edit End LibreOffice task using Task Manager -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151708] Unsaved documents are no longer recovered
https://bugs.documentfoundation.org/show_bug.cgi?id=151708 --- Comment #3 from Matt --- Created attachment 183207 --> https://bugs.documentfoundation.org/attachment.cgi?id=183207=edit unsaved file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151708] Unsaved documents are no longer recovered
https://bugs.documentfoundation.org/show_bug.cgi?id=151708 --- Comment #2 from Matt --- Created attachment 183206 --> https://bugs.documentfoundation.org/attachment.cgi?id=183206=edit saved file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151708] Unsaved documents are no longer recovered
https://bugs.documentfoundation.org/show_bug.cgi?id=151708 --- Comment #1 from Matt --- Created attachment 183205 --> https://bugs.documentfoundation.org/attachment.cgi?id=183205=edit setup to reproduce -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151708] New: Unsaved documents are no longer recovered
https://bugs.documentfoundation.org/show_bug.cgi?id=151708 Bug ID: 151708 Summary: Unsaved documents are no longer recovered Product: LibreOffice Version: unspecified Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: vr...@post.com Description: L/O Writer (vers 7.4.2.3) is no longer recovering unsaved files. I do not know when I first noticed that it does not, but it has been several months (several versions earlier). Finally, I uninstalled the current version, and installed two old versions (7.0.0.0 and 7.1.0.0) that I was reasonably sure did not have the problem because they were before I encountered the problem. However, upon installing the old versions, they had the same problem, so now I am baffled. After uninstalling them, and reinstalling 7.4.2.3, the problem still exists. Steps to Reproduce: Step 0 – Setup I have one saved document (in a folder on the Desktop), and 4 unsaved, open documents (pic 01). There is the saved document (named document 1.odt) (pic 02) I have pics of unsaved documents (pics 03-06) all filled with text. Step 1 – End task Then I kill LibreOffice using “End task” on Task Manager (pic 07). I have used this often, with unsaved documents always being recovered upon restarting LibreOffice. Step 2 – Restart LibreOffice Now, when I restart LibreOffice (pic 08), it looks like it is going to recover the documents. I click “Start” which brings up a screen that says that all documents were “Successfully recovered” (pic 09). Step 3 – View the results Actual Results: When you look at the "recovered" documents, the saved document looks good (pic 10), but all of the unsaved documents are empty with the text “(Remote)” added to the temporary, unsaved document name (pics 11-14). Expected Results: I would expect all recovered documents to be as they were before. Reproducible: Always User Profile Reset: No Additional Info: This is my first bug report to LibreOffice. Safe Mode did not resolve the problem. It didn't try to recover documents at all. So, as instructed, I did not try to "reset" UserProfile. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115665] Format in the CTRL+H search affects the CTRL+F search
https://bugs.documentfoundation.org/show_bug.cgi?id=115665 --- Comment #10 from V Stuart Foote --- UX gave direction in see also bug 72080 -- the Find Bar query should be as simple (basic) as possible with no bleed over from the Find & Replace dialog--the dialog being used for any more demanding searches across the modules. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115665] Format in the CTRL+H search affects the CTRL+F search
https://bugs.documentfoundation.org/show_bug.cgi?id=115665 V Stuart Foote changed: What|Removed |Added CC||rayk...@gmail.com --- Comment #9 from V Stuart Foote --- STR of comment 0 and result remain valid, settings made in the Find and Replace dialog are bleeding into the Find Bar search. Here it is a setting made to the Format -> Font Effects 'Case' values, when set they affect searches from the Find Bar. @Jim and thoughts on connectivity between the Find Bar and settings of the Find & Replace dialog? And which, if any, should affect the Find Bar & Sidebar Navigator 'Repeat search' actions... -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151694] Sifr: The Mime Types for MS Office Files Are Missing or Too Generic
https://bugs.documentfoundation.org/show_bug.cgi?id=151694 Adolfo Jayme Barrientos changed: What|Removed |Added Blocks||125965 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=125965 [Bug 125965] [META] Sifr icons -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125965] [META] Sifr icons
https://bugs.documentfoundation.org/show_bug.cgi?id=125965 Adolfo Jayme Barrientos changed: What|Removed |Added Depends on||151694 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151694 [Bug 151694] Sifr: The Mime Types for MS Office Files Are Missing or Too Generic -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144072] LibreofficeBase crashed when 2 fields selected in report builder from different sections and width is adjusted 2nd time
https://bugs.documentfoundation.org/show_bug.cgi?id=144072 --- Comment #19 from Aron Budea --- (In reply to raal from comment #18) > @Aron, can you bisect it? I did get the crash after some steps based on the report, plus undoing changes, but the steps were anything but consistent, thus I'd rather not go down that rabbit hole. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151427] Writer is not opening at last cursor position
https://bugs.documentfoundation.org/show_bug.cgi?id=151427 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 151680] very sluggish opening documents!
https://bugs.documentfoundation.org/show_bug.cgi?id=151680 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151423] Unintended zoom in or out on command key press if Calc is still scrolling.
https://bugs.documentfoundation.org/show_bug.cgi?id=151423 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 151419] Crash in LO 7.4.1 MacOS aarch64 Writer when closing the formula editor
https://bugs.documentfoundation.org/show_bug.cgi?id=151419 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 151680] very sluggish opening documents!
https://bugs.documentfoundation.org/show_bug.cgi?id=151680 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151438] Cannot change style by keyboard
https://bugs.documentfoundation.org/show_bug.cgi?id=151438 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151438] Cannot change style by keyboard
https://bugs.documentfoundation.org/show_bug.cgi?id=151438 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147885] Crash if properties resize bar is dragged vertically
https://bugs.documentfoundation.org/show_bug.cgi?id=147885 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147885] Crash if properties resize bar is dragged vertically
https://bugs.documentfoundation.org/show_bug.cgi?id=147885 --- Comment #3 from QA Administrators --- Dear jon0x0, 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 88073] FORMATTING: Drawing Object Styles lost after template update
https://bugs.documentfoundation.org/show_bug.cgi?id=88073 --- Comment #13 from QA Administrators --- Dear Sean Carlos, 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 77902] Device I/O error when appending to log file from Linux to Samba share
https://bugs.documentfoundation.org/show_bug.cgi?id=77902 --- Comment #14 from QA Administrators --- Dear Jeff H, 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 47415] vclcanvas does not show pure-text effects on X11
https://bugs.documentfoundation.org/show_bug.cgi?id=47415 --- Comment #8 from QA Administrators --- Dear Thorsten Behrens (CIB), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115665] Format in the CTRL+H search affects the CTRL+F search
https://bugs.documentfoundation.org/show_bug.cgi?id=115665 --- Comment #8 from QA Administrators --- Dear Eltomito, 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 113984] Content of a sub-table in another table is hidden by page footer when breaking across pages
https://bugs.documentfoundation.org/show_bug.cgi?id=113984 --- Comment #14 from QA Administrators --- Dear Kieran Grant, 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 141619] Undoing of Replace All operation leaves a "dirty" spreadsheet, force recalculation needed
https://bugs.documentfoundation.org/show_bug.cgi?id=141619 Aron Budea changed: What|Removed |Added CC||aron.bu...@gmail.com Keywords|bibisectRequest |bibisected --- Comment #4 from Aron Budea --- Bibisected to the following range, which is a single commit in repo bibisect-42max. https://cgit.freedesktop.org/libreoffice/core/log/?qt=range=ac84ffb3c90bb5788608eadf2177f587021daaad..4c99a427ee4adaeddb2682c192384bad21d9d09b -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108799] [META] HTML export bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108799 V Stuart Foote changed: What|Removed |Added Depends on||151698 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151698 [Bug 151698] SCORM Output -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117708] Expose exporting as SVG slideshow as a separate menu option (or similar)
https://bugs.documentfoundation.org/show_bug.cgi?id=117708 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1698 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151698] SCORM Output
https://bugs.documentfoundation.org/show_bug.cgi?id=151698 V Stuart Foote changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vsfo...@libreoffice.org Blocks||108799 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||7708 Keywords||needsUXEval --- Comment #2 from V Stuart Foote --- way out of project scope, LO works trades in ODF few of the functional elements needed to prepare SCORM materials are even implemented, bug 95861 or bug 135282 for example. We might get as far as completing presentation export to SVG based Synchronized Multimedia Integration Language (SMIL), [1] and see also bug 117708) but SMI is about as far as we should go. Not clear we should invest dev effort to support current W3C SMIL 3.0. IMHO regards SCORM just NO, => WF =-ref-= [1] https://en.wikipedia.org/wiki/Synchronized_Multimedia_Integration_Language Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108799 [Bug 108799] [META] HTML export bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 151698] SCORM Output
https://bugs.documentfoundation.org/show_bug.cgi?id=151698 V Stuart Foote changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vsfo...@libreoffice.org Blocks||108799 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||7708 Keywords||needsUXEval --- Comment #2 from V Stuart Foote --- way out of project scope, LO works trades in ODF few of the functional elements needed to prepare SCORM materials are even implemented, bug 95861 or bug 135282 for example. We might get as far as completing presentation export to SVG based Synchronized Multimedia Integration Language (SMIL), [1] and see also bug 117708) but SMI is about as far as we should go. Not clear we should invest dev effort to support current W3C SMIL 3.0. IMHO regards SCORM just NO, => WF =-ref-= [1] https://en.wikipedia.org/wiki/Synchronized_Multimedia_Integration_Language Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108799 [Bug 108799] [META] HTML export bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 151438] Cannot change style by keyboard
https://bugs.documentfoundation.org/show_bug.cgi?id=151438 --- Comment #4 from Cal --- I gave up on Libre Office completely, just to buggie. I'm sitting back with the impression that the amount of features have precedence over quality. To many features are buggie or not working at an acceptable level. You really need a "Linus Torvalds" alike person to be gate-keeper of new features/code and to be in charge of clean-up before it's getting out of hand (well, I guess you already passed that point). World really need an alternative. I've gladly pay for it too. But I didn't found one in Libra. But thanks for taking your time to looking into my bug report, but I've no longer have Libre installed so cannot give any feedback on the subject now. (Sorry for going off-topic.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151702] Down arrows in Calc AutoFilter are not very visible using dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=151702 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org --- Comment #1 from V Stuart Foote --- 1) Using the selected color scheme: then we could use the Text color for the button background and Application Color for the down-arrow +1, I think we build these selection arrows (i.e. not from an icon theme) so maybe? If possible the Text color/Application Color from theme would be functional. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129062] [META] Skia library bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=129062 V Stuart Foote changed: What|Removed |Added Depends on||151703 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151703 [Bug 151703] Impress slide show loses background gradients -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151703] Impress slide show loses background gradients
https://bugs.documentfoundation.org/show_bug.cgi?id=151703 V Stuart Foote changed: What|Removed |Added Ever confirmed|0 |1 CC||vsfo...@libreoffice.org Blocks||129062 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from V Stuart Foote --- Any improvement to the gradient for the background gradient in the slide show when you disable Skia rendering? Done from Tools -> Options -> View and clear both Skia checkboxes and restart. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=129062 [Bug 129062] [META] Skia library bugs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151671] Calc: Freeze Rows and Columns is freez the first rows or columns only
https://bugs.documentfoundation.org/show_bug.cgi?id=151671 --- Comment #4 from MARINA-SODA --- This behavior has continued since Version 4, and I was wondering why there are two of the same functions. Now I tested once more, I got indeterminate result. Freeze Rows and Columns,freezed at the top rows, freezed at the nth rows, etc and columns are not freezed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102283] [META] Slide/page pane bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102283 Aron Budea changed: What|Removed |Added Depends on||151383 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151383 [Bug 151383] UI: slide sorting position icon black box, previously grayish -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143108] PolyLine appearing/disappearing depending on zoom-level with Skia and anti-aliasing disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=143108 Aron Budea changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1383 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151383] UI: slide sorting position icon black box, previously grayish
https://bugs.documentfoundation.org/show_bug.cgi?id=151383 Aron Budea changed: What|Removed |Added Keywords|bibisectRequest |bibisected, bisected, ||regression See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||3108 CC||aron.bu...@gmail.com, ||l.lu...@collabora.com Blocks||102283 --- Comment #5 from Aron Budea --- This is a regression from the following commit, bibisected using repo bibisect-linux-64-7.1. Same commit as identified in bug 143108. Adding CC: to Luboš Luňák. https://cgit.freedesktop.org/libreoffice/core/commit/?id=4deadc3c78949c18bb886eb1f66caa8f3cd7a2df author Luboš Luňák 2020-09-25 13:30:11 +0200 committer Luboš Luňák 2020-09-29 09:54:42 +0200 disentangle AA and B2D use in VCL drawing Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102283 [Bug 102283] [META] Slide/page pane bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147235] Writer doesn't remember "view/resolved comments"
https://bugs.documentfoundation.org/show_bug.cgi?id=147235 Aron Budea changed: What|Removed |Added Version|unspecified |6.4.7.2 release CC||aron.bu...@gmail.com Keywords|bibisectRequest |implementationError --- Comment #4 from Aron Budea --- This is already in latest of 6.4, the feature got introduced in 6.4 as well in bug 119228. I think we can safely say this is an implementation error. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151705] FORMATTING italics
https://bugs.documentfoundation.org/show_bug.cgi?id=151705 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org --- Comment #1 from V Stuart Foote --- Shortcut works form me on Windows. Perhaps clear user profile, or check Tools -> Customization for shortcut assigned to .uno:Italic, and if the Toolbar DF button action applies. Version: 7.4.2.3 (x64) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: b887d67ff9914100df787bd2036b22bf32456fab CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103184] [META] UI theming bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103184 Bug 103184 depends on bug 46973, which changed state. Bug 46973 Summary: Libreoffice uses GtkMenu background as color of document frame shadow https://bugs.documentfoundation.org/show_bug.cgi?id=46973 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 46973] Libreoffice uses GtkMenu background as color of document frame shadow
https://bugs.documentfoundation.org/show_bug.cgi?id=46973 Adolfo Jayme Barrientos changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #11 from Adolfo Jayme Barrientos --- Andreas Kainz led an effort years ago to remove the fugly borders. We all forgot about this bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 32500] [META] GTK style doesn't draw some elements via GTK
https://bugs.documentfoundation.org/show_bug.cgi?id=32500 Bug 32500 depends on bug 46973, which changed state. Bug 46973 Summary: Libreoffice uses GtkMenu background as color of document frame shadow https://bugs.documentfoundation.org/show_bug.cgi?id=46973 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150966] FILESAVE Editing this MSO file in LO Writer causes the header and footer contents to be corrupted
https://bugs.documentfoundation.org/show_bug.cgi?id=150966 Aron Budea changed: What|Removed |Added Hardware|x86-64 (AMD64) |All CC||aron.bu...@gmail.com Regression By||Tomaž Vajngerl See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||8321 Keywords|bibisectRequest |bibisected, bisected --- Comment #8 from Aron Budea --- This regression started with the following commit, bibisected to the following commit using repo bibisect-win64-7.4 and steps from comment 3. Adding CC: to Tomaž Vajngerl. author Tomaž Vajngerl 2022-06-06 22:53:23 +0200 committer Tomaž Vajngerl2022-06-08 11:36:12 +0200 tdf148321: convert OOXML inset values to text distance values -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148321] FILEOPEN PPTX: text on top of circular object misplaced
https://bugs.documentfoundation.org/show_bug.cgi?id=148321 Aron Budea changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||0966 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147817] Calc (USA English) interprets Dollar amount "12.08" as the eighth of December if the user added a date acceptance pattern of M.D
https://bugs.documentfoundation.org/show_bug.cgi?id=147817 Eike Rathke changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #7 from Eike Rathke --- (In reply to Loren Amelang from comment #6) > The problem in this report turned out to be that it affects not only > currently typed dates in date columns, but the handling of any number in any > column that could possibly be an "M.D" date! It's treated like every other date input because it was specified as date acceptance pattern. This M.D pattern makes no sense in your locale but was forced when added. Hence I say it shouldn't be accepted in such constellation. > Like dollar values... In > columns that are not date formatted! Like any other date input. A display format is not an input mask. > If a column is explicitly set to dates A column is not set to dates. Cells of a column may have number formats applied, that display the underlying numeric value as date. Just enter 2022-10-22 in a cell, then remove all formatting with Ctrl+M and see the value 44856. > you should be able to enter more dates formatted like what you see above your > cell. You format values to not look like dates but numbers and at the same time want the input of a number be accepted as date.. again, number display formats are not input masks. > And even more importantly, in columns that are NOT formatted as dates, the > "Date acceptance patterns" should not affect the interpretation of numbers > at all! If the user told it to do so.. again, such M.D pattern simply should not be allowed in a locale that uses the . dot decimal separator, or if it was encountered in the configuration be ignored/discarded. > Is there some separate mechanism for choosing only how an entry you are > currently typing will be interpreted? No. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151664] Rendered text shifted with some Hebrew fonts - but not in PDF output
https://bugs.documentfoundation.org/show_bug.cgi?id=151664 --- Comment #15 from u...@net9.ga --- Replying to Eyal Rozenberg from comment 11: In my system, Insert → Special Character... also has separate entries for fonts of different languages. And the Noto Sans looks to me a short cut for Noto Sans English. It could be just of necessity. In order not to have one extremely long entry which will confuse, and discourage, many users. It could be just a sorting aid. Different countries seem to get their own page at fonts.google.com. But the fonts for each language remain the same. The Lebanon page, https://fonts.google.com/noto/fonts?noto.continent=Asia=LB, and the Palestinian Territories page, https://fonts.google.com/noto/fonts?noto.continent=Asia=PS, have the same Arabic fonts. And so does https://fonts.google.com/noto/fonts?noto.lang=en_Latn=Europe=GB=Latn and https://fonts.google.com/noto/fonts?noto.lang=en_Latn=Americas=US=Latn. I can not tell why google has so many duplicate pages. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151664] Rendered text shifted with some Hebrew fonts - but not in PDF output
https://bugs.documentfoundation.org/show_bug.cgi?id=151664 --- Comment #14 from u...@net9.ga --- Created attachment 183204 --> https://bugs.documentfoundation.org/attachment.cgi?id=183204=edit Lines mark approximate cursor positions for middle hebrew paragraph Replyig to Eyal Rozenberg from comment 13: The shifting does not affect the cursor position. Or it does so negligibly. What gets shifted is the glyph positions. Not the cursor positions. Consider the picture in the attachment. It has the 2nd Hebrew paragraph. And some thin blue lines added by me. Those lines were drawn by hand. Which is why they are only approximation. They should have been vertical. They are not. Only close to vertical. They should have been placed at the cursor positions. They are not. I positioned the cursor. Then, in order to draw the line, I had to open a menu. Which made me use the mouse. And that moved the cursor with the mouse, and changed it shape. Never the less, I hope these lines are good approximation for what follows. Let us mark the longest blue line as line #0. It marks the cursor position when the cursor is at the right edge of the paragraph. The next blue line, line #-1, is much shorter then line 0. It is positioned where the cursor gets to when I move it from position 0 one place to the left. Line -2 is where the cursor gets when it is moved another step to the left. And so on. As you see, I had no patient, and time, to mark lines all the way further. But I move the cursor one step to the left to see the if what follows does feet. What all this summaries to? If I could move the א in between line 0 and line -1, it looks as if its width will fill the distance between those two line. Between line -1 and line -2 I would put the space that is supposedly the shift at line 0. I will then move the ב in between line -2 and -3. It looks as if its width fills the gap between this 2 lines. Try that yourself. Move the cursor slowly one position to the left, and try to estimate if the gap between its current, and previous, position is suitable for the next glyph. The way I see it, the cursor position is correct. The glyph should follow it. And they are not. It is mainly the glyph positions that get shifted. Not the cursor position. As an aside, I tried to have the page use a built in grid. And failed. Is that a bug, or a wrong usage on my part? As a 2nd aside, perhaps the gutter that was added to version 7.4 is the source of our trouble? This is just a guess. Just trying to see what has changed from earlier versions, where there was no such problem. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sc/source
sc/source/ui/app/inputhdl.cxx |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
New commits:
commit 9d1d668a608cc5b406601c2f7f3d8581e8f47d1c
Author: Eike Rathke
AuthorDate: Sat Oct 22 23:22:15 2022 +0200
Commit: Eike Rathke
CommitDate: Sun Oct 23 00:23:48 2022 +0200
Resolves: tdf#150780 Overtyping is not editing
Change-Id: Ie83245479e4f356cf120dae1da39d35a9bb1a2e3
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/141676
Reviewed-by: Eike Rathke
Tested-by: Jenkins
diff --git a/sc/source/ui/app/inputhdl.cxx b/sc/source/ui/app/inputhdl.cxx
index 0d8274e3cc59..3ad56ba03cc7 100644
--- a/sc/source/ui/app/inputhdl.cxx
+++ b/sc/source/ui/app/inputhdl.cxx
@@ -2562,7 +2562,9 @@ bool ScInputHandler::StartTable( sal_Unicode cTyped, bool
bFromCommand, bool bIn
}
else
aStr = GetEditText(mpEditEngine.get());
-mbEditingExistingContent = !aStr.isEmpty();
+
+// cTyped!=0 is overtyping, not editing.
+mbEditingExistingContent = !cTyped && !aStr.isEmpty();
if (aStr.startsWith("{=") && aStr.endsWith("}") ) // Matrix
formula?
{
[Libreoffice-bugs] [Bug 145562] crash very short after program start or when selecting text
https://bugs.documentfoundation.org/show_bug.cgi?id=145562 stragu changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 Component|Writer |LibreOffice Hardware|x86 (IA32) |All CC||stephane.guil...@member.fsf ||.org --- Comment #7 from stragu --- Thomas : does this happen with Writer only or other components too? Mike : what suggests the crashes in Writer and Calc come from the same issue? Thomas and Mike : please both check if the latest 7.3 and 7.4 versions still crash on you, ideally also a recent master build from https://dev-builds.libreoffice.org/daily/master/current.html Setting the bug status to "need info" until we have more information. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151680] very sluggish opening documents!
https://bugs.documentfoundation.org/show_bug.cgi?id=151680 --- Comment #4 from Bee --- Hello! Some progress: I did downlaod and install 7.4.2 AND - lots of my documents open swiftly and perfectly but some still do not. Even some taken from two weeks ago - before I downlaoded a new version of Libre Office. (by the way, I had version 7.3 when I had the problem the first time... and since tried 7.3.6 as well. None worked) Once a sluggish document opens after waiting a long time - I cut and paste the contents inot a new document - and that opens swiftly, every time! I have just figured something out: Documents I have made past or present by PASTING TEXT FROM THE INTERNET ... are not all opening swiftly - but some are Documents I created and wrote ALL open swiftly, immediately! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103427] [META] Styles and Formatting sidebar deck and floating window
https://bugs.documentfoundation.org/show_bug.cgi?id=103427 Eyal Rozenberg changed: What|Removed |Added Depends on||151707 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151707 [Bug 151707] Add style filters: Applied on this page, applied in this viewport -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 151707] Add style filters: Applied on this page, applied in this viewport
https://bugs.documentfoundation.org/show_bug.cgi?id=151707 Eyal Rozenberg changed: What|Removed |Added Blocks||103427 Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103427 [Bug 103427] [META] Styles and Formatting sidebar deck and floating window -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 151707] Add style filters: Applied on this page, applied in this viewport
https://bugs.documentfoundation.org/show_bug.cgi?id=151707 Eyal Rozenberg changed: What|Removed |Added Blocks||103427 Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103427 [Bug 103427] [META] Styles and Formatting sidebar deck and floating window -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151707] New: Add style filters: Applied on this page, applied in this viewport
https://bugs.documentfoundation.org/show_bug.cgi?id=151707 Bug ID: 151707 Summary: Add style filters: Applied on this page, applied in this viewport Product: LibreOffice Version: 7.4.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com The bottom of the Styles sidebar has a drop-down list of applicable filters (or display modifiers) to the listbox of styles. Items currently include: * All Styles * Hierarchical * Hidden Styles * Applied Styles * Custom Styles I would like to be able to a refinement of "Applied Styles": 1. The styles applied anywhere on the current page 2. The styles applied anywhere visible in the viewport (typically a sub-area of a single page but sometimes parts of multiple pages) this would be in addition to "Applied styles", which are the styles applied anywhere in the document. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150780] Calc Failed to re-enter a formula starting with +
https://bugs.documentfoundation.org/show_bug.cgi?id=150780 Eike Rathke changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |er...@redhat.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150780] Calc Failed to re-enter a formula starting with +
https://bugs.documentfoundation.org/show_bug.cgi?id=150780 Eike Rathke changed: What|Removed |Added Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104278] UI: The text in the Type frame in the DocInformation tab in the Fields dialog isn't aligned to the left
https://bugs.documentfoundation.org/show_bug.cgi?id=104278 Caolán McNamara changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |caol...@redhat.com |desktop.org | Status|REOPENED|ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: vcl/headless
vcl/headless/CairoCommon.cxx |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit 96d7d4d16cfae09085d0baa41d5d70b5d33da726
Author: Caolán McNamara
AuthorDate: Sat Oct 22 20:36:04 2022 +0100
Commit: Caolán McNamara
CommitDate: Sat Oct 22 22:26:26 2022 +0200
ofz#52514 OOM
Change-Id: Id4f3b3cef27a299e5496276e274406d0720a27fe
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/141672
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/vcl/headless/CairoCommon.cxx b/vcl/headless/CairoCommon.cxx
index ec73955f1c0b..8f11fdbd9b6c 100644
--- a/vcl/headless/CairoCommon.cxx
+++ b/vcl/headless/CairoCommon.cxx
@@ -707,7 +707,7 @@ bool CairoCommon::drawPolyLine(cairo_t* cr,
basegfx::B2DRange* pExtents, const C
cairo_set_line_join(cr, eCairoLineJoin);
cairo_set_line_cap(cr, eCairoLineCap);
-constexpr int MaxNormalLineWidth = 128;
+constexpr int MaxNormalLineWidth = 96;
if (fLineWidth > MaxNormalLineWidth)
{
const double fLineWidthPixel
[Libreoffice-bugs] [Bug 151674] svg import of subscript distorted
https://bugs.documentfoundation.org/show_bug.cgi?id=151674 Caolán McNamara changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |caol...@redhat.com |desktop.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sc/source
sc/source/ui/unoobj/chart2uno.cxx |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit 9a2f193706278eef4c59df4b7028531a599dff8b
Author: Caolán McNamara
AuthorDate: Sat Oct 22 20:06:22 2022 +0100
Commit: Caolán McNamara
CommitDate: Sat Oct 22 21:53:36 2022 +0200
crashtesting: various ScChart2DataSequence::getTextualData crashes
since:
commit 03ef97c7605f4d3f537d5a1f31c2f131a439578d
Date: Tue Oct 18 14:16:08 2022 +0200
tdf#131910 speed up chart display
e.g.
bugtrackers/ods/ooo49870-1.ods
Change-Id: I14f8a03374d1c1d2b6e35b471c5d415b7590829e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/141671
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/sc/source/ui/unoobj/chart2uno.cxx
b/sc/source/ui/unoobj/chart2uno.cxx
index 58ca25ae854e..f92b1d4ec2ca 100644
--- a/sc/source/ui/unoobj/chart2uno.cxx
+++ b/sc/source/ui/unoobj/chart2uno.cxx
@@ -2460,7 +2460,7 @@ ScChart2DataSequence::ScChart2DataSequence(ScDocument*
pDoc, const ScChart2DataS
// Clone tokens.
m_aTokens.reserve(r.m_aTokens.size());
-for (const auto& rxToken : m_aTokens)
+for (const auto& rxToken : r.m_aTokens)
{
ScTokenRef p(rxToken->Clone());
m_aTokens.push_back(p);
[Libreoffice-bugs] [Bug 151706] New: Cannot recover file after removableMedium is restored
https://bugs.documentfoundation.org/show_bug.cgi?id=151706 Bug ID: 151706 Summary: Cannot recover file after removableMedium is restored Product: LibreOffice Version: 7.4.2.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tor...@yahoo.com Description: Open any file, edit it, stop Writer with ~^Del>TaskManager/LibreOffice>EndTask (under Windows). (In real life, this might be a computer or LibreOffice crash.) Restart LibreOffice; it recovers the file. OK. Do the same with a removable medium, but remove medium (USB key) before restarting LibreOffice (In real life, this might be a cloud drive which has not been restarted since the computer was.): it fails to recover the file, of course (*file* does not exist). Exit LibreOffice, re-insert the USB key (or restart the cloud drive), then restart LibreOffice; it fails again; it should not, since *file* now exists. Steps to Reproduce: 0: Open any file; 1: stop Writer with (under Windows) ~^Del>TaskManager/LibreOffice>EndTask. (In real life, this might be a computer or LibreOffice crash.) 2: Restart LibreOffice; it recovers the file. OK. 3: Open any file from a removable medium (USB key), stop Writer with (under Windows) ~^Del>TaskManager/LibreOffice>EndTask; 4: restart LibreOffice (In real life, this might be a cloud drive which has not been restarted since the computer was.): it fails to recover the file, of course (*file* does not exist). 5: Exit LibreOffice, re-insert the USB key (restore the removableMedium), then restart LibreOffice; it fails again; it should not, since *file* now exists. Actual Results: Recovery fails even though file is available. On top of it, Writer never forgets the failed recoveries and keeps presenting all of them at every restart. Expected Results: Recovery should succeed after file has been made available. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.4.2.3 (x64) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-CA (en_CA); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-22.05' - svx/source
svx/source/dialog/crashreportdlg.cxx |9 +
svx/source/dialog/crashreportdlg.hxx |2 ++
2 files changed, 11 insertions(+)
New commits:
commit 9d1c51265b419ea8e4084e2de30f740984380fa5
Author: Mike Kaganski
AuthorDate: Sat Oct 22 14:45:11 2022 +0200
Commit: Mike Kaganski
CommitDate: Sat Oct 22 21:21:00 2022 +0200
Set InstallLOKNotifier handler for CrashReportDialog
This prevents assertion failure in Window::SetLOKNotifier
called from Dialog::ImplStartExecute in gtktiledviewer.
Change-Id: I5c67d85728a34e47c36c73dafa616df45afa8092
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/141589
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
(cherry picked from commit 7b04e44d4e909e4a6e48a894ec5ad00cacbbcbf5)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/141592
Tested-by: Jenkins CollaboraOffice
diff --git a/svx/source/dialog/crashreportdlg.cxx
b/svx/source/dialog/crashreportdlg.cxx
index 8492ca3eccf3..4effe1dc636c 100644
--- a/svx/source/dialog/crashreportdlg.cxx
+++ b/svx/source/dialog/crashreportdlg.cxx
@@ -15,10 +15,17 @@
#include
#include
#include
+#include
#include
#include
+IMPL_STATIC_LINK_NOARG(CrashReportDialog, InstallLOKNotifierHdl, void*,
+ vcl::ILibreOfficeKitNotifier*)
+{
+return GetpApp();
+}
+
CrashReportDialog::CrashReportDialog(weld::Window* pParent)
: GenericDialogController(pParent, "svx/ui/crashreportdlg.ui",
"CrashReportDialog")
, mxBtnSend(m_xBuilder->weld_button("btn_send"))
@@ -46,6 +53,8 @@ CrashReportDialog::CrashReportDialog(weld::Window* pParent)
officecfg::Office::Common::Menus::PrivacyPolicyURL::get()
+ "?type=crashreport=" + utl::ConfigManager::getProductVersion()
+ "=" +
LanguageTag(utl::ConfigManager::getUILocale()).getBcp47());
+
+m_xDialog->SetInstallLOKNotifierHdl(LINK(this, CrashReportDialog,
InstallLOKNotifierHdl));
}
CrashReportDialog::~CrashReportDialog() {}
diff --git a/svx/source/dialog/crashreportdlg.hxx
b/svx/source/dialog/crashreportdlg.hxx
index 10bd77ef89c6..298d34cc8d87 100644
--- a/svx/source/dialog/crashreportdlg.hxx
+++ b/svx/source/dialog/crashreportdlg.hxx
@@ -32,6 +32,8 @@ private:
OUString maSuccessMsg;
DECL_LINK(BtnHdl, weld::Button&, void);
+DECL_STATIC_LINK(CrashReportDialog, InstallLOKNotifierHdl, void*,
+ vcl::ILibreOfficeKitNotifier*);
};
#endif
[Libreoffice-commits] core.git: vcl/source
vcl/source/filter/itiff/itiff.cxx |2 ++ 1 file changed, 2 insertions(+) New commits: commit c2f2317494adbf2055d43ad585c44eb8408f4ebd Author: Caolán McNamara AuthorDate: Sat Oct 22 16:37:24 2022 +0100 Commit: Caolán McNamara CommitDate: Sat Oct 22 20:31:30 2022 +0200 ofz#52600 stop after first failed image in a multi-image tiff Change-Id: Ibd0a8fd5720fef0801e00a6dd4d52c018471e24d Reviewed-on: https://gerrit.libreoffice.org/c/core/+/141667 Tested-by: Jenkins Reviewed-by: Caolán McNamara diff --git a/vcl/source/filter/itiff/itiff.cxx b/vcl/source/filter/itiff/itiff.cxx index 2dda51469ce7..510261e21b91 100644 --- a/vcl/source/filter/itiff/itiff.cxx +++ b/vcl/source/filter/itiff/itiff.cxx @@ -291,6 +291,8 @@ bool ImportTiffGraphicImport(SvStream& rTIFF, Graphic& rGraphic) ANIMATION_TIMEOUT_ON_CLICK, Disposal::Back); aAnimation.Insert(aAnimationFrame); } +else +break; } while (TIFFReadDirectory(tif)); TIFFClose(tif);
Re: Comparion of LogicalFontInstance::ImplGetGlyphBoundRect() between platforms
On Sat, 2022-10-22 at 01:42 +1100, Chris Sherlock wrote: > > Test name: VclLogicalFontInstanceTest::testglyphboundrect > > equality assertion failed > > - Expected: 51x82@(7,-80) > > - Actual : 51x83@(7,-80) > > I’ve had another look at the code, with some help from Khaled. The > issue is the way in which we do our final rounding. > > On Freetype, it uses 26.6 fixed point, and thus needs it’s own > special FreeType ceil and floor functions. CoreText appears to using > floating point, but the std::ceil and std::floor functions give > slight different results. I presume that for mac its CoreTextStyle::ImplGetGlyphoundRect and the CTFontGetBoundingRectsForGlyphs so could print the numbers we get there vs the ones we get in FreeTypeFont::GetGlyphBoundRect to verify that.
[Libreoffice-ux-advise] [Bug 151692] UI for controlling elements visible in animations list entry
https://bugs.documentfoundation.org/show_bug.cgi?id=151692 --- Comment #2 from Eyal Rozenberg --- I would also like to be able not to see: Shape "Foo" for a shape named "Foo", but rather just: Foo But I'm not sure whether I want this to be user-controlled, or just the second option always. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 151692] UI for controlling elements visible in animations list entry
https://bugs.documentfoundation.org/show_bug.cgi?id=151692 --- Comment #2 from Eyal Rozenberg --- I would also like to be able not to see: Shape "Foo" for a shape named "Foo", but rather just: Foo But I'm not sure whether I want this to be user-controlled, or just the second option always. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151691] Better distinguish shape text from shape name
https://bugs.documentfoundation.org/show_bug.cgi?id=151691 --- Comment #5 from Eyal Rozenberg --- (In reply to V Stuart Foote from comment #4) > If you want more differentiation just name the object, 1. But I don't want to have to name the object. Certainly not for this purpose. 2. Even if it's named, that's still no help: I will still only have a bunch of text. Colons, quotation marks, whatever - it's a single run of text. Not enough differentiation. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 151691] Better distinguish shape text from shape name
https://bugs.documentfoundation.org/show_bug.cgi?id=151691 --- Comment #5 from Eyal Rozenberg --- (In reply to V Stuart Foote from comment #4) > If you want more differentiation just name the object, 1. But I don't want to have to name the object. Certainly not for this purpose. 2. Even if it's named, that's still no help: I will still only have a bunch of text. Colons, quotation marks, whatever - it's a single run of text. Not enough differentiation. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 135462] LibreOffice 7.0.0.3 does not recognise JRE installation location at startup other than those in /Library/Java/JavaVirtualMachines/
https://bugs.documentfoundation.org/show_bug.cgi?id=135462 --- Comment #41 from Julien Nabet --- What processor do you have? I mean if it's Arm, JRE should be used again from 7.5.0 (see https://bugs.documentfoundation.org/show_bug.cgi?id=151545). Anyway don't hesitate to provide feedback with recent LO versions 7.3.6 or brand new 7.4.2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151692] UI for controlling elements visible in animations list entry
https://bugs.documentfoundation.org/show_bug.cgi?id=151692 Telesto changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||tele...@surfxs.nl -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 151692] UI for controlling elements visible in animations list entry
https://bugs.documentfoundation.org/show_bug.cgi?id=151692 Telesto changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||tele...@surfxs.nl -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 151692] UI for controlling elements visible in animations list entry
https://bugs.documentfoundation.org/show_bug.cgi?id=151692 --- Comment #1 from Telesto --- Same feeling here. I mentioned something similar at bug 151377 comment 9. However, I was looking at font spacing. This might be a better solution. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151705] New: FORMATTING italics
https://bugs.documentfoundation.org/show_bug.cgi?id=151705 Bug ID: 151705 Summary: FORMATTING italics Product: LibreOffice Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: da...@davidkachel.com CTRL+I simply doesn't work. LO Writer LibreOffice installation via Flatpack LibreOffice 7.4.0.3 Linux Mint 21 Cinammon 5.4.12 Linux Kernel 5.15.0-52-generic -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151700] "Print to file" doesn't work on OSX 12.6
https://bugs.documentfoundation.org/show_bug.cgi?id=151700 خالد حسني changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from خالد حسني --- Can you attach a screenshot of the print dialog? I get system print dialog and it does not have "Print to File", but I can select "Save as PDF" from a drop down menu and it saves a PDF file just fine. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 151691] Better distinguish shape text from shape name
https://bugs.documentfoundation.org/show_bug.cgi?id=151691 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org --- Comment #4 from V Stuart Foote --- What Regina didn't note is that when the object receiving the animation is named, its entry on the animation list will receive single quotation tics. So already provides more than the ":" separator. If you want more differentiation just name the object, as opposed to accepting the object type defaults. I imagine the name gets quoted to allow emended white space, but it works none the less. To name the sd objects, we can select from canvas or Navigator but we can't directly name an object from Navigator, open as bug 139633. But with object selection made the Format -> Name... dialog works fine. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 151691] Better distinguish shape text from shape name
https://bugs.documentfoundation.org/show_bug.cgi?id=151691 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org --- Comment #4 from V Stuart Foote --- What Regina didn't note is that when the object receiving the animation is named, its entry on the animation list will receive single quotation tics. So already provides more than the ":" separator. If you want more differentiation just name the object, as opposed to accepting the object type defaults. I imagine the name gets quoted to allow emended white space, but it works none the less. To name the sd objects, we can select from canvas or Navigator but we can't directly name an object from Navigator, open as bug 139633. But with object selection made the Format -> Name... dialog works fine. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145031] UI: Add shape name in the list, which list the animations
https://bugs.documentfoundation.org/show_bug.cgi?id=145031 --- Comment #6 from V Stuart Foote --- (In reply to V Stuart Foote from comment #5) > When needed, ability to Name... a selected object from the Navigator would > simplify things further. And that is open with proposed patch needing additional review as bug 139633 -- You are receiving this mail because: You are the assignee for the bug.
New Defects reported by Coverity Scan for LibreOffice
Hi,
Please find the latest report on new defect(s) introduced to LibreOffice found
with Coverity Scan.
1 new defect(s) introduced to LibreOffice found with Coverity Scan.
1 defect(s), reported by Coverity Scan earlier, were marked fixed in the recent
build analyzed by Coverity Scan.
New defect(s) Reported-by: Coverity Scan
Showing 1 of 1 defect(s)
** CID 1516141: Null pointer dereferences (FORWARD_NULL)
*** CID 1516141: Null pointer dereferences (FORWARD_NULL)
/sw/source/core/layout/paintfrm.cxx: 4293 in
SwFlyFrame::PaintSwFrame(OutputDevice &, const SwRect &, const SwPrintData *)
const()
4287
4288 SwLayoutFrame::PaintSwFrame( rRenderContext, aRect );
4289
4290 Validate();
4291
4292 {
>>> CID 1516141: Null pointer dereferences (FORWARD_NULL)
>>> Passing null pointer "pShell" to "GetOut", which dereferences it.
4293 SwTaggedPDFHelper tag(nullptr, nullptr, nullptr,
*pShell->GetOut());
4294 // first paint lines added by fly frame paint
4295 // and then unlock other lines.
4296 gProp.pSLines->PaintLines( , gProp );
4297 gProp.pSLines->LockLines( false );
4298 // have to paint frame borders added in heaven layer here...
To view the defects in Coverity Scan visit,
https://u15810271.ct.sendgrid.net/ls/click?upn=HRESupC-2F2Czv4BOaCWWCy7my0P0qcxCbhZ31OYv50ypSs1kiFPuCn2xFdlMIFBirii0zZ9j2-2F9F2XPBcBm2BNgi9duPy3v-2FzgFDd2LJ-2BDKI-3DrmUn_OTq2XUZbbipYjyLSo6GRo-2FpVxQ9OzkDINu9UTS-2FQhSdO0F0jQniitrGlNxDIzPJixVa1RlSFoO8Iq91OVlXhYkvpRjrn6ry8TbszrW82-2BGDTMcGDksUJyKOoLWZ2MtDvt3DfkuMjUotpT3Igngyt15Q-2BO45Z-2BS6jCx8FMTEbyiP2b3U9YhWDeenYzSo8YaQFgafrd0N62pwMJTNkYtcd3g3LUnwgcbUdFZtVTu9KqDE-3D
[Libreoffice-bugs] [Bug 145031] UI: Add shape name in the list, which list the animations
https://bugs.documentfoundation.org/show_bug.cgi?id=145031 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||9005 --- Comment #5 from V Stuart Foote --- So seems like WFM of bug 149005 makes this irrelevant and a => WF. You can now identify the object on canvas receiving the animation. Although the specific element of the object is not identified, the Sidebar Navigator/Animation deck are always in context of a view of the slide. A given that the work flow is much better if names are given to the objects on canvas receiving animations. So while we can select now from Navigator, we can't name directly and have to use the Format -> Name... dialog indirectly. When needed, ability to Name... a selected object from the Navigator would simplify things further. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149005] Navigator does not select/highlight names of images, objects, tables etc that get focus, also not with Content View activated
https://bugs.documentfoundation.org/show_bug.cgi?id=149005 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||5031 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151438] Cannot change style by keyboard
https://bugs.documentfoundation.org/show_bug.cgi?id=151438 Dieter changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #3 from Dieter --- (In reply to LeroyG from comment #2) > (In reply to LeroyG from comment #1) > > Press Tab twice, then Arrow Down/Arrow Up. > > Then Enter to apply. Cal, does this solve your problem? => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: svx/source
svx/source/dialog/crashreportdlg.cxx |9 +
svx/source/dialog/crashreportdlg.hxx |2 ++
2 files changed, 11 insertions(+)
New commits:
commit 7b04e44d4e909e4a6e48a894ec5ad00cacbbcbf5
Author: Mike Kaganski
AuthorDate: Sat Oct 22 14:45:11 2022 +0200
Commit: Mike Kaganski
CommitDate: Sat Oct 22 18:38:42 2022 +0200
Set InstallLOKNotifier handler for CrashReportDialog
This prevents assertion failure in Window::SetLOKNotifier
called from Dialog::ImplStartExecute in gtktiledviewer.
Change-Id: I5c67d85728a34e47c36c73dafa616df45afa8092
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/141589
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/svx/source/dialog/crashreportdlg.cxx
b/svx/source/dialog/crashreportdlg.cxx
index 33c879866cfd..d50f64131b11 100644
--- a/svx/source/dialog/crashreportdlg.cxx
+++ b/svx/source/dialog/crashreportdlg.cxx
@@ -15,10 +15,17 @@
#include
#include
#include
+#include
#include
#include
+IMPL_STATIC_LINK_NOARG(CrashReportDialog, InstallLOKNotifierHdl, void*,
+ vcl::ILibreOfficeKitNotifier*)
+{
+return GetpApp();
+}
+
CrashReportDialog::CrashReportDialog(weld::Window* pParent)
: GenericDialogController(pParent, "svx/ui/crashreportdlg.ui",
"CrashReportDialog")
, mxBtnSend(m_xBuilder->weld_button("btn_send"))
@@ -45,6 +52,8 @@ CrashReportDialog::CrashReportDialog(weld::Window* pParent)
officecfg::Office::Common::Menus::PrivacyPolicyURL::get()
+ "?type=crashreport=" + utl::ConfigManager::getProductVersion()
+ "=" +
LanguageTag(utl::ConfigManager::getUILocale()).getBcp47());
+
+m_xDialog->SetInstallLOKNotifierHdl(LINK(this, CrashReportDialog,
InstallLOKNotifierHdl));
}
CrashReportDialog::~CrashReportDialog() {}
diff --git a/svx/source/dialog/crashreportdlg.hxx
b/svx/source/dialog/crashreportdlg.hxx
index 868f86c58e68..f9d477f4d6f5 100644
--- a/svx/source/dialog/crashreportdlg.hxx
+++ b/svx/source/dialog/crashreportdlg.hxx
@@ -32,6 +32,8 @@ private:
OUString maSuccessMsg;
DECL_LINK(BtnHdl, weld::Button&, void);
+DECL_STATIC_LINK(CrashReportDialog, InstallLOKNotifierHdl, void*,
+ vcl::ILibreOfficeKitNotifier*);
};
#endif
Re: (was: ESC meeting minutes: 2022-10-20)
Am 22.10.22 um 15:58 schrieb Thorsten Behrens: Hi Andreas, all, Andreas Mantke wrote: I find it very shameful how much efford the board and it's members with a known and possible CoI on this topic invest to not enable further contributions and throw away a project which is evaluated important for the future of LibreOffice and TDF. While I understand your frustration - as Stephan points out up-thread, you did significant infrastructure work on the repo - I don't find it particularly nice, when you try (again) to politicize a technical evaluation. sorry but you try to refract. Please read my replies carefully. I'm not talking about numbers and this is not my matter here. And really I'm personally not frustrated. But as a member of TDF I'm frustrated about the actions of board members, not fostering opportunities for TDF/LibreOffice especially (online) collaborative versions of the softwre. And I hope I'm not the only TDF/community member who is concerned about this process. In this venue (with the dev list in Cc), it is not credible to claim someone would 'throw away' a project, or prevent further contributions, when you've just shown that there's no problem setting up shop on github easily. And here you try to refract again. The matter is not, if one could set up a project else where (like another LibreOffice Online fork), but if a collaborative work could be done on the resources and under the umbrella of TDF. There were times, when TDF was eager to broaden its OSS basis and try to convince further OSS projects / initiatives to join the foundation. Regards, Andreas -- ## Free Software Advocate ## Plone add-on developer ## My blog: http://www.amantke.de/blog
