[Libreoffice-bugs] [Bug 154040] Not possible to insert interactive frame
https://bugs.documentfoundation.org/show_bug.cgi?id=154040 --- Comment #10 from Tomaz Vajngerl --- Yes, I can reproduce. Must be something dumb we do at inserting with the SdrObject, which is not valid anymore. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154154] LO can't install an extension for all users under macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=154154 QA Administrators changed: What|Removed |Added Keywords||notBibisectable -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151074] LibreOffice from macOS appstore - can not create connection to mysql database via database creation wizard
https://bugs.documentfoundation.org/show_bug.cgi?id=151074 QA Administrators changed: What|Removed |Added Keywords||notBibisectable -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153911] Warning when opening files with other files already open
https://bugs.documentfoundation.org/show_bug.cgi?id=153911 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 152250] Copying conditional formatting creates unmodifiable styles (save/load fixes it)
https://bugs.documentfoundation.org/show_bug.cgi?id=152250 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146764] LibreOffice Vanilla, TDF LibreOffice from macOS AppStore - form wizard fails to launch with embedded Firebird DB
https://bugs.documentfoundation.org/show_bug.cgi?id=146764 QA Administrators changed: What|Removed |Added Keywords||notBibisectable -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153910] textbox in Writer does not resolve style:writing-mode="page" to the writing mode of the page
https://bugs.documentfoundation.org/show_bug.cgi?id=153910 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 152250] Copying conditional formatting creates unmodifiable styles (save/load fixes it)
https://bugs.documentfoundation.org/show_bug.cgi?id=152250 --- Comment #4 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96651] Background Image Can be Arranged Forward
https://bugs.documentfoundation.org/show_bug.cgi?id=96651 --- Comment #9 from QA Administrators --- Dear Harald Koester, 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 55355] Writer PRINTING, PDF, FILEOPEN DOCX: Embedded image imported from docx file print at wrong size
https://bugs.documentfoundation.org/show_bug.cgi?id=55355 --- Comment #13 from QA Administrators --- Dear Ian Miller, 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 137510] Mail merge printer or single: fields remains without value at second header style
https://bugs.documentfoundation.org/show_bug.cgi?id=137510 --- Comment #11 from QA Administrators --- Dear pabordel, 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 140698] calc paste not working between sheets with Klipper history size set to 1 (steps in comment 12)
https://bugs.documentfoundation.org/show_bug.cgi?id=140698 --- Comment #13 from QA Administrators --- Dear Pascal, 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 136230] SPECIAL CHARACTER DIALOG: Results of search field are not displayed after font changing
https://bugs.documentfoundation.org/show_bug.cgi?id=136230 --- Comment #5 from QA Administrators --- Dear shariqkeen, 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 123527] Insert / special Character not correctly rebuilding font chart to match selected font and search string
https://bugs.documentfoundation.org/show_bug.cgi?id=123527 --- Comment #4 from QA Administrators --- Dear Luuk, 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 116372] VIEWING: Page jumps relative to ruler when switching to another window of the same document
https://bugs.documentfoundation.org/show_bug.cgi?id=116372 --- Comment #12 from QA Administrators --- Dear Harald Koester, 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 111850] UI breaks after scrolling somewhere while playing video
https://bugs.documentfoundation.org/show_bug.cgi?id=111850 --- Comment #8 from QA Administrators --- Dear Yan Pas, 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 154210] F1 (Help) for Navigator context menu for Headings not linked to relevant help pages
https://bugs.documentfoundation.org/show_bug.cgi?id=154210 Olivier Hallot changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154221] New: Insert image URL
https://bugs.documentfoundation.org/show_bug.cgi?id=154221 Bug ID: 154221 Summary: Insert image URL Product: LibreOffice Version: 7.5.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sme...@gmu.edu Provide a means to insert an image URL into a document and to use that URL rather than the actual image when exporting as HTML. Ideally this should include generating the URL from the browse (file selection) dialog. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154220] New: Case conversion
https://bugs.documentfoundation.org/show_bug.cgi?id=154220 Bug ID: 154220 Summary: Case conversion Product: LibreOffice Version: 7.5.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sme...@gmu.edu Provide keyboard and menu tool for case conversions: lower case, sentence case, title case, toggle case, upper case. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154219] New: Set format of image caption
https://bugs.documentfoundation.org/show_bug.cgi?id=154219 Bug ID: 154219 Summary: Set format of image caption Product: LibreOffice Version: 7.5.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sme...@gmu.edu Provide keyboard and menu tool to set the format of image captions to include centering and hyperlink. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127146] Footnotes "Before/After" text disappears while saving as DOC/X
https://bugs.documentfoundation.org/show_bug.cgi?id=127146 --- Comment #9 from Sulphur --- There isn't any workaround until this is fixed, is there? Maybe some way to add a space automatically to the beginning of the footnote text, as opposed to appending a non-clickable character to the footnote numeral? (That doesn't help with needing to add characters before the footnote numeral, of course.) Just tired of manually going to each footnote and hitting space when I need to send someone a decently-formatted docx. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154215] The WeekNum worksheet function is very slow
https://bugs.documentfoundation.org/show_bug.cgi?id=154215 --- Comment #2 from NOYB --- I realize VBA is a compatibility layer and do expect a performance hit. But a 1000 x performance hit? Seriously? Actually it even more the 1000 x because the system used for the Excel benchmark is 10 years old and much slower machine. 1.8GHz compared to 2.4GHz. The performance difference is probably near 2000 x. That doesn't seem reasonable even for compatibility. Even though it technically functions. With the much of a performance hit, it's essentially not compatible. Pretty sure there is plenty of room for improvement. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154215] The WeekNum worksheet function is very slow
https://bugs.documentfoundation.org/show_bug.cgi?id=154215 --- Comment #1 from Eike Rathke --- VBASupport is a compatibility layer, so don't expect speed. Any invocation of WorksheetFunction.something() requires overhead that can't be neglected. You'd probably save some time using the com.sun.star.sheet.FunctionAccess service directly from BASIC. See https://api.libreoffice.org/docs/idl/ref/servicecom_1_1sun_1_1star_1_1sheet_1_1FunctionAccess.html -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153908] Dragging scrollbars with mouse in relationships window causes content panel moves in oposite direction than expected
https://bugs.documentfoundation.org/show_bug.cgi?id=153908 Stéphane Guillou (stragu) changed: What|Removed |Added Regression By||Caolán McNamara Keywords|bibisectRequest |bibisected, bisected CC||caol...@redhat.com --- Comment #5 from Stéphane Guillou (stragu) --- bibisected with linux-64-7.5 repo to first bad commit 842a5e704af521cb282236a0fbd49a46e5fe615b which points to core commit: commit 59a2650101a0ce711151bfd39af1bbb69f71f318 author Caolán McNamara Fri Aug 05 15:51:46 2022 +0100 committer Caolán McNamara Sat Aug 06 13:07:49 2022 +0200 tdf#117388 use native scrollbar under gtk in database scrolled window Reviewed-on: https://gerrit.libreoffice.org/c/core/+/137879 Caolán, can you please have a look? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152250] Copying conditional formatting creates unmodifiable styles (save/load fixes it)
https://bugs.documentfoundation.org/show_bug.cgi?id=152250 --- Comment #3 from Peter Gervai --- Same happens in safe mode. Version: 7.4.5.1 / LibreOffice Community Build ID: 40(Build:1) CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: hu-HU (hu_HU.UTF8); UI: en-US Debian package version: 4:7.4.5-2 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152250] Copying conditional formatting creates unmodifiable styles (save/load fixes it)
https://bugs.documentfoundation.org/show_bug.cgi?id=152250 --- Comment #2 from Peter Gervai --- Reproduced in 7.4.5.1 as well. More detailed steps: 1. create a new sheet document 2. create new style "test1", set font color to octarine or whatever 3. create a column from 1..10 numbers 4. select column 5. Fromat >> Conditional >> Condition 6. Set "Cell Value // is less than // 5", Apply style "test1". Half of the cell colors shall change. 7. select cells with values; edit >> copy 8. create a new sheet document (where "test1" does not exist) 9. create a few numbers, select them 10. Edit >> Paste special >> Paste special >> Formats Only (button) This will color some cells and ALSO creates "test1" style. 11. open styles sidebar (F11), right click on "test1" 12. Modify is grayed out. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153908] Dragging scrollbars with mouse in relationships window causes content panel moves in oposite direction than expected
https://bugs.documentfoundation.org/show_bug.cgi?id=153908 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||105957, 108044 CC||stephane.guillou@libreoffic ||e.org OS|Windows (All) |All Status|UNCONFIRMED |NEW Keywords||bibisectRequest, regression Ever confirmed|0 |1 --- Comment #4 from Stéphane Guillou (stragu) --- Reproduced in: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 44837a12d12be3e525fa48b37c3dd2553cc97d94 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Confirmed that it's a regression, not reproduced in 7.4.6.2 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=105957 [Bug 105957] [META] Scrollbar-related bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=108044 [Bug 108044] [META] Base UX bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108044] [META] Base UX bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108044 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153908 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153908 [Bug 153908] Dragging scrollbars with mouse in relationships window causes content panel moves in oposite direction than expected -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105957] [META] Scrollbar-related bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=105957 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153908 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153908 [Bug 153908] Dragging scrollbars with mouse in relationships window causes content panel moves in oposite direction than expected -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151472] FORMATTING: Style change breaks direct formatting (bold, italic, underline)
https://bugs.documentfoundation.org/show_bug.cgi?id=151472 Peter Gervai changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEEDINFO|RESOLVED --- Comment #3 from Peter Gervai --- It is _not_ broken in 7.4.5.1. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104468] [META] DOCX (OOXML) image-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104468 Bug 104468 depends on bug 147318, which changed state. Bug 147318 Summary: FILEOPEN DOCX: Image position off https://bugs.documentfoundation.org/show_bug.cgi?id=147318 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96579] [WRITER] Figure caption badly converted in Word format because image anchoring and wrapping is changed to as-character/DML
https://bugs.documentfoundation.org/show_bug.cgi?id=96579 --- Comment #19 from Justin L --- *** Bug 147318 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147318] FILEOPEN DOCX: Image position off
https://bugs.documentfoundation.org/show_bug.cgi?id=147318 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Justin L --- *** This bug has been marked as a duplicate of bug 96579 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154218] New: variable and user field input field mishandles datetime when a locale is active
https://bugs.documentfoundation.org/show_bug.cgi?id=154218 Bug ID: 154218 Summary: variable and user field input field mishandles datetime when a locale is active Product: LibreOffice Version: 7.4.5.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: g...@grin.hu When using a full datetime format for a variable (fields>>variables>>user field or set variable) like "1999-01-01 11:22:33" it seems the dialog mishandles the decimal point. I had my test set to Hungarian, which uses comma (,) as a decimal separator, so the input field for "1999-01-01 12:00" generated a string like "43210,12345" which resulted "1899-12-31 12:00" since the dialog seem to expect english decimal point, as "43210.12345". Replacing the decimal manually fixed the datetime. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103378] [META] PDF export bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103378 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||154193 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154193 [Bug 154193] Inserted SVG is distorted after exporting to PDF -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154193] Inserted SVG is distorted after exporting to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=154193 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Version|7.5.0.3 release |5.4.0.3 release Ever confirmed|0 |1 Component|Writer |Printing and PDF export Status|UNCONFIRMED |NEW Blocks||103378 --- Comment #1 from Stéphane Guillou (stragu) --- Reproduced with: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 44837a12d12be3e525fa48b37c3dd2553cc97d94 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Artifacts were even worse back in 5.4.0.3 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103378 [Bug 103378] [META] PDF export bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154217] New: Fields variables (user field and variable) cannot format value for update as date (or similar)
https://bugs.documentfoundation.org/show_bug.cgi?id=154217 Bug ID: 154217 Summary: Fields variables (user field and variable) cannot format value for update as date (or similar) Product: LibreOffice Version: 7.4.5.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: g...@grin.hu Fields >> Variables >> User Field, Set variable, Show Variable, and editing a field or a variable by double click cannot handle formatting other than text or numerical, causing a very confusing experience, especially for dates and datetime. Reproduction: 1. create a new variable with "Set variable", and set format to a date format like "1999-01-01", and enter a date value, say, 2023-03-15. 2. Insert the variable, and close the dialog. 3. Double-click on the field: you will get value "42000" I see that it's "number of dates since 1899-12-30", but that probably won't help much in everyday use. It seems user fields and variables remember their formatting, but the input field ignores that when displaying. It is still possible to correctly update the field with "2022-11-22", but it's not possible to view the actual value. (As a sidenote: the manual about variables and user fields is pretty terse. It even neglects to tell the difference between variables and user fields. I see now but... possibly I shall create some diff there.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120163] Image partially hidden by white rectangle in header ( created with OnlyOffice)
https://bugs.documentfoundation.org/show_bug.cgi?id=120163 --- Comment #19 from Justin L --- "Compte Rendu" in the header requests a white background for the whole paragraph. Ceo-vision image requests to be in the background - behind the text. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140961] LO Writer: Frames are converted into text box when saving in .docx
https://bugs.documentfoundation.org/show_bug.cgi?id=140961 --- Comment #14 from Justin L --- I think this should be closed as INVALID. We have to do all kinds of emulation when saving from ODT to DOCX. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153758] LibreOffice Online Build is failing
https://bugs.documentfoundation.org/show_bug.cgi?id=153758 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org --- Comment #1 from Stéphane Guillou (stragu) --- Thank you for the report. Unfortunately, LibreOffice Online is currently frozen, so it is unlikely a fix will be available in the short term. I recommend looking into https://collaboraonline.github.io/ instead, which is built on top of LibreOffice. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154216] New: Scroll region window object; capture tools inhibited
https://bugs.documentfoundation.org/show_bug.cgi?id=154216 Bug ID: 154216 Summary: Scroll region window object; capture tools inhibited Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: junkyardma...@frontier.com Description: Scroll region is not a separate window object so cannot use scroll capture feature of tools such as Hypersnap. Please make the rows/columns scroll region a separate window object that can be utilized by the scroll capture feature of tools such as Hypersnap. Capture - Entire page with Scrolling; Ctrl + Shift + S Steps to Reproduce: 1. Create speaesheet with more rows than fit on screen. 2. Use a tool such as Hypersnap to do a scroll capture. 3. Actual Results: Capture entire visible window rather than the scrollable region. Expected Results: Scroll to capture the entire scrollable region. Even the portion that is off screen. Reproducible: Always User Profile Reset: No Additional Info: Perhaps other capture tools used with non windows OS are also inhibited. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113776] Hierarchical numerbing of objects (e.g. tables, figures) is not saved properly to DOC or DOCX format
https://bugs.documentfoundation.org/show_bug.cgi?id=113776 --- Comment #13 from Gabor Kelemen (allotropia) --- (In reply to space from comment #12) > Hi guy, > I used the latest released version of LO v7.5.1, this issue can be still > reproduced for .doc and .docx. so how is the progress and what is the plan ? > > Thanks > BR Hi If this bug is important for you (or any organization you work for/with) to be fixed, please consider getting professional help from certified developers: https://www.documentfoundation.org/certified-developers/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149570] Can't undo removing columns / rows until leaving the table or adding to history stack (steps in comment 4)
https://bugs.documentfoundation.org/show_bug.cgi?id=149570 Stéphane Guillou (stragu) changed: What|Removed |Added Version|7.4.0.0 alpha1+ |7.3.0.0.alpha1+ Regression By||Tomaž Vajngerl --- Comment #7 from Stéphane Guillou (stragu) --- Thanks, Caolán. I should have clarified the steps I used for my bisect: 1. Open Impress or Draw 2. Insert table 3. Add row: undo is possible 4. Remove row: undo is greyed out Before commit ae0e7e3918284c31a91acca0f733919926ae3a62, it was possible to undo the row removal without extra steps. But now I can see how your change in focus simply made a pre-existing issue pop-up when following my steps. Before that commit, one needs to then click inside the table as a step 5 to see that the undo was already unavailable. Quikee, any thoughts? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107830] [META] DOCX (OOXML) paragraph-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107830 Gabor Kelemen (allotropia) changed: What|Removed |Added Depends on|124059 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=124059 [Bug 124059] FILEOPEN DOCX: Position of text changes when exporting to DOCX and reopen in LO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120466] [META] DOCX (OOXML) anchor and text wrapping bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=120466 Gabor Kelemen (allotropia) changed: What|Removed |Added Depends on||124059 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=124059 [Bug 124059] FILEOPEN DOCX: Position of text changes when exporting to DOCX and reopen in LO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124059] FILEOPEN DOCX: Position of text changes when exporting to DOCX and reopen in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=124059 Gabor Kelemen (allotropia) changed: What|Removed |Added Blocks|107830 |120466 CC||kelem...@ubuntu.com Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107830 [Bug 107830] [META] DOCX (OOXML) paragraph-related issues https://bugs.documentfoundation.org/show_bug.cgi?id=120466 [Bug 120466] [META] DOCX (OOXML) anchor and text wrapping bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115625] FILEOPEN DOCX: Table placed on wrong position because of Frame Wrap
https://bugs.documentfoundation.org/show_bug.cgi?id=115625 --- Comment #9 from Justin L --- This kind of bug report is duplicated several times. Apparently LO doesn't really consider a table something that needs to be affected by wrapping. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 31914] FILEOPEN: incorrectly formatting 2007 DOCX; missing first page text shape content with Content Controls
https://bugs.documentfoundation.org/show_bug.cgi?id=31914 --- Comment #23 from Justin L --- Yeah - we can't put content controls into an editeng textbox. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154215] New: The WeekNum worksheet function is very slow
https://bugs.documentfoundation.org/show_bug.cgi?id=154215
Bug ID: 154215
Summary: The WeekNum worksheet function is very slow
Product: LibreOffice
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: BASIC
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: junkyardma...@frontier.com
Description:
More than 1000x > than Excel
Steps to Reproduce:
1. Run the code in the other information section.
2.
3.
Actual Results:
12 seconds for 10K WeekNum() calls (> 1ms per)
More than 1000x > than Excel
Expected Results:
Reasonably close to Excel performance (< 10x)
0.101 seconds for 10K WeekNum() calls
Reproducible: Always
User Profile Reset: No
Additional Info:
Option VBASupport 1
Sub WeekNum_Function_Performance()
Dim T1 As Single
Dim T2 As Single
With WorksheetFunction
T1 = Timer()
For i = 1 To 1
WkNum = .WeekNum("03/14/2023", 1)
Next i
T2 = Timer()
End With
MsgBox ("Iterations: " & i & ", Time: " & T2 - T1)
End Sub
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152943] GetErrCode() doesn't work as expected on RISC-V due to floating-point NaN payload not being propagated
https://bugs.documentfoundation.org/show_bug.cgi?id=152943 --- Comment #5 from Eike Rathke --- From https://groups.google.com/a/groups.riscv.org/g/isa-dev/c/g79dHlV4B_k/m/dtlPNaq8AwAJ "Implementors are free to provide a NaN payload propagation scheme as a nonstandard extension enabled by a nonstandard operating mode." I deduce that there may be RISC-V systems that support propagating NaN payloads. So with bad luck a build, even if it did make check on such system, would not run properly on systems that do not support the extension. We might have to have a runtime check in Calc as well and bail out if NaN payloads are not supported. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95228] FILEOPEN DOCX Textboxes overlap
https://bugs.documentfoundation.org/show_bug.cgi?id=95228 Justin L changed: What|Removed |Added Priority|medium |lowest Hardware|x86-64 (AMD64) |All OS|Windows (All) |All --- Comment #8 from Justin L --- Yeah, like comment 5 says, there is more than just textboxes here. It totally depends on a page-wide transparent image to contour-wrap paragraphs to the next page. The design of this document is atrocious. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135706] Text behind image frame after saving DOCX (as character frame)
https://bugs.documentfoundation.org/show_bug.cgi?id=135706 Telesto changed: What|Removed |Added Keywords|bibisectRequest | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154197] Pivot Table with column named "Data" does not show in Data Fields pane -EDITING
https://bugs.documentfoundation.org/show_bug.cgi?id=154197 --- Comment #2 from Alistair Saywell --- Original spreadsheet from Meta.xml was created in LibreOffice/7.0.4.2$Linux_ARM_EABI LibreOffice_project I modified it in 7.3.7.2 just to add image so neither is earlier version. It was created in German language version so the word displayed in Data fields was "Daten" not "Date". Apparently, it still displays "Daten" in German version, de.DE. Maybe better to have an error dialogue on creation of pivot table based on a range with a heading using reserved words so the issue could be corrected before the pivot table is created. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139666] Text hidden behind red arrow after DOCX export (but visible in ODT) (wrap issue)
https://bugs.documentfoundation.org/show_bug.cgi?id=139666 Telesto changed: What|Removed |Added Keywords|bibisectRequest, regression | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152943] GetErrCode() doesn't work as expected on RISC-V due to floating-point NaN payload not being propagated
https://bugs.documentfoundation.org/show_bug.cgi?id=152943 Eike Rathke changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Version|7.6.0.0 alpha0+ Master |Inherited From OOo OS|Linux (All) |All -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114426] [META] Caption bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=114426 sdc.bla...@youmail.dk changed: What|Removed |Added Depends on||154214 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154214 [Bug 154214] redesign proposal for Caption Options dialog -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154214] redesign proposal for Caption Options dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=154214 sdc.bla...@youmail.dk changed: What|Removed |Added Blocks||114426 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=114426 [Bug 114426] [META] Caption bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154214] New: redesign proposal for Caption Options dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=154214 Bug ID: 154214 Summary: redesign proposal for Caption Options dialog Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sdc.bla...@youmail.dk Created attachment 185992 --> https://bugs.documentfoundation.org/attachment.cgi?id=185992=edit glade preview of proposed redesign Attached is Glade preview screenshot for proposed redesign of Caption Options dialog. Main features: 1. groups options under meaningful section titles 2. organizes sections starting with the one that affects greater number of users, and then downward. 3. better labelling (i.e., more accurate presentation of the function of each option) Comparison with current dialog 1. (has poor section titles) 2. (no apparent logic to section ordering) 3. (labels are wrong, hard to understand in Category and Frame Format section) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104449] [META] DOCX (OOXML) textbox-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104449 Bug 104449 depends on bug 135706, which changed state. Bug 135706 Summary: Text behind image frame after saving DOCX (as character frame) https://bugs.documentfoundation.org/show_bug.cgi?id=135706 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104450] [META] DOCX (OOXML) file opening issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104450 Bug 104450 depends on bug 135706, which changed state. Bug 135706 Summary: Text behind image frame after saving DOCX (as character frame) https://bugs.documentfoundation.org/show_bug.cgi?id=135706 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135706] Text behind image frame after saving DOCX (as character frame)
https://bugs.documentfoundation.org/show_bug.cgi?id=135706 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #8 from Justin L --- *** This bug has been marked as a duplicate of bug 96579 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96579] [WRITER] Figure caption badly converted in Word format because image anchoring and wrapping is changed to as-character/DML
https://bugs.documentfoundation.org/show_bug.cgi?id=96579 --- Comment #18 from Justin L --- *** Bug 135706 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142855] Heading below image after DOCX export (anchored vertical-bottom-of-paragraph)
https://bugs.documentfoundation.org/show_bug.cgi?id=142855 Justin L changed: What|Removed |Added Summary|Heading below image after |Heading below image after |DOCX export |DOCX export (anchored ||vertical-bottom-of-paragrap ||h) --- Comment #7 from Justin L --- Lots of emulation happening here, since an ODT frame changes to a DOCX drawing something. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154205] Crash on reload of file (segfault in libswlo.so)
https://bugs.documentfoundation.org/show_bug.cgi?id=154205 --- Comment #2 from Caolán McNamara --- https://gerrit.libreoffice.org/c/core/+/148939 and https://gerrit.libreoffice.org/c/core/+/148940 might help -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152943] GetErrCode() doesn't work as expected on RISC-V due to floating-point NaN payload not being propagated
https://bugs.documentfoundation.org/show_bug.cgi?id=152943 --- Comment #4 from Commit Notification --- Eike Rathke committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/2fd915b7d2d2a9e25600a07587ab01d23bffbc58 Related: tdf#152943 Test that a quiet NaN payload is propagated It will be available in 7.6.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152943] GetErrCode() doesn't work as expected on RISC-V due to floating-point NaN payload not being propagated
https://bugs.documentfoundation.org/show_bug.cgi?id=152943 Commit Notification changed: What|Removed |Added Whiteboard||target:7.6.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118017] [META] macOS Dark Mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=118017 Bug 118017 depends on bug 154169, which changed state. Bug 154169 Summary: macOS Dark mode: black tree menu lines on dark background in LO preferences https://bugs.documentfoundation.org/show_bug.cgi?id=154169 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104461] [META] DOCX (OOXML) frame-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104461 Bug 104461 depends on bug 143292, which changed state. Bug 143292 Summary: Misaligned caption name in caption frame after DOCX/DOC export https://bugs.documentfoundation.org/show_bug.cgi?id=143292 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96579] [WRITER] Figure caption badly converted in Word format because image anchoring and wrapping is changed to as-character/DML
https://bugs.documentfoundation.org/show_bug.cgi?id=96579 --- Comment #17 from Justin L --- *** Bug 143292 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143292] Misaligned caption name in caption frame after DOCX/DOC export
https://bugs.documentfoundation.org/show_bug.cgi?id=143292 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #7 from Justin L --- *** This bug has been marked as a duplicate of bug 96579 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154140] Bring back the transparency option
https://bugs.documentfoundation.org/show_bug.cgi?id=154140 Cor Nouws changed: What|Removed |Added CC||c...@nouenoff.nl --- Comment #8 from Cor Nouws --- (In reply to Andreas Säger from comment #0) > Transparency option is now hidden in the "expert options". > > My most popular answer on ask.libreoffice.org is this: > https://ask.libreoffice.org/t/asked-before-calc-ver-7-3-1-3-highlighted-cell- > color/75738/4 Hi Andreas, It is happening so frequent and so complicated, that you think it is really worth bringing that option back from hidden to somewhere in the UI? thnx - Cor -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105035] FILEOPEN DOCX: Two frames, anchored to the same paragraph, imported as a single frame (comment 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=105035 Justin L changed: What|Removed |Added CC||jl...@mail.com --- Comment #11 from Justin L --- The two frames are different because style Cm has a
[Libreoffice-bugs] [Bug 104461] [META] DOCX (OOXML) frame-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104461 Bug 104461 depends on bug 127622, which changed state. Bug 127622 Summary: A text frame is imported from a specific DOCX as several separate frames which overlap https://bugs.documentfoundation.org/show_bug.cgi?id=127622 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105035] FILEOPEN DOCX: Two frames, anchored to the same paragraph, imported as a single frame (comment 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=105035 Justin L changed: What|Removed |Added CC||mikekagan...@hotmail.com --- Comment #10 from Justin L --- *** Bug 127622 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127622] A text frame is imported from a specific DOCX as several separate frames which overlap
https://bugs.documentfoundation.org/show_bug.cgi?id=127622 Justin L changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #7 from Justin L --- *** This bug has been marked as a duplicate of bug 105035 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127622] A text frame is imported from a specific DOCX as several separate frames which overlap
https://bugs.documentfoundation.org/show_bug.cgi?id=127622 Justin L changed: What|Removed |Added CC||jl...@mail.com --- Comment #6 from Justin L --- (In reply to NISZ LibreOffice Team from comment #3) > The text in the frame has several paragraphs and they have different > paragraph styles set. This seems to be the basis of breaking up the frame Yes, the documentation says that only "exactly identically defined framePr's are grouped together. So if there are any differences in x, y, etc, then they are separate frames. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104461] [META] DOCX (OOXML) frame-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104461 Bug 104461 depends on bug 149370, which changed state. Bug 149370 Summary: FILEOPEN DOCX Content imported without the frame https://bugs.documentfoundation.org/show_bug.cgi?id=149370 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137788] FILEOPEN DOCX: Table in frame positioned wrongly
https://bugs.documentfoundation.org/show_bug.cgi?id=137788 --- Comment #13 from Justin L --- *** Bug 149370 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149370] FILEOPEN DOCX Content imported without the frame
https://bugs.documentfoundation.org/show_bug.cgi?id=149370 Justin L changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #4 from Justin L --- *** This bug has been marked as a duplicate of bug 137788 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137788] FILEOPEN DOCX: Table in frame positioned wrongly
https://bugs.documentfoundation.org/show_bug.cgi?id=137788 --- Comment #12 from Justin L --- frame created by have the same across a regular paragraph and a blockTable (a table not inside ). Good luck. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154213] LibeOffice icons on the GNOME desktop are too big
https://bugs.documentfoundation.org/show_bug.cgi?id=154213 --- Comment #2 from Verhoeckx --- Created attachment 185991 --> https://bugs.documentfoundation.org/attachment.cgi?id=185991=edit GNOME icon template -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154213] LibeOffice icons on the GNOME desktop are too big
https://bugs.documentfoundation.org/show_bug.cgi?id=154213 --- Comment #1 from Verhoeckx --- Created attachment 185990 --> https://bugs.documentfoundation.org/attachment.cgi?id=185990=edit LibreOffice icon compared to a normal desktop icon This image was created by Tobias Bernard. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154213] New: LibeOffice icons on the GNOME desktop are too big
https://bugs.documentfoundation.org/show_bug.cgi?id=154213 Bug ID: 154213 Summary: LibeOffice icons on the GNOME desktop are too big Product: LibreOffice Version: 7.5.0.3 release Hardware: x86-64 (AMD64) OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: j.verhoe...@protonmail.com Description: Hello LibreOffice developers, The GNOME desktop has developed a standard how big the icons on their platform should be: https://developer.gnome.org/hig/guidelines/app-icons.html?highlight=icons#size-shape https://gitlab.gnome.org/Teams/Design/HIG-app-icons/blob/master/template.svg According to this standard the icons should adhere to the size of the base shape and shouldn't take the full height and width of the canvas. The problem with the icons of LibreOffice is that they take the full height of the canvas and don't follow the size of the base shape. The result is that the icons look too big on the GNOME desktop (in the Activities Overview and in the Dash). The solution is quiet simple: shrink the icons until they adhere to the base shape. This will improve the look and feel (the aesthetics) of the icons on the GNOME desktop a lot. --- I was made aware of this issue by a comment of Tobias Bernard (one of the main UX designers of the GNOME desktop) on Mastodon. You can find his comment here: https://mastodon.social/@tbernard/109982952297798479 --- LibreOffice 7.5 GNOME 43 Steps to Reproduce: 1. Install LibreOffice on the GNOME desktop 2. Look at the icons ;-) Actual Results: The icons are too big compared to all the other icons on the GNOME desktop. Expected Results: The icons should have the same size as all the other icons on the GNOME desktop. Reproducible: Always User Profile Reset: No Additional Info: A new set if icons especially for the GNOME desktop should be created in which the icons adhere to the base shape of the icon canvas. I'm not sure if the same problem also happens on the KDE desktop (or any other desktop) so this should be checked. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153666] MASTER DOCUMENT: In navigator 'Insert -> File' should be 'Insert -> Text File' to be more precise
https://bugs.documentfoundation.org/show_bug.cgi?id=153666 Cor Nouws changed: What|Removed |Added Version|7.5.0.3 release |Inherited From OOo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153666] MASTER DOCUMENT: In navigator 'Insert -> File' should be 'Insert -> Text File' to be more precise
https://bugs.documentfoundation.org/show_bug.cgi?id=153666 Cor Nouws changed: What|Removed |Added CC||c...@nouenoff.nl --- Comment #6 from Cor Nouws --- (In reply to peter josvai from comment #1) > insert "text from document" as a section And that is the whole idea of master documents? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153903] "Category and Number" and "Caption Text" in Cross-reference variable dialog are limited to fixed structural relations
https://bugs.documentfoundation.org/show_bug.cgi?id=153903 --- Comment #5 from sdc.bla...@youmail.dk --- (In reply to Heiko Tietze from comment #4) > Until then I suggest to just treat everything which is not category > or number as text. iiuc, this is a proposal for changing the current implementation (until a better solution, e.g., a CT field) is developed? Perhaps an EasyHack? I am guessing the change would be needed around here: https://opengrok.libreoffice.org/xref/core/sw/source/core/fields/reffld.cxx?r=71337b43#558 Such a hack would also have to address the current behavior that any text between the category name and caption number is currently included when the "Category and Number" option is chosen. In relation to the proposal, perhaps that text should not be included as "Caption Text"? If not an EasyHack, then maybe better to wait for a CT field? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147219] Keyboard short cut to traverse over open modules
https://bugs.documentfoundation.org/show_bug.cgi?id=147219 --- Comment #4 from Cor Nouws --- On Gnome, Alt+` (key left of 1/!) does just that; switching between windows of the same application. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147219] Keyboard short cut to traverse over open modules
https://bugs.documentfoundation.org/show_bug.cgi?id=147219 Cor Nouws changed: What|Removed |Added Version|7.3.0.3 release |Inherited From OOo CC||c...@nouenoff.nl -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153860] FILEOPEN DOCX: Frame moves to the left (instead of spilling off the end of the page)
https://bugs.documentfoundation.org/show_bug.cgi?id=153860 Justin L changed: What|Removed |Added Summary|FILEOPEN DOCX: Frame moves |FILEOPEN DOCX: Frame moves |to the left |to the left (instead of ||spilling off the end of the ||page) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153860] FILEOPEN DOCX: Frame moves to the left
https://bugs.documentfoundation.org/show_bug.cgi?id=153860 Justin L changed: What|Removed |Added Version|7.5.1.2 release |unspecified Priority|medium |lowest Severity|normal |minor OS|Windows (All) |All --- Comment #3 from Justin L --- The problem is that the frame is set to be larger than the text area. It is size 27.58 cm and the paper is less than 28cm wide. In MS Word the frame spills off the end into invisibility, but in LO it squishes into the available paper size. That can readily be seen by adding borders for example. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154212] A Frame with a Heading disrupts the "Move Chapter Up/Down" in Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=154212 sdc.bla...@youmail.dk changed: What|Removed |Added Blocks||103030 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103030 [Bug 103030] [META] Navigator sidebar deck and floating window -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103030] [META] Navigator sidebar deck and floating window
https://bugs.documentfoundation.org/show_bug.cgi?id=103030 sdc.bla...@youmail.dk changed: What|Removed |Added Depends on||154212 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154212 [Bug 154212] A Frame with a Heading disrupts the "Move Chapter Up/Down" in Navigator -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154212] New: A Frame with a Heading disrupts the "Move Chapter Up/Down" in Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=154212 Bug ID: 154212 Summary: A Frame with a Heading disrupts the "Move Chapter Up/Down" in Navigator Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sdc.bla...@youmail.dk Created attachment 185989 --> https://bugs.documentfoundation.org/attachment.cgi?id=185989=edit Document for demonstrating the effect of a frame on moving a chapter up The issue is easier to explain by demonstration. 1. Open the attached document. 2. In Navigator notice "MOVE THIS Heading Level 2" 3. Use context menu or "Move Chapter Down" icon in Navigator Panel to move this heading down. 4. Then use "Move Chapter Up" (or icon in panel) Actual: Heading moved to top in Navigator (and document) (above Level 1 Heading) Expected: Moved back to its original place. Additional information: 1. Example is a simplified version of an actual document where some headings appear in frames. 2. Have also encountered cases where "Move Chapter Down" gives unexpected effects with frames. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ee5dbd193fa24b46fb980ddd8a6c39ca349d0d01 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: da-DK (da_DK); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112313] FILESAVE Text below image moves up next to it when file saved as DOCX (ODT 2cm wrap, DOCX ~1cm wrap; comment 14)
https://bugs.documentfoundation.org/show_bug.cgi?id=112313 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||1650 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101650] Different wrapping space allowance between LO and Word: now a character is placed beside the table, in stead if below it.
https://bugs.documentfoundation.org/show_bug.cgi?id=101650 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||2313 CC||jl...@mail.com --- Comment #19 from Justin L --- probably a duplicate of bug 112313 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117611] Images anchored 'To Paragraph' in ODT are misplaced after saving as DOCX and anchored 'To Character'
https://bugs.documentfoundation.org/show_bug.cgi?id=117611 Justin L changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=13 | |5581| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124059] FILEOPEN DOCX: Position of text changes when exporting to DOCX and reopen in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=124059 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||5581 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135581] Changing anchor from "to page" or "to paragraph' or 'to character' (with intent or in DOCX export) moves the image to a total different position
https://bugs.documentfoundation.org/show_bug.cgi?id=135581 Justin L changed: What|Removed |Added See Also|https://bugs.documentfounda |https://bugs.documentfounda |tion.org/show_bug.cgi?id=11 |tion.org/show_bug.cgi?id=12 |7611|4059 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135581] Changing anchor from "to page" or "to paragraph' or 'to character' (with intent or in DOCX export) moves the image to a total different position
https://bugs.documentfoundation.org/show_bug.cgi?id=135581 --- Comment #13 from Justin L --- *** Bug 135842 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 87740] [META] Anchor and text wrapping bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=87740 Bug 87740 depends on bug 135842, which changed state. Bug 135842 Summary: Anchoring changes image position depending on which anchor is chosen https://bugs.documentfoundation.org/show_bug.cgi?id=135842 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
