[Libreoffice-bugs] [Bug 154071] Request: Rename "Square" gradient to "Rectangle" gradient in the UI
https://bugs.documentfoundation.org/show_bug.cgi?id=154071 Heiko Tietze changed: What|Removed |Added OS|Windows (All) |All CC|heiko.tietze@documentfounda |sdc.bla...@youmail.dk |tion.org| Hardware|x86-64 (AMD64) |All --- Comment #1 from Heiko Tietze --- I don't like the over-specification of a fairly fuzzy term. Most users (including me) don't understand the difference between Square and Quadratic (and the documentation keeps silent over the types) and rather play with the result than trying to understand the effect from the name. Switching from "Square" to "Rectangular" sounds good to me but I'd keep "Quadratic". Ultimately I don't see need to align the UI labels with internal variable names. So probably also NAB. Looking for gradient naming did not return bug insights: CSS: linear, radial, and conic [1] Adobe: Linear, Radial, Conic, Diamond, Reflected Photoshop: Linear, Radial, Angle, Reflected and Diamond MSO: DiagonalDown, DiagonalUp, FromCenter, FromCorner, FromTitle, Horizontal, Mixed, Vertical MSO: Linear, Radial, Rectangular, Path [1] https://css-tricks.com/a-complete-guide-to-css-gradients/ [2] https://xd.adobe.com/ideas/principles/web-design/gradient-color-definition/ [3] https://www.creativebloq.com/computer-arts/how-master-gradients-photoshop-51411514 [4] https://learn.microsoft.com/en-us/office/vba/api/office.msogradientstyle [5] https://www.officetooltips.com/office_365/tips/fill_and_outline_options_in_microsoft.html -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153839] Exporting to xhtml results in most of the tags and content in one single line
https://bugs.documentfoundation.org/show_bug.cgi?id=153839 --- Comment #5 from Commit Notification --- Franklin Weng committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/d2e8705c9cc503afdaed366b1f71ed012b0c568f tdf#153839: add newline after certain tags 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 153839] Exporting to xhtml results in most of the tags and content in one single line
https://bugs.documentfoundation.org/show_bug.cgi?id=153839 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 154050] Crashes when inserting or changing a note in Calc With Standard Toolbar (Single Mode) enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=154050 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 96190] Date in Form shows different values in Datefield and Formatted Field, if based on an integer Column
https://bugs.documentfoundation.org/show_bug.cgi?id=96190 --- Comment #12 from Robert Großkopf --- Bug is still the same in LO 7.5.1.2 on OpenSUSE 15.3 64bit rpm Linux. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153977] Bad quality of opened PDFs in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=153977 Kurosh Tavassoli changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #4 from Kurosh Tavassoli --- I'm so sorry, I can't reproduce the bug myself as well. I'll try to reproduce the bug and report it if I could. Thanks. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153609] Elementary's Book Preview icon not distinct enough to Two Pages Preview
https://bugs.documentfoundation.org/show_bug.cgi?id=153609 Rizal Muttaqin changed: What|Removed |Added CC||riz...@libreoffice.org --- Comment #2 from Rizal Muttaqin --- (In reply to Stéphane Guillou (stragu) from comment #1) > Created attachment 185363 [details] > Highlighted icons in LO 7.6, Elementary icons, GNOME dark mode Oh yes I kind of agree since elementary use non-folded paper as the representation. Do you think the icons should have folded part? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154084] CALC Rogue URL addresses
https://bugs.documentfoundation.org/show_bug.cgi?id=154084 --- Comment #1 from Colin --- Created attachment 185854 --> https://bugs.documentfoundation.org/attachment.cgi?id=185854=edit Calc Demonstrating the issue -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154084] New: CALC Rogue URL addresses
https://bugs.documentfoundation.org/show_bug.cgi?id=154084 Bug ID: 154084 Summary: CALC Rogue URL addresses Product: LibreOffice Version: 7.4.5.1 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: trivial Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: that.man.co...@gmail.com Description: Where a column of anchored and resized URL "Buttons" has been created, double-clicking any "empty" cell will produce a URL address hint at locations in the "URL Column" when the mouse is moved to hover in that column. The hint is dynamic and will change as the cursor is scrolled over a lower or higher cell. It is not necessary to click to focus the new cell, just hovering will produce the effect. If hovering over the first vacant cell below the column of buttons, the rogue hint is for the URL in row 11. Scrolling up "on top of" the existing buttons it will only cycle the rogue hint as far back as the genuine first link address. I have no idea why the first "uncluttered" cell produces the link address for row 11. Steps to Reproduce: Utilising the attached CALC, double-click F424 Observe that a rogue URL Hint will appear at that location Move your mouse cursor to any location in the column and observe how the hint is dynamic, reflecting the anticipated incremental address. It is not necessary to click or focus in any way - a simple mouse hover will elicit the rogue response. There is a nominal pause when the mouse moves over the page layout marquee. Actual Results: Rogue hint produced Expected Results: nothing Reproducible: Always User Profile Reset: No Additional Info: Version: 7.4.5.1 (x64) / LibreOffice Community Build ID: 9c0871452b3918c1019dde9bfac75448afc4b57f CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: sv-SE (en_GB); UI: en-GB Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154077] Drop Common/InternalMSExport/UseOldExport config key completely
https://bugs.documentfoundation.org/show_bug.cgi?id=154077 Buovjaga changed: What|Removed |Added Keywords||topicCleanup Ever confirmed|0 |1 CC|ilmari.lauhakangas@libreoff | |ice.org | Status|UNCONFIRMED |NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154068] LO_Style_design
https://bugs.documentfoundation.org/show_bug.cgi?id=154068 --- Comment #5 from Roman --- (In reply to V Stuart Foote from comment #4) > link in comment 3 provides method to set > > Tools -> Options -> View "Appearance" change from System to Light|Dark as > you prefer. That's it, he does not react as he was black, and he remained so Вот именно не реагирует он как был чёрным, так и остался им -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153780] Draw has problems with displaying cropped images and SVGs
https://bugs.documentfoundation.org/show_bug.cgi?id=153780 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 150858] Italian corrector "perchè', ciò'"
https://bugs.documentfoundation.org/show_bug.cgi?id=150858 --- Comment #8 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154019] UI string "Scale" is misleading
https://bugs.documentfoundation.org/show_bug.cgi?id=154019 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154016] Libreoffice Math Crash when scrolling through "element categories"
https://bugs.documentfoundation.org/show_bug.cgi?id=154016 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150266] Program does not continue where it left off.
https://bugs.documentfoundation.org/show_bug.cgi?id=150266 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 150858] Italian corrector "perchè', ciò'"
https://bugs.documentfoundation.org/show_bug.cgi?id=150858 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 148800] Print size decreases when highlighting or replacing a word.
https://bugs.documentfoundation.org/show_bug.cgi?id=148800 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150266] Program does not continue where it left off.
https://bugs.documentfoundation.org/show_bug.cgi?id=150266 --- Comment #6 from QA Administrators --- Dear holtecaydi, 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 149721] LO doesn't jump to last edited page
https://bugs.documentfoundation.org/show_bug.cgi?id=149721 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 149721] LO doesn't jump to last edited page
https://bugs.documentfoundation.org/show_bug.cgi?id=149721 --- Comment #4 from QA Administrators --- Dear Stu Corpe, 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 150887] LibreOffice only works in safe mode
https://bugs.documentfoundation.org/show_bug.cgi?id=150887 --- Comment #3 from QA Administrators --- Dear FLAVIO, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147147] Display of UI is very large on Mac
https://bugs.documentfoundation.org/show_bug.cgi?id=147147 --- Comment #4 from QA Administrators --- Dear Tony, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148800] Print size decreases when highlighting or replacing a word.
https://bugs.documentfoundation.org/show_bug.cgi?id=148800 --- Comment #5 from QA Administrators --- Dear howaz, 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 144388] Libreoffice 7.2 upgrade after install the office suite won't launch
https://bugs.documentfoundation.org/show_bug.cgi?id=144388 --- Comment #4 from QA Administrators --- Dear Robin, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96615] Repainting issues when the focus is in the footer
https://bugs.documentfoundation.org/show_bug.cgi?id=96615 --- Comment #9 from QA Administrators --- Dear szotsaki, 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 96620] Chart is lost as soon as custom formatting is involved
https://bugs.documentfoundation.org/show_bug.cgi?id=96620 --- Comment #7 from QA Administrators --- Dear szotsaki, 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 140325] Frame content not properly rendered after certain steps
https://bugs.documentfoundation.org/show_bug.cgi?id=140325 --- Comment #7 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 42040] Scrolling with Mouse Wheel sticks in Form Fields and Comment Boxes
https://bugs.documentfoundation.org/show_bug.cgi?id=42040 --- 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 96190] Date in Form shows different values in Datefield and Formatted Field, if based on an integer Column
https://bugs.documentfoundation.org/show_bug.cgi?id=96190 --- Comment #11 from QA Administrators --- Dear Robert Großkopf, 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 138841] Windows installer display tiny icon under high resolution
https://bugs.documentfoundation.org/show_bug.cgi?id=138841 --- Comment #15 from QA Administrators --- Dear Chaoting Liu, 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 115038] Umlaute (mutation) will be shown wrong in some objects when you type them first
https://bugs.documentfoundation.org/show_bug.cgi?id=115038 --- Comment #15 from QA Administrators --- Dear Karsten, 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 100951] [EDITING] Font colour picker doesn't show current colour
https://bugs.documentfoundation.org/show_bug.cgi?id=100951 --- Comment #7 from QA Administrators --- Dear szotsaki, 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 100958] [EDITING] Cannot demote list item
https://bugs.documentfoundation.org/show_bug.cgi?id=100958 --- Comment #6 from QA Administrators --- Dear szotsaki, 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 100565] Graphic redraw problems with multiple windows
https://bugs.documentfoundation.org/show_bug.cgi?id=100565 --- Comment #14 from QA Administrators --- Dear welliben, 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 154083] New: LibreOffice & Calc 7.4.5 don't start
https://bugs.documentfoundation.org/show_bug.cgi?id=154083 Bug ID: 154083 Summary: LibreOffice & Calc 7.4.5 don't start Product: LibreOffice Version: 7.4.5.1 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rpl01...@gmail.com Description: just downloaded it and did system Restart. Now clicking on any LibreOffice or Calc document or starting Office from Windows Start has no effect. No error message, no dialog box. Restarted again, same result. Windows Start in Safe Mode same result. The command line command libreoffice --safe-mode gives a dialog box "Windows cannot find LibreOffice". 64-bit Windows 10 on a Lenovo X1 carbon. Have been using LibreOffice all the time for over a year now. Issued a bug report involving what seems to be a mutex mess-up in Calc earlier today before downloading 7.4.5, if that as any connection. Actual Results: see Description. Expected Results: see Description Reproducible: Always User Profile Reset: Yes Additional Info: re user profile: using soffice.com -env:UserInstallation=file:///c:/my-test-profile results in ...>soffice.com -env:UserInstallation=file:///c:/my 'soffice.com' is not recognized as an internal or external command, operable program or batch file. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154082] FILEOPEN DOCX: section starts after the top margin of the first paragraph in the section
https://bugs.documentfoundation.org/show_bug.cgi?id=154082 --- Comment #1 from Justin L --- It is probably worth nothing that the PDF is not actually a perfect representation of how it appears in MS Word 2019 - apparently what you see is not what you export to pdf. (Mainly the background colouring is off. The focus in any case is the position of the text relative to the top of the column, which is accurately shown in the PDF.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154082] FILEOPEN DOCX: section starts after the top margin of the first paragraph in the section
https://bugs.documentfoundation.org/show_bug.cgi?id=154082 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3964 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131304] [META] MS Word compatibilityMode = 15
https://bugs.documentfoundation.org/show_bug.cgi?id=131304 Bug 131304 depends on bug 153964, which changed state. Bug 153964 Summary: FILEOPEN DOCX COMPAT15: paragraph top margin should only apply once - affecting page/col breaks https://bugs.documentfoundation.org/show_bug.cgi?id=153964 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153964] FILEOPEN DOCX COMPAT15: paragraph top margin should only apply once - affecting page/col breaks
https://bugs.documentfoundation.org/show_bug.cgi?id=153964 Justin L changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |jl...@mail.com |desktop.org | See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4082 Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #8 from Justin L --- Actually, let me close it since the description is all over the place. I'll open a new ticket to deal specifically with the section difference. bug 154082 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107738] [META] Section bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107738 Justin L changed: What|Removed |Added Depends on||154082 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154082 [Bug 154082] FILEOPEN DOCX: section starts after the top margin of the first paragraph in the section -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104520] [META] DOCX (OOXML) bug tracker
https://bugs.documentfoundation.org/show_bug.cgi?id=104520 Justin L changed: What|Removed |Added Depends on||154082 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154082 [Bug 154082] FILEOPEN DOCX: section starts after the top margin of the first paragraph in the section -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154082] New: FILEOPEN DOCX: section starts after the top margin of the first paragraph in the section
https://bugs.documentfoundation.org/show_bug.cgi?id=154082 Bug ID: 154082 Summary: FILEOPEN DOCX: section starts after the top margin of the first paragraph in the section Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Keywords: filter:docx, notBibisectable Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jl...@mail.com CC: jl...@mail.com Blocks: 104520, 107738 If a section starts with a back-ground coloured paragraph and a top margin of 100pts, you would expect to see a large coloured block above the text. And normally you do, except at the start of a section - where the block is just "empty". This is especially noticeable when the section has columns. The other columns don't start "at the top of the page", but "after the 100pt top margin". In other words, they are automatically aligned with the first paragraph's text. This is a fundamental difference between LO and MS Word. See bug 153964 where this was initially discussed, and is demonstrated by attachment 185823: sectionStart.odt. To reproduce: -open attachment 185749: columnMargin15.docx It should look like the compat15 version in attachment 185748. This is not bibisectable. I don't care if earlier versions imported the DOCX as page-columns instead of section-columns. The point of the bug report is about sections, so use sectionStart.odt if you want to do any bibisecting. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=104520 [Bug 104520] [META] DOCX (OOXML) bug tracker https://bugs.documentfoundation.org/show_bug.cgi?id=107738 [Bug 107738] [META] Section bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153964] FILEOPEN DOCX COMPAT15: paragraph top margin should only apply once - affecting page/col breaks
https://bugs.documentfoundation.org/show_bug.cgi?id=153964 Justin L changed: What|Removed |Added Whiteboard|target:7.6.0| Assignee|jl...@mail.com |libreoffice-b...@lists.free ||desktop.org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154081] Unnumbered headings influence the numbering of numbered headings
https://bugs.documentfoundation.org/show_bug.cgi?id=154081 sdc.bla...@youmail.dk changed: What|Removed |Added Keywords||possibleRegression Blocks||103370 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103370 [Bug 103370] [META] Heading Numbering bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103370] [META] Heading Numbering bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103370 sdc.bla...@youmail.dk changed: What|Removed |Added Depends on||154081 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154081 [Bug 154081] Unnumbered headings influence the numbering of numbered headings -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154081] New: Unnumbered headings influence the numbering of numbered headings
https://bugs.documentfoundation.org/show_bug.cgi?id=154081 Bug ID: 154081 Summary: Unnumbered headings influence the numbering of numbered headings 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 185853 --> https://bugs.documentfoundation.org/attachment.cgi?id=185853=edit demonstration of problem Attachment demonstrates the problem. 1. Tools - Chapter (Heading) Numbering, assign: Level Numbering 1 1,2,3 2 A,B,C show 2 sublevels 3 none show 3 sublevels (i.e., first two outline levels get numbering, third does not) Test document w/ three paragraphs with following PS 1 Heading 1 Heading 3 1.A heading 2 Critical "test": What numbering shown for outline level 2 (i.e., third paragraph)? RESULTS: Actual and expected (in 7.2.7.2): 1.A heading 2 Actual in 7.6.0.0.alpha0+: 1.B heading 2 Expected: 1.A heading 2 Additional test: Change unnumbered level 3 paragraph to "Text Body", then numbering on level 2 paragraph is as expected. => presence of unnumbered outline level 3 paragraph appears to increase the numbering for the outline level 2 paragraph. => seems like possible regression, because works as expected in 7.2.7.2 Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: a179f6c91692076e7e17babf4890638caa398384 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 133764] [META] Very large spreadsheets problem
https://bugs.documentfoundation.org/show_bug.cgi?id=133764 Bug 133764 depends on bug 148143, which changed state. Bug 148143 Summary: CRASH: after pasting twice the whole sheet https://bugs.documentfoundation.org/show_bug.cgi?id=148143 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154069] no link to relevant help page for "Create new user-defined index"
https://bugs.documentfoundation.org/show_bug.cgi?id=154069 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 154080] Comment indicator is too small, non-circumspect, easy to miss
https://bugs.documentfoundation.org/show_bug.cgi?id=154080 Eyal Rozenberg changed: What|Removed |Added Severity|enhancement |minor -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152887] Online/automatic accessibility check needs new icons for the status bar
https://bugs.documentfoundation.org/show_bug.cgi?id=152887 Rizal Muttaqin changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |riz...@libreoffice.org |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152887] Online/automatic accessibility check needs new icons for the status bar
https://bugs.documentfoundation.org/show_bug.cgi?id=152887 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 154066] Unable to undo attributes part of cell's area
https://bugs.documentfoundation.org/show_bug.cgi?id=154066 m.a.riosv changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED CC||miguelangelrv@libreoffice.o ||rg --- Comment #3 from m.a.riosv --- *** This bug has been marked as a duplicate of bug 154044 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154044] Undoing the first applied cell formatting only works for column A
https://bugs.documentfoundation.org/show_bug.cgi?id=154044 m.a.riosv changed: What|Removed |Added CC||nfsmob...@mail.ru --- Comment #2 from m.a.riosv --- *** Bug 154066 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 154080] Comment indicator is too small, non-circumspect, easy to miss
https://bugs.documentfoundation.org/show_bug.cgi?id=154080 m.a.riosv changed: What|Removed |Added Severity|normal |enhancement -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151273] With qt5 and qfont, characters overlap in autofit text box, unreadable
https://bugs.documentfoundation.org/show_bug.cgi?id=151273 --- Comment #19 from Eyal Rozenberg --- (In reply to Michael Weghorn from comment #18) > (In reply to Eyal Rozenberg from comment #15) > What we can still consider is switching the default from 2) to 1), i.e. > people that only set SAL_USE_VCLPLUGIN=qt5 get the more mature Cairo > rendering by default. And then introduce some new environment variable > (maybe sth like SAL_VCL_QT5_USE_QFONT_RENDERING) to explicitly switch to the > experimental QFont rendering. I'm very much in favor of that: The default should be the more robustly-implemented alternative. Unless there's some strong argument to the contrary I'm not aware of? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154075] Calc's F4 absolute cycle is sub-optimal when starting from a sheet-only absolute reference
https://bugs.documentfoundation.org/show_bug.cgi?id=154075 --- Comment #6 from Justin L --- (In reply to ady from comment #3) > I cannot reproduce your sequence. Sorry - I mis-read. I thought you said there was an existing case where your SUGGESTION was followed. Although I have no intention of proposing that this be accepted, I have coded up your suggested sequence. https://gerrit.libreoffice.org/c/core/+/148516 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153410] Style list changes scroll bar position to 'active' style after deleting a style
https://bugs.documentfoundation.org/show_bug.cgi?id=153410 --- Comment #6 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #5) > The Stylist is a single-selection tree where one node is always selected. It doesn't have to have one node always selected. It could be a single-selection tree in which _at most_ one node is selected. Also, that's only one of two options for resolving this bug. > After deleting the selected node the currently active style becomes > selected. And by default the tree scrolls to this position to give proper > feedback. How is that feedback in any way proper? Typically, the focused element's style has not even changed, and the selected item before the deletion was not the active one. So how is such feedback in any way related to what the user has just done? No, this is _improper_ feedback. Wrong feedback. A bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153792] Chart with drawing object going beyond the chart results in distorted, scaled down chart elements
https://bugs.documentfoundation.org/show_bug.cgi?id=153792
--- Comment #6 from wpeat...@gmail.com ---
In my version of LibO (7.2.7.2) and OS (Windoze), I always get funny behavior
when I have a drawn line in a chart and then copy and paste said chart. It
doesn't matter if the line is inside or outside the chart axes. It can be a
regular line or a freeform line.
So to respond to stragu and vsfoote, the only way I know to create a line that
extends outside the chart area is to copy and paste the chart and it will
happen automatically. If you look at the attached file, the original chart is
on the first sheet ("data and chart"). The pasted charts are on the second
sheet ("chart copies").
Other drawing objects are well behaved. Boxes, text boxes. Even callouts (which
have lines) will copy and paste fine.
Polygons are wonky. You can't draw them inside of a chart. But if you paste one
inside of a chart, it will not behave well when the whole chart is copied and
pasted.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137931] Show the UI selection dialog on first start-up
https://bugs.documentfoundation.org/show_bug.cgi?id=137931 --- Comment #14 from Eyal Rozenberg --- About a light/dark choice on that dialog: Do you guys also want that choice to be available via View | User Interface on the menus , or do you want a different, special dialog for the first startup? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154080] Comment indicator is too small, non-circumspect, easy to miss
https://bugs.documentfoundation.org/show_bug.cgi?id=154080 Eyal Rozenberg changed: What|Removed |Added Summary|Comment indicator is too|Comment indicator is too |non-circumspect, easy to|small, non-circumspect, |miss|easy to miss --- Comment #5 from Eyal Rozenberg --- I'll clarify the ask here: It's not about the size per se, but the visibility. If the indicator is visible enough, I don't mind that it's small. Enlargment is just one possible way of increasing its visibility. I'll also repeat a comment I made on bug 153106: The patch for 91415 improved the situation by switching to a triangle for, which I find more visible (but it also introduced scaling at different zoom levels, which may be problematic.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154080] Comment indicator is too non-circumspect, easy to miss
https://bugs.documentfoundation.org/show_bug.cgi?id=154080 Eyal Rozenberg changed: What|Removed |Added Summary|Comment indicator is too|Comment indicator is too |small, non-circumspect, |non-circumspect, easy to |easy to miss|miss -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 56677] Comment indicator too small
https://bugs.documentfoundation.org/show_bug.cgi?id=56677 --- Comment #7 from Eyal Rozenberg --- To followers of the old bug: I claim that this has _not_ been fixed, at least not in the release version. You may also want to look at what's happened on bug 91415, which has bearing on this. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147760] DOCX export: Writer adds timestamps to the anonymized tracked changes
https://bugs.documentfoundation.org/show_bug.cgi?id=147760 László Németh changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||6904 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136904] Crash swlo!SwRedlineData::operator!=+0x177 (steps in comment 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=136904 László Németh changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||7760 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136904] Crash swlo!SwRedlineData::operator!=+0x177 (steps in comment 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=136904 László Németh changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||1176 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Bug 133092 depends on bug 136904, which changed state. Bug 136904 Summary: Crash swlo!SwRedlineData::operator!=+0x177 (steps in comment 7) https://bugs.documentfoundation.org/show_bug.cgi?id=136904 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 83946] [META] Tracking changes issues
https://bugs.documentfoundation.org/show_bug.cgi?id=83946 Bug 83946 depends on bug 136904, which changed state. Bug 136904 Summary: Crash swlo!SwRedlineData::operator!=+0x177 (steps in comment 7) https://bugs.documentfoundation.org/show_bug.cgi?id=136904 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136904] Crash swlo!SwRedlineData::operator!=+0x177 (steps in comment 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=136904 László Németh changed: What|Removed |Added Assignee|nem...@numbertext.org |libreoffice-b...@lists.free ||desktop.org Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #19 from László Németh --- @Telesto: very nice catch! Thanks! @Xisco, Buovjaga, Hossein: Thanks for bibisecting and feedback! Commit description: tdf#136904 tdf#116084 tdf#121176 sw: fix Undo & anonymized w:del in w:ins Undo/Redo crash resulted by the workaround for anonymized w:del in w:ins. Anonymized (no time stamp) redlines are loaded with Epoch time (1970-01-01) since commit 2c51746997478ad5d0e7cc64aa6489769c473d43 "tdf#146171 DOCX: fix loss of change tracking, if no date", so it's possible to fix the original DOCX import problem using this value: don't combine anonymized deletion inside/over anonymized insertion, and remove all the workaround, keeping only their adjusted unit tests, and add new tests for the export fixed finally, which keeps anonymized w:del in anonymized w:ins. Revert commit 2de1fd7d8b8bd42c66190140cc4506df0c3367f1 "tdf#125187 DOCX track changes: fix w:del within w:ins", commit df4f405a153603551f67e289bbaccf9ac39b923c "tdf#121176 DOCX track changes: same size w:del in w:ins" and commit 7a810d6a9fb79a24d00e5dbd8e1223e6f8b09677 "tdf#116084 DOCX track changes: fix w:del within w:ins". Regression from commit 2de1fd7d8b8bd42c66190140cc4506df0c3367f1 "tdf#125187 DOCX track changes: fix w:del within w:ins". See also commit 64dcedcf7c073d1819794d68a33651b14877e1b5 "tdf#147760 tdf#142902 DOCX export: anonymize date and moveFromRangeStart". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153106] Revert commit of Bug 91415 - Scale Calc's comment indicator with zoom level (please, do not)
https://bugs.documentfoundation.org/show_bug.cgi?id=153106 --- Comment #22 from Eyal Rozenberg --- (In reply to ady from comment #21) > > I disagree with that. On the contrary, I see it as a problem if the comment > > indicator does not draw your attention. > > Yes, if that were to be a problem. It has definitely been a problem: bug 56677. But the "fix" was insufficient in my opinion. Things have certainly not gotten to the level of visibility of MS Excel, and in absolute terms - it's really not good enough. > There is no report claiming that the comment indicator cannot be seen. There is now: Bug 154080. > The user should be able to see it, but it > should not be "the main thing"; that would be distracting. It _needs_ to distract - while not interfering with the visibility of the actual cell contents. > (In reply to Eyal Rozenberg from comment #20) > > There are (at least) two usability considerations/problems regarding comment > > indications: > > > > 1. On one hand, it's a problem when comment indicators hide content. > > 2. On the other hand, it's a problem if comment indicators are not > > clearly-visible, as I might inadvertently miss them > > > > Bug 91415 was opened regarding the first usability problem, not the second > > one. Also, bug 91415 did not ask for any changes at high zoom levels - it > > regarded the situation without playing with the zoom level. > > That sounds as if the request explicitly said "I cannot use the zoom feature > to solve this" A bug was reported in the behavior without the user applying zoom. Whatever changes in the behavior when zooming in or out cannot resolve the bug. > The reason users do not mention zoom in bug 91415 is > because they are simply not aware that the zoom feature resolves the problem. No, that's not the reason, and no, it doesn't resolve the problem. ... which is also why the patch should not have included scaling at different zoom levels - because zoom is irrelevant to the bug. > There is no physical way to > _simultaneously_ see more details and to see "the big picture" in the same > UI. That's the reason to use zoom. Of course there is. More than one way even. The use of the triangle shape rather than the dot/small square is one such way. One can think of others. > I could take almost any cell, with a clear visible text and indicator, scale > the zoom factor to, say, 20%, and show how it is an inconvenience. It doesn't matter what happens at zoom 20% nor at zoom 500%. Both cell contents, and comment indicators, must be clearly visible at zoom 100%. (or rather - it does matter, but not in the context of bug 91415.) Anyway, I don't understand why you're arguing with one of the people who agrees with you. In fact, you're undermining your own request for back-out by claiming that what happens at different zoom levels has bearing on 91415. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154061] CRASH: undoing column insert
https://bugs.documentfoundation.org/show_bug.cgi?id=154061 --- Comment #2 from Paris Oplopoios --- I added a patch that seems to fix this issue https://gerrit.libreoffice.org/c/core/+/148492 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154080] Comment indicator is too small, non-circumspect, easy to miss
https://bugs.documentfoundation.org/show_bug.cgi?id=154080 --- Comment #4 from Eyal Rozenberg --- Created attachment 185852 --> https://bugs.documentfoundation.org/attachment.cgi?id=185852=edit Screenshot of calc window with attachment 185851 Note how the triangles for text exceeding cell boundaries are also a bit similar to comment indicators, helping camouflage it even further. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154080] Comment indicator is too small, non-circumspect, easy to miss
https://bugs.documentfoundation.org/show_bug.cgi?id=154080 Eyal Rozenberg changed: What|Removed |Added Attachment #185850|0 |1 is obsolete|| --- Comment #3 from Eyal Rozenberg --- Created attachment 185851 --> https://bugs.documentfoundation.org/attachment.cgi?id=185851=edit Calc sheet with comments and surrounding text -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154080] Comment indicator is too small, non-circumspect, easy to miss
https://bugs.documentfoundation.org/show_bug.cgi?id=154080 --- Comment #2 from Eyal Rozenberg --- Created attachment 185850 --> https://bugs.documentfoundation.org/attachment.cgi?id=185850=edit Calc sheet with comments -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154080] Comment indicator is too small, non-circumspect, easy to miss
https://bugs.documentfoundation.org/show_bug.cgi?id=154080 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=56 ||677 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 56677] Comment indicator too small
https://bugs.documentfoundation.org/show_bug.cgi?id=56677 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4080 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153106] Revert commit of Bug 91415 - Scale Calc's comment indicator with zoom level (please, do not)
https://bugs.documentfoundation.org/show_bug.cgi?id=153106 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4080 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154080] Comment indicator is too small, non-circumspect, easy to miss
https://bugs.documentfoundation.org/show_bug.cgi?id=154080 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3106 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 91415] Improve design of comment indicators to block less of the cell's content
https://bugs.documentfoundation.org/show_bug.cgi?id=91415 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4080 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154080] Comment indicator is too small, non-circumspect, easy to miss
https://bugs.documentfoundation.org/show_bug.cgi?id=154080 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=91 ||415 --- Comment #1 from Eyal Rozenberg --- Bug 91415 asks that the comment indicator block less of the cell's contents. That _may_ be contradictory to the request in this bug, but - perhaps not really. Part of the problem with noticing the comment indicator is the overlap with the cell contents - making the indicator "camouflaged" by the cell contents. Also, please note that zooming in / zooming out and their effect on the comment indicator are not relevant to this bug: I want to notice the comment indicators _without_ having to play with the zoom. If I already know the indicator is there, the problem is kind of solved to begin with. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154072] crash / no effect when clicking some dropdown buttons when toolbar overflows
https://bugs.documentfoundation.org/show_bug.cgi?id=154072 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #3 from Stéphane Guillou (stragu) --- Confirmed via duplicate bug 154079. Seems to be Wayland-related? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154079] Crash if I try to open any drop down selection menu when the window is resized in Ubuntu 22.10
https://bugs.documentfoundation.org/show_bug.cgi?id=154079 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #3 from Stéphane Guillou (stragu) --- I happen to have reported the same issue just a few hours before you in bug 154072. Marking as a duplicate. Thank you! *** This bug has been marked as a duplicate of bug 154072 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154072] crash / no effect when clicking some dropdown buttons when toolbar overflows
https://bugs.documentfoundation.org/show_bug.cgi?id=154072 Stéphane Guillou (stragu) changed: What|Removed |Added CC||md.ashikurrahmanasif@proton ||mail.com --- Comment #2 from Stéphane Guillou (stragu) --- *** Bug 154079 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 154080] New: Comment indicator is too small, non-circumspect, easy to miss
https://bugs.documentfoundation.org/show_bug.cgi?id=154080 Bug ID: 154080 Summary: Comment indicator is too small, non-circumspect, easy to miss Product: LibreOffice Version: 7.4.5.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com Bug 56677 was marked as fixed. But - it wasn't fixed AFAIAC. The comment indicator is much too small and easy to miss - when the cell is not empty. See the attached document. Without paying close attention, one is quite likely to miss the indicator - especially in the upper cell with the comment. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154075] Calc's F4 absolute cycle is sub-optimal when starting from a sheet-only absolute reference
https://bugs.documentfoundation.org/show_bug.cgi?id=154075 --- Comment #5 from ady --- (In reply to Justin L from comment #4) > please provide the > exact formula/steps that you are following to trigger this cycle. Using: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 0484a9a3f5e2ecb678f6fb41bbb251529e89c00d CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (es_AR); UI: en-US Calc: CL threaded Built 2023.03.07 1. Open new Calc with Sheet1 and Sheet2 2. With the focus on Sheet1.A1, click on the "=" icon on the Formula bar. 3. Click on Sheet2's tab. 4. Click on Sheet2.A1 (do _not_ press [enter]) 5. Currently the Formula bar shows $Sheet2.A1 (step 0), still in edit mode (the formula is not yet fully introduced). By pressing F4 we cycle: Sheet2.$A$1 Sheet2.A$1 Sheet2.$A1 Sheet2.A1 $Sheet2.$A$1 $Sheet2.A$1 $Sheet2.$A1 $Sheet2.A1 > we are back to the same status as step 0 above. At any given step, we can press [enter]. Evidently, when users type-in the formula, there is no "default" type of reference, other than whatever they typed-in. From that point, the cycle should be in the same order as I described, depending on what they initially typed-in. The concept of "default" references are relevant for 2 alternative situations: * when clicking on the cells (while building the formula; that is, the function is typed-in, and the arguments are selected by mouse+click); or, * when using the Formula wizard, in which case the "default" type of references varies depending on the function and the argument. Unfortunately, while using the Formula Wizard (whether in full mode or shrink mode), the F4 key doesn't work (I wished it would, because it saves a lot of time when it works in it, in other spreadsheet programs). So I am mentioning here the first alternative, as I just described. Hopefully this clarifies the steps / procedure. From it, I am suggesting to change the behavior as I posted in comment 1. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 81545] Manual column break misplaced after copy-paste
https://bugs.documentfoundation.org/show_bug.cgi?id=81545 --- Comment #16 from Jean-Baptiste Faure --- Nothing changed in Version: 7.5.2.0.0+ (X86_64) / LibreOffice Community Build ID: 1c7b700179afda772af0f004e7ba497ba42fd8fc CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Ubuntu_20.04_x86-64 Calc: threaded Best regards. JBF -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139902] [META] PPTX Image issues
https://bugs.documentfoundation.org/show_bug.cgi?id=139902 Gabor Kelemen (allotropia) changed: What|Removed |Added Depends on||153466 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153466 [Bug 153466] Slide imported from PPTX with custom sized background image. When opened in Impress it loses the settings and changes from tile to stretched. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154071] Request: Rename "Square" gradient to "Rectangle" gradient in the UI
https://bugs.documentfoundation.org/show_bug.cgi?id=154071 Telesto changed: What|Removed |Added CC||heiko.tietze@documentfounda ||tion.org, ||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154075] Calc's F4 absolute cycle is sub-optimal when starting from a sheet-only absolute reference
https://bugs.documentfoundation.org/show_bug.cgi?id=154075 --- Comment #4 from Justin L --- (In reply to ady from comment #3) I cannot reproduce your sequence. If I just type in the formula area "=$Sheet1.$A$1" and then cycle with F4 I get: -$Sheet1.B$2 = sheet + row (aka 6) -$Sheet1.$B2 = sheet + col (aka 5) -$Sheet1.B2 = sheet (aka 4) - you said this would become Sheet.B2 (aka 0) -Sheet1.$B$2 = cell (aka 3) -Sheet1.B$2 = row (aka 2) -Sheet1.$B2 = col (aka 1) -Sheet1.B2 = relative (aka 0) - you said this would become $Sheet.B2 (aka 4) I'm pretty sure you are mistaken because the code path I found is a very simple "subtract by 1" formula. If you are not mistaken, please provide the exact formula/steps that you are following to trigger this cycle. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154079] Crash if I try to open any drop down selection menu when the window is resized in Ubuntu 22.10
https://bugs.documentfoundation.org/show_bug.cgi?id=154079 md.ashikurrahmana...@protonmail.com changed: What|Removed |Added Summary|Crash if I try to open any |Crash if I try to open any |drop down selection menu|drop down selection menu |when the window is tiled in |when the window is resized |Ubuntu 22.10|in Ubuntu 22.10 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154079] Crash if I try to open any drop down selection menu when the window is tiled in Ubuntu 22.10
https://bugs.documentfoundation.org/show_bug.cgi?id=154079 md.ashikurrahmana...@protonmail.com changed: What|Removed |Added CC|md.ashikurrahmanasif@proton | |mail.com| --- Comment #2 from md.ashikurrahmana...@protonmail.com --- The Terminal shows this error message after crashing: $ libreoffice (opened Writer and recreated the bug) Gdk-Message: 01:41:24.092: Error 71 (Protocol error) dispatching to Wayland display. $ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154079] Crash if I try to open any drop down selection menu when the window is tiled in Ubuntu 22.10
https://bugs.documentfoundation.org/show_bug.cgi?id=154079 md.ashikurrahmana...@protonmail.com changed: What|Removed |Added CC||md.ashikurrahmanasif@proton ||mail.com --- Comment #1 from md.ashikurrahmana...@protonmail.com --- Created attachment 185849 --> https://bugs.documentfoundation.org/attachment.cgi?id=185849=edit Shows how the program crashes This happens everytime when I need to use a small or tiled window. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154075] Calc's F4 absolute cycle is sub-optimal when starting from a sheet-only absolute reference
https://bugs.documentfoundation.org/show_bug.cgi?id=154075 --- Comment #3 from ady --- (In reply to ady from comment #2) > BTW, the suggested cycle is also already the current cycle when editing a > formula that was already introduced, for example by the Formula Wizard. Sorry, I think I was not clear enough. What I mean is that when having, for instance, $Sheet2.$A$1 already in the formula bar as part of a formula that was previously introduced, then getting into edit mode again and clicking on the reference, the F4 cycle continues in the same way as suggested. The point is that in such cases, there is also no disruption; the cycle continues in the same way as it is now. I hope I was clearer now. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154079] New: Crash if I try to open any drop down selection menu when the window is tiled in Ubuntu 22.10
https://bugs.documentfoundation.org/show_bug.cgi?id=154079 Bug ID: 154079 Summary: Crash if I try to open any drop down selection menu when the window is tiled in Ubuntu 22.10 Product: LibreOffice Version: 7.4.4.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: md.ashikurrahmana...@protonmail.com Description: When I make the maximized window resized or tiled to the point when the toolbar does not have enough space to show all the icons, any attempt to open a dropdown menu that is hidden under the two arrows of the toolbar crashes the window or just does not respond at all. When the window is at its regular state or maximized when the toolbar is wide open, the dropdown menu performs as it should. Steps to Reproduce: 1. Open a window (Writer/Calc/Impress/others) and resize the window to the point when the toolbar does not have enough space to show any of the dropdown menu icons (e.g. bullet list in Writer) and gets hidden under the two arrow to reach the other icons. 2. Click on the dropdown menu icon to open the dropdown menu (e.g. different bullet lists). Actual Results: The click does nothing and gets frozen for a while or just crashes the program. Expected Results: It should open a clickable dropdown menu and perform the clicked or selected task. Reproducible: Always User Profile Reset: Yes Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: StartModule [Information guessed from browser] OS: Ubuntu 22.10 OS is 64bit: yes -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154075] Calc's F4 absolute cycle is sub-optimal when starting from a sheet-only absolute reference
https://bugs.documentfoundation.org/show_bug.cgi?id=154075 --- Comment #2 from ady --- (In reply to ady from comment #1) > The suggestion is for the F4 cycle to work as follows: > 0. $Sheet2.A1 < this is before pressing F4 (no change) > > 1. $Sheet2.$A$1 > 2. $Sheet2.A$1 > 3. $Sheet2.$A1 > 4. Sheet2.A1 > 5. Sheet2.$A$1 > 6. Sheet2.A$1 > 7. Sheet2.$A1 > 8. $Sheet2.A1 > we are back to the same as step 0 above. > > So, the suggested cycle changes nothing regarding rows and columns. BTW, the suggested cycle is also already the current cycle when editing a formula that was already introduced, for example by the Formula Wizard. PS: having F4 also available when using the Formula Wizard would another RFE. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154072] crash / no effect when clicking some dropdown buttons when toolbar overflows
https://bugs.documentfoundation.org/show_bug.cgi?id=154072 --- Comment #1 from Martin Sourada --- I cannot reproduce the crash, but the dropdown buttons (e.g. border, color, currency) do nothing (just close the expanded panel) when they’re hidden. In 7.3 it works as expected, in 7.4 and 7.5 it's broken. Version: 7.5.0.1 (X86_64) / LibreOffice Community Build ID: 77cd3d7ad4445740a0c6cf977992dafd8ebad8df CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: cs-CZ Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154075] Calc's F4 absolute cycle is sub-optimal when starting from a sheet-only absolute reference
https://bugs.documentfoundation.org/show_bug.cgi?id=154075 ady changed: What|Removed |Added Summary|Cacl's F4 absolute cycle is |Calc's F4 absolute cycle is |sub-optimal when starting |sub-optimal when starting |from a sheet-only absolute |from a sheet-only absolute |reference |reference -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154075] Cacl's F4 absolute cycle is sub-optimal when starting from a sheet-only absolute reference
https://bugs.documentfoundation.org/show_bug.cgi?id=154075 --- Comment #1 from ady --- As of: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 0484a9a3f5e2ecb678f6fb41bbb251529e89c00d CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (es_AR); UI: en-US Calc: CL threaded Built 2023.03.07 Currently the cycle goes like this: 0. $Sheet2.A1 < this is before pressing F4. With successive F4, the cycle currently continues as: 1. Sheet2.$A$1 2. Sheet2.A$1 3. Sheet2.$A1 4. Sheet2.A1 5. $Sheet2.$A$1 6. $Sheet2.A$1 7. $Sheet2.$A1 8. $Sheet2.A1 > we are back to the same status as step 0 above. The suggestion is for the F4 cycle to work as follows: 0. $Sheet2.A1 < this is before pressing F4 (no change) 1. $Sheet2.$A$1 2. $Sheet2.A$1 3. $Sheet2.$A1 4. Sheet2.A1 5. Sheet2.$A$1 6. Sheet2.A$1 7. Sheet2.$A1 8. $Sheet2.A1 > we are back to the same as step 0 above. So, the suggested cycle changes nothing regarding rows and columns. FWIW and FYI, a little bit of background history... Absolute and relative references for cells/rows/columns are supported in every spreadsheet software, but relative references for worksheets is not as widely supported, and thus it is a less-known feature. Users that are unaware of the existence of relative references for worksheets used to complain that some formulas didn't work when copying entire worksheets several times (e.g. more than 2 worksheets with the first one as "template" or as “summarize”, or one plus a dozen worksheets that were not working all the same as they expected) and so they used to report the behavior as a bug; that is, without anyone knowing that the real problem was that the worksheets' references were relative, instead of the "expected" absolute reference, which was the only type they knew. The repetitive reports, forum posts, investigations and explanations were all reduced when the default worksheet reference was set as absolute instead of the prior relative reference. This was a few years back already. For most users, the suggested modified cycle should not have negative consequences, and the amount of F4s might probably be reduced rather than increased. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154076] Conditional formatting rules containing unquoted text only apply to empty cells
https://bugs.documentfoundation.org/show_bug.cgi?id=154076 --- Comment #2 from f --- I don't see such a dialog on my end, but I guess a documentation link is helpful. I did not realize there was a page for that, thank you. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154078] New: [EDITING][FILESAVE]:Finish Signing option in info-bar not functioning
https://bugs.documentfoundation.org/show_bug.cgi?id=154078 Bug ID: 154078 Summary: [EDITING][FILESAVE]:Finish Signing option in info-bar not functioning Product: LibreOffice Version: 7.5.1.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: pradyumnarut...@gmail.com Description: When trying to add signature using Insert > Signature Line to a pdf in LO-Draw, signature is not getting saved and not visible when opened in some pdf reader. Steps to Reproduce: 1.Open an existing pdf in LO Draw. 2.Then insert a signature by Insert -> Signature Line 3.Select some rectangular region in chosen pdf.This is where you want to add sign. 4.Select a certificate to sign and click on Finish Signing in Info-Bar. Actual Results: It is expected that a signature will be added when clicked on Finish Signing in Info-Bar and signature will be visible when opened in some pdf reader(e.g Adobe reader,WPS-Office). Expected Results: When clicked on Finish Signing in Info-Bar signature is not getting saved.And it is also not visible when opened in some pdf reader. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-IN (en_IN); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
