[Bug 57466] Change in UI user configuration will cause new UI items in next versions of LibreOffice to be invisible, when that previous userprofile is used
https://bugs.documentfoundation.org/show_bug.cgi?id=57466 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0513 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 153293] [META] Dark Mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=153293 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160513 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160513 [Bug 160513] Table guides and margin formatting aids not visible after upgrade from 7.5 to 7.6+: Application Colors' dark scheme not mapped to new scheme (comment 9) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 142074] [META] Application Colours settings bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=142074 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160513 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160513 [Bug 160513] Table guides and margin formatting aids not visible after upgrade from 7.5 to 7.6+: Application Colors' dark scheme not mapped to new scheme (comment 9) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 115518] [META] Old user profile causing problems when upgrading to new release
https://bugs.documentfoundation.org/show_bug.cgi?id=115518 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160513 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160513 [Bug 160513] Table guides and margin formatting aids not visible after upgrade from 7.5 to 7.6+: Application Colors' dark scheme not mapped to new scheme (comment 9) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160513] Table guides and margin formatting aids not visible after upgrade from 7.5 to 7.6+: Application Colors' dark scheme not mapped to new scheme (comment 9)
https://bugs.documentfoundation.org/show_bug.cgi?id=160513 Stéphane Guillou (stragu) changed: What|Removed |Added Version|7.6.6.3 release |7.6.0.3 release Ever confirmed|0 |1 OS|Windows (All) |All Hardware|x86 (IA32) |All See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=57 ||466 Summary|Table guides and margin |Table guides and margin |formatting aids not visible |formatting aids not visible |after upgrade from 7.5.9 to |after upgrade from 7.5 to |7.6.6 |7.6+: Application Colors' ||dark scheme not mapped to ||new scheme (comment 9) CC||heiko.tietze@documentfounda ||tion.org Status|UNCONFIRMED |NEW Blocks||142074, 115518, 153293 --- Comment #9 from Stéphane Guillou (stragu) --- (In reply to Ulrich Windl from comment #7) > Eventually I found the problem (see screenshot): > The "Schema" for user-defined colors was blank Great, we've now pinpointed the issue! So, in summary, it's: "Upgrade from 7.5 to 7.6+ does not map Application Colors scheme properly when profile kept" Steps to reproduce: 1. In LO 7.5, choose the "LibreOffice Dark" scheme in Tools > Options > LibreOffice > Application Colors > Color Scheme > Scheme 2. Exit, go to user profile directory, copy registrymodifications.xcu across to the user profile of a 7.6 installation 3. Open Writer 7.6 4. Insert table with Table > Insert table > OK Results: - no margin crosshairs - no table boundaries - Ctrl + F10: no margin lines - go to Tools > Options > LibreOffice > Application Colors > Custom Colors > Scheme: empty selection, and all optional elements in the list are ticker off. Same happens if going from 7.5 to 24.2. Note that this does not happen with a custom named scheme. Heiko, I assume this started with 5675937f7564fa5614f7be5aec0d7f20ba91d02c. Can we fix the mapping from: "Scheme = LibreOffice Dark" to: "Scheme = Automatic" + "Automatic = Dark" somehow ? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=115518 [Bug 115518] [META] Old user profile causing problems when upgrading to new release https://bugs.documentfoundation.org/show_bug.cgi?id=142074 [Bug 142074] [META] Application Colours settings bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=153293 [Bug 153293] [META] Dark Mode bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160525] Crash in: Edit::ImplSetText(rtl::OUString const &,Selection const *) when opening Bullets and Numbering dialog in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=160525 Stéphane Guillou (stragu) changed: What|Removed |Added Keywords||wantBacktrace Status|RESOLVED|NEW Resolution|WORKSFORME |--- --- Comment #4 from Stéphane Guillou (stragu) --- Indeed, there are still more issues. Using the same attachment, I still reproduce a crash with 24.2.2.2, but can't figure out a 100% consistent set of steps. It can happen on first opening of the dialog, or on the third go, and duplicate the slide or getting in and out of text box edit mode might help. Note that if the dialog does open and close successfully, there is an active drag-and-drop selection on the text for some reason. Might be related? Result: https://crashreport.libreoffice.org/stats/crash_details/15e22769-6691-47ab-b842-3766dfd0fdba -- You are receiving this mail because: You are the assignee for the bug.
[Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Bug 133092 depends on bug 160525, which changed state. Bug 160525 Summary: Crash in: Edit::ImplSetText(rtl::OUString const &,Selection const *) when opening Bullets and Numbering dialog in Impress https://bugs.documentfoundation.org/show_bug.cgi?id=160525 What|Removed |Added Status|RESOLVED|NEW Resolution|WORKSFORME |--- -- You are receiving this mail because: You are the assignee for the bug.
[Bug 48799] [META] Impress Bullets and Numbering bugs (formatting and UI)
https://bugs.documentfoundation.org/show_bug.cgi?id=48799 Bug 48799 depends on bug 160525, which changed state. Bug 160525 Summary: Crash in: Edit::ImplSetText(rtl::OUString const &,Selection const *) when opening Bullets and Numbering dialog in Impress https://bugs.documentfoundation.org/show_bug.cgi?id=160525 What|Removed |Added Status|RESOLVED|NEW Resolution|WORKSFORME |--- -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160559] I'm unable to open documents using Writer even after setting it as the default app.
https://bugs.documentfoundation.org/show_bug.cgi?id=160559 Mike Kaganski changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Mike Kaganski --- This is not a bug. There is no separate "Draw" or "Writer" in LibreOffice, they are just modules in the monolithic suite; and when the suite starts with a file name, it analyses the file structure, and decided which module to use. That is unless you pass the import filter explicitly, which is much more targeted than just telling which module to use. But then the question is, which file you are trying to open. Because there is not many file types that both Draw and Writer can open - I think that it's only PDF, for which Draw is the default application in the suite. And in truth, both aren't good options to handle PDF files, better alternatives exist (LibreOffice is not a PDF editing software)*. If that happens for a specific file type, please describe which. Then you might need to edit the Windows registry to associate these files with a specific command line, which would include the explicit import filter. * But see https://events.documentfoundation.org/media/libreoffice-conference-2023/submissions/JDSEVU/resources/LO_as_PDF_editor_sbZDN5T.pdf -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160559] New: I'm unable to open documents using Writer even after setting it as the default app.
https://bugs.documentfoundation.org/show_bug.cgi?id=160559 Bug ID: 160559 Summary: I'm unable to open documents using Writer even after setting it as the default app. Product: LibreOffice Version: 24.2.1.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sarahabdalwah...@gmail.com Description: I'm experiencing an issue where I'm unable to open documents using LibreOffice Writer, even after setting it as the default application for document files. Instead, when I attempt to open a document, it automatically opens with the LibreOffice Drawer. This occurs consistently, regardless of file type or method of attempted opening. Steps to Reproduce: 1. Open LibreOffice Writer. 2. Ensure that LibreOffice Writer is set as the default application for opening document files. 3. Attempt to open a document by double-clicking on the file in the file explorer or by selecting "Open" from the LibreOffice Writer file menu. 4. Additionally, try to open documents from outside LibreOffice Writer by right-clicking on the document file in the file explorer and selecting "Open with" > "LibreOffice Writer" from the context menu. Actual Results: opens in drawer Expected Results: Observe that the document still opens automatically in the LibreOffice Drawer instead of opening in LibreOffice Writer. Reproducible: Always User Profile Reset: No Additional Info: document open in writer -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160319] Calc: add constraints on Format Cells - Format Code
https://bugs.documentfoundation.org/show_bug.cgi?id=160319 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160312] Highlighting Calc cell when entering characters (not) in «Edit» mode
https://bugs.documentfoundation.org/show_bug.cgi?id=160312 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160311] SVG: Add support for feComponentTransfer
https://bugs.documentfoundation.org/show_bug.cgi?id=160311 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160496] Viewport jumps after moving cursor to different style
https://bugs.documentfoundation.org/show_bug.cgi?id=160496 --- Comment #7 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160496] Viewport jumps after moving cursor to different style
https://bugs.documentfoundation.org/show_bug.cgi?id=160496 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.
[Bug 157121] Files will not open, dialog boxes are blank. taskbar shows file open
https://bugs.documentfoundation.org/show_bug.cgi?id=157121 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157121] Files will not open, dialog boxes are blank. taskbar shows file open
https://bugs.documentfoundation.org/show_bug.cgi?id=157121 --- Comment #3 from QA Administrators --- Dear Michael M, 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.
[Bug 156298] Recorded macro in Writer is not saved when program quits in LibreOffice 7.3.7.2 new
https://bugs.documentfoundation.org/show_bug.cgi?id=156298 --- Comment #3 from QA Administrators --- Dear William, 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.
[Bug 156298] Recorded macro in Writer is not saved when program quits in LibreOffice 7.3.7.2 new
https://bugs.documentfoundation.org/show_bug.cgi?id=156298 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 145521] Default color set for the graphing should be changed to support chromatic vision.
https://bugs.documentfoundation.org/show_bug.cgi?id=145521 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 145521] Default color set for the graphing should be changed to support chromatic vision.
https://bugs.documentfoundation.org/show_bug.cgi?id=145521 --- Comment #4 from QA Administrators --- Dear moe.koto.mugi, 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.
[Bug 144966] Instead of having two tools "show" and "hide" have one called "toggle"
https://bugs.documentfoundation.org/show_bug.cgi?id=144966 --- Comment #3 from QA Administrators --- Dear Elmar, 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.
[Bug 98048] base doesn't wake up after windows suspension
https://bugs.documentfoundation.org/show_bug.cgi?id=98048 --- Comment #10 from QA Administrators --- Dear boicottms, 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.
[Bug 121995] Form preview shows content of the form very confused
https://bugs.documentfoundation.org/show_bug.cgi?id=121995 --- Comment #7 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.
[Bug 131702] Shape (copied from Draw) grows when pasted multiple times at the same position
https://bugs.documentfoundation.org/show_bug.cgi?id=131702 --- Comment #6 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.
[Bug 123890] When selected text starts with a slash, inserting a hyperlink creates one link for the slash and another for the rest
https://bugs.documentfoundation.org/show_bug.cgi?id=123890 --- Comment #7 from QA Administrators --- Dear msaghaei, 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.
[Bug 109299] Empty cells are not copied to external application like Notepad (while copied to another spreadsheet)
https://bugs.documentfoundation.org/show_bug.cgi?id=109299 --- Comment #20 from QA Administrators --- Dear Larsen, 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.
[Bug 160558] New: Calc shows incorrect words in portuguese ordinal numbers when formatting using [NatNum12 ordinal]
https://bugs.documentfoundation.org/show_bug.cgi?id=160558 Bug ID: 160558 Summary: Calc shows incorrect words in portuguese ordinal numbers when formatting using [NatNum12 ordinal] Product: LibreOffice Version: 24.2.2.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: juk...@crypape.com Description: I am using a custom number format with the specifiers `[NatNum 12 ordinal]` and `[NatNum12 ordinal-feminine]` and the numbers shown are written incorrectly, both in masculine and in feminine. This problem affects both Brazilian Portuguese and European Portuguese. A secondary, but inseparable problem is that Brazil is the only portuguese-speaking country that uses the short scale for big numbers. All others countries use the long scale. I dont know how big integers can get in Calc, so I only tested numbers up to multiples of 10^9. Steps to Reproduce: 1. Type a number in any cell. 2. Right-click and select Format Cells... 3. In the Numbers tab, use one of the following Format Codes: [NatNum12 ordinal]0 or [NatNum12 ordinal-feminine]0 4. Click OK. Actual Results: number -> ordinal(feminine ending) 40 -> cuadragésimo(a) 50 -> quincuagésimo(a) 400 -> quadrigentésimo(a) 700 -> septicentésimo(a) 800 -> octigentésimo(a) Greater than one thousand: 1000 -> milésimo(a) (This is one correct, but the next ones are not.) 2000 -> dois milésimo(a) 3000 -> três milésimo(a) 4000 -> quatro(a) milésimo(a) 5000 -> cinco(a) milésimo Greater than ten thousand: Simply do not exist. Greater than one hundred thousand: Simply do not exist. (For multiples of 10^4 and 10^5, the cell still shows the same arabic numbers. For other numbers it does not show the ordinals within this range in the long ordinal form.) Greater than a million: 1.000.000 -> milionésimo(a) (This is one correct, but the next ones are not.) 2.000.000 -> dois milionésimo(a) 3.000.000 -> três milionésimo(a) 4.000.000 -> quatro(a) milionésimo(a) ... (Brazil) 1.000.000.000 -> bilionésimo(a) (Correct, but the next ones are not.) 2.000.000.000 -> dois bilionésimo(a) 2.001.100.001 -> dois bilionésimo(a) milésimo(a) 3.000.000.000 -> três bilionésimo(a) 4.000.000.000 -> quatro(a) bilionésimo(a) (the rest) 1.000.000.000 -> bilionésimo(a) (incorrect, all should use long scale) 2.000.000.000 -> dois bilionésimo(a) 2.001.100.001 -> dois bilionésimo(a) milionésimo(a) 3.000.000.000 -> três bilionésimo(a) 4.000.000.000 -> quatro(a) bilionésimo(a) Expected Results: number -> ordinal(feminine ending) 40 -> quadragésimo(a) 50 -> quinquagésimo(a) 400 -> quadriNgentésimo(a) 700 -> septiNgentésimo(a) 800 -> octiNgentésimo(a) Greater than one thousand: 1000 -> milésimo(a) 2000 -> segundo(a) milésimo(a) 3000 -> terceiro(a) milésmio(a) 4000 -> quarto(a) milésimo(a) 5000 -> quinto(a) milésimo(a) Greater than ten thousand: 10.000 -> décimo(a) milésimo(a) 11.000 -> décimo(a) primeiro(a) milésimo(a) 22.222 -> vigésimo(a) segundo(a) milésimo(a) ducentésimo(a) vigésimo(a) segundo(a) Greater than one hundred thousand: 100.000 -> centésimo(a) milésimo(a) 111.000 -> centésimo(a) décimo(a) primeiro(a) milésimo(a) 222.222 -> ducentésimo(a) vigésimo(a) segundo(a) milésimo(a) ducentésimo(a) vigésimo(a) segundo(a) Greater than a million: 1.000.000 -> milionésimo(a) 2.000.000 -> segundo(a) milionésimo(a) 3.000.000 -> terceiro(a) milionésimo(a) 4.000.000 -> quarto(a) milionésimo(a) ... (Brazil) 1.000.000.000 -> bilionésimo(a) (Correct, but the next ones are not.) 2.000.000.000 -> segundo(a) bilionésimo(a) 2.001.100.001 -> segundo(a) bilionésimo(a) milionésimo(a) centésimo(a) milésimo(a) primeiro(a) 3.000.000.000 -> terceiro(a) bilionésimo(a) 4.000.000.000 -> quarto(a) bilionésimo(a) (the rest) 1.000.000.000 -> milésimo(a) milionésimo(a) 2.000.000.000 -> segundo(a) milésimo(a) milionésimo(a) 2.001.100.001 -> segundo(a) milésimo(a) primeiro(a) milionésimo(a) centésimo(a) milésimo(a) primeiro(a) 3.000.000.000 -> terceiro(a) milésimo(a) milionésimo(a) 4.000.000.000 -> quarto(a) milésimo(a) milionésimo(a) Reproducible: Always User Profile Reset: Yes Additional Info: - long and short scales: https://en.wikipedia.org/wiki/Long_and_short_scales - numbers in portuguese: https://en.wiktionary.org/wiki/Appendix:Portuguese_numbers https://european-portuguese.info/numbers - [NatNum12] : https://help.libreoffice.org/latest/en-US/text/shared/01/05020301.html -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160557] High display scaling results in squeezed tabbed interface and slightly smaller icons
https://bugs.documentfoundation.org/show_bug.cgi?id=160557 Rob changed: What|Removed |Added Version|unspecified |6.2.5.2 release -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160557] High display scaling results in squeezed tabbed interface and slightly smaller icons
https://bugs.documentfoundation.org/show_bug.cgi?id=160557 --- Comment #2 from Rob --- Created attachment 193533 --> https://bugs.documentfoundation.org/attachment.cgi?id=193533=edit Screenshot of Tabbed interface when display scaling is set to 100% -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160557] High display scaling results in squeezed tabbed interface and slightly smaller icons
https://bugs.documentfoundation.org/show_bug.cgi?id=160557 --- Comment #1 from Rob --- Created attachment 193532 --> https://bugs.documentfoundation.org/attachment.cgi?id=193532=edit Screenshot of bugged Tabbed interface when display scaling is set to 200% -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160557] New: High display scaling results in squeezed tabbed interface and slightly smaller icons
https://bugs.documentfoundation.org/show_bug.cgi?id=160557 Bug ID: 160557 Summary: High display scaling results in squeezed tabbed interface and slightly smaller icons Product: LibreOffice Version: unspecified Hardware: x86 (IA32) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: cobamern...@gmail.com Description: When the display scaling on Windows is set to anything greater than 125%, the tabbed interface appears too small, and squished to the side. Consequently, the icons are also slightly smaller than they should be, making them harder to press. The problem appears to have been occurring since at least LibreOffice 6.2.5.2, and I have not been able to verify whether the problem occurs on an earlier version. This scaling bug does not seem to affect the Standard Toolbar or its variants, and affects all LibreOffice Applications where the user interface can be set to "Tabbed" or its variants. This can be especially problematic on devices for which the default scaling is set to something greater than 125%. I'll also attach two screenshots below to illustrate the bug. Both screenshots were taken in LibreOffice Writer in full screen mode, but with different display scaling options. Steps to Reproduce: 1.Open Windows settings app 2.Click on System 3.Click on Display 4.Set scale to 200% (This is the default on my windows device) 5.Open LibreOffice Word, Calc, or Impress and set the user interface to "Tabbed" Actual Results: The tabs appear to be compressed and squished to the left, and the icons are slightly smaller than normal. Expected Results: The tabbed interface is normally more polished and uniform. Reproducible: Always User Profile Reset: Yes Additional Info: Device info: - Device: Surface Pro (2017) - OS: Windows 10 Pro - Display scaling: 200% LibreOffice info: - Version: 24.2.2.2 (X86_64) / LibreOffice Community - Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 C- PU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160556] New: Crash in: ntdll.dll
https://bugs.documentfoundation.org/show_bug.cgi?id=160556 Bug ID: 160556 Summary: Crash in: ntdll.dll Product: LibreOffice Version: 24.2.2.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: leo.m...@syonic.eu This bug was filed from the crash reporting server and is br-bdd7d520-f563-4695-94a0-5c8d84907fbf. = See the new comment for: https://bugs.documentfoundation.org/show_bug.cgi?id=160525 This new crash was with LibreOffice 24.2.2.2! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160525] Crash in: Edit::ImplSetText(rtl::OUString const &,Selection const *) when opening Bullets and Numbering dialog in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=160525
--- Comment #3 from Leonard ---
New Crash with version 24.2.2:
https://crashreport.libreoffice.org/stats/crash_details/bdd7d520-f563-4695-94a0-5c8d84907fbf
1. Opened my previous file
2. Right clicked word in bullet level 3 ("C."): worked fine;
3. Changed to level 4: OK;
4. Next slide: clicked on similar bullet with level 3 ("C");
5. Changed to level 5 ("E")
=> Crash
After restarting LibreOffice:
- changed to bullet level 4: NO crash;
- changed then to bullet level 5: still NO crash;
- but did not check if changing directly to level 5 will repeat the crash;
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 143148] Use pragma once instead of include guards (Episode 2: Endgame)
https://bugs.documentfoundation.org/show_bug.cgi?id=143148 --- Comment #133 from Commit Notification --- Heikki Ilvesmäki committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/2c724d88fef38a390744bbe1a4add031c6c62843 tdf#143148 use pragma once instead of include guards It will be available in 24.8.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.
[Bug 160555] Pasting text with default style attributes after differently styled text gives unexpected results
https://bugs.documentfoundation.org/show_bug.cgi?id=160555 Ulrich Windl changed: What|Removed |Added CC||u20230...@gmail.com Summary|Pasting text with default |Pasting text with default |style attributes after |style attributes after |differently styled text |differently styled text ||gives unexpected results -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160555] New: Pasting text with default style attributes after differently styled text
https://bugs.documentfoundation.org/show_bug.cgi?id=160555 Bug ID: 160555 Summary: Pasting text with default style attributes after differently styled text Product: LibreOffice Version: 7.6.6.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: u20230...@gmail.com Created attachment 193531 --> https://bugs.documentfoundation.org/attachment.cgi?id=193531=edit Sample document showing the effect I think this is a bug, because it results in poor usability, and it's counter-intuitive: Consider you have a text document with (default-styled text)(e.g. bold text) Now if you mark all text in the line and paste it at the end of the line, what happens? You do *not* get this: (default-styled text)(e.g. bold text)(default-styled text)(e.g. bold text) But instead you get: (default-styled text)(e.g. bold text)(bold text)(e.g. bold text) That is the style at the end of the line (at the cursor) is not "canceled" when inserting unstyled text, but the attributes are "continued". Usually when pasting text, the text is pasted *with* attributes (unless you use special paste), but that's not happening here, or at least not as expected. In contrast when you start with (e.g. bold text)(default-styled text) And repeat the experiment, you get (the expected) (e.g. bold text)(default-styled text)(e.g. bold text)(default-styled text) because the style at the cursor (end of line) is *not* "continued". See the sample document. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160528] spam
https://bugs.documentfoundation.org/show_bug.cgi?id=160528 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |INVALID Product|QA Tools|LibreOffice Component|General |deletionRequest Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160528] spam
https://bugs.documentfoundation.org/show_bug.cgi?id=160528 Stéphane Guillou (stragu) changed: What|Removed |Added Summary|Error in CSV export |spam |functionality | -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160510] When pasting text styled with character format to a new document that style isn't edit-able
https://bugs.documentfoundation.org/show_bug.cgi?id=160510
--- Comment #5 from Ulrich Windl ---
(In reply to Haris from comment #3)
I think you misunderstood, or I didn't explain well enough:
I don't want to assign a different "named" character style, but instead I want
to change the attributes of the currently assigned style ("Taste" in the
screenshot, I thought it was obvious).
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 85811] [META] Main menu bar bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=85811 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160391 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160391 [Bug 160391] Font color of the menu bar stays black when changing win10/11 from light to dark mode -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160391] Font color of the menu bar stays black when changing win10/11 from light to dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=160391 Stéphane Guillou (stragu) changed: What|Removed |Added Version|7.6.5.2 release |7.6.0.0 alpha0+ Blocks||85811 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=85811 [Bug 85811] [META] Main menu bar bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160554] New: Crashes when creating a new Writer document or opening an existing one.
https://bugs.documentfoundation.org/show_bug.cgi?id=160554 Bug ID: 160554 Summary: Crashes when creating a new Writer document or opening an existing one. Product: LibreOffice Version: 24.8.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: critical Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: miguelange...@libreoffice.org At creating a new writer on the start screen, or opening an existing one, LibreOffice crash after a few seconds, even with 'Tip of day' on the screen. >From scratch 2024-04-04 Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 7b9905df455b47977968a185a7c43f35541e018b CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded regression from (scratch) 2024-03-31 Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: c9d4f99b2bb54ac7735b3e0d0cadbafbd0279518 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160523] FILEOPEN Writer closes immediately after the odt document is Opened / Created in LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=160523 Stéphane Guillou (stragu) changed: What|Removed |Added Keywords||haveBacktrace -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160523] FILEOPEN Writer closes immediately after the odt document is Opened / Created in LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=160523 --- Comment #3 from Stéphane Guillou (stragu) --- Created attachment 193530 --> https://bugs.documentfoundation.org/attachment.cgi?id=193530=edit WinDbg backtrace Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 7b9905df455b47977968a185a7c43f35541e018b CPU threads: 4; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160511] "box around character" uses too much padding above (matter of taste)
https://bugs.documentfoundation.org/show_bug.cgi?id=160511 --- Comment #6 from Ulrich Windl --- Created attachment 193529 --> https://bugs.documentfoundation.org/attachment.cgi?id=193529=edit Screenshot showing boxes around text for some variants (In reply to m_a_riosv from comment #5) > Can't you solve it, by disable the synchronization on border's padding?, set > up them individually. When using *one* style for all it would depend on the actual characters being used. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160552] Strg+f replaced by ALT+F - WTF?!!!
https://bugs.documentfoundation.org/show_bug.cgi?id=160552 --- Comment #2 from Mike --- Well, exactly. STRG is German for CTRL. I never change stock shortcuts, since I'm working on differnent machines. That would make things difficult. All right, I'll check out safe mode next week when I'm back at the machine that has this strange behavior. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159690] Manual line break forces automatic Wrap Text
https://bugs.documentfoundation.org/show_bug.cgi?id=159690 --- Comment #24 from Francewhoa --- This is to confirm this challenge. Using Calc 24.2.2.2. Also confirming that we could not reproduce this challenge with Calc ≤ 7.6.4 Adding a manual line break, then press "Enter" key, forces a not needed automatic wrap text Both me and the Ubertus.Org team would be happy, as volunteer, to contribute testing new versions and writing documentation, if needed. Using the LO from https://flathub.org/apps/org.libreoffice.LibreOffice --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- Below is the same as above. But with detailed steps and screenshots if you're interested in those. --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- Steps to Reproduce: 1. Using Calc version 24.2.2.2, add text to a cell with a manual line break. For example, the cell "A1". Adding at least one manual break is important. As it triggers this challenge 100% of the time. Alternatively, use the attached already configured "Francewhoa---Test_File---Zombie_Auto_Wrap---V1.ods" file. 2. Using the "Format Cells" window, deactivate "Wrap text automatically" for cell "A1". This screenshot https://bugs.documentfoundation.org/attachment.cgi?id=193525 shows this config. 3. This screenshot https://bugs.documentfoundation.org/attachment.cgi?id=193526 shows that the cell "A1" presently does not have any wrap text. 4. Edit this cell content. For example, add or remove a letter in the text. Then press "Enter" key to validate your edit. 5. Somehow, Calc automatically forced reactivated the not needed "Wrap text automatically" configuration. In other words, a Zombie-Wrap (joke ;). The attached screenshots https://bugs.documentfoundation.org/attachment.cgi?id=193527 and https://bugs.documentfoundation.org/attachment.cgi?id=193528 show this challenge. --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- Narrowing Down: Below is what we found while testing. Which might be useful to resolve this challenge. • Using Calc 24.2.2.2, using this file https://bugs.documentfoundation.org/attachment.cgi?id=193524 Using the steps to reproduce above, at step 3, instead of pressing "Enter" key, press on "Escape" (Esc) key. Your edit is lost. But the Zombie-Wrap is not forced. This means that somehow, pressing "Enter" key triggers this challenge. • Using a version of Calc older than 24.2.2.2, I forgot to write down which one exactly, most likely the before last version or the second before last version. Using the steps to reproduce above, complete the first 3 steps only. Then left click on cell "A1" to select it. Then save the document. The Zombie-Wrap is forced. This means that somehow, when a selected cell includes a break line, when the user save the document, the Zombie-Wrap is triggered. This challenge is resolved with 24.2.2.2. But the other challenge above with the "Enter" key is not yet resolved. • Also using a version of Calc older than 24.2.2.2, again using the steps to reproduce above, complete the first 3 steps only. Then left click on cell "A4" to select it. In the attached file this cell is empty. Then save the document. The Zombie-Wrap is not forced. Again, this confirms that somehow, only when a selected cell includes a break line, when the user save the document, the Zombie-Wrap is triggered. Again, this challenge is resolved with 24.2.2.2. But the other challenge above with the "Enter" key is not yet resolved. --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- Using: • LibreOffice 24.2.2.2 from https://flathub.org/apps/org.libreoffice.LibreOffice • Debian 12 Bookworm 64 bits • GNOME 43.9 • Wayland -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160512] CRASH Writer Hangs completely when copying complete file, even small file
https://bugs.documentfoundation.org/show_bug.cgi?id=160512 m_a_riosv changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160491] In Calc "text to columns" produces two rows out of one row of data
https://bugs.documentfoundation.org/show_bug.cgi?id=160491 m_a_riosv changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160458] Char unveiled in Calc and Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=160458 --- Comment #4 from m_a_riosv --- You can use Menu/Insert/Special character Also introducing the hexadecimal code plus [Alt+X] 2713+[Alt+X] https://help.libreoffice.org/24.8/en-US/text/shared/01/0410.html?=CALC=WIN https://help.libreoffice.org/24.8/en-US/text/shared/04/0101.html?=CALC=WIN#unicode_shortcut -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155012] Same Help page used for Sign Document and Encrypt Document dialogs
https://bugs.documentfoundation.org/show_bug.cgi?id=155012 Dione Maddern changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |dionemadd...@gmail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155012] Same Help page used for Sign Document and Encrypt Document dialogs
https://bugs.documentfoundation.org/show_bug.cgi?id=155012 --- Comment #4 from Dione Maddern --- Ah. I see. Thanks. I think I should be able to get a separate page set up. Looks like the page could do with a little updating too. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 35694] "Page number" automatic field stops counting before last page if offset >0 (see comment 22)
https://bugs.documentfoundation.org/show_bug.cgi?id=35694
--- Comment #83 from Eyal Rozenberg ---
(In reply to Heiko Tietze from comment #82)
> Comment 70 and 78 are wisdom, and a good proposal is missing too.
But comment 70 _is_ a proposal: Using a formula which can utilize a page-number
variable. What's wrong with that?
> On the other hand, compatibility is prime and neither prev/next page nor
> any offset are stored with docx.
Why is this "on the other hand"? Do these two statements disagree? It seems
like it's "on the same hand"...
> MS Word allows an offsets per field code like
> "{={PAGE}-10} of {={NUMPAGES}*20}" showing as "-9 of 80". But it wont be
> stored as a field when saving as ODT.
Comment 70 states that Writer supports inserting such formula fields generally.
Taking Mike's word for it (as I can't find this myself) - why won't such
MS-Word fields be stored as field when saving as ODT? Is there a known reason?
> In the end we do not have the expertise to decide on the matter. The
> functionality is unclear, the need to describe an offset in the way ODF does
> not what exactly user expect (beyond a negative offset for cover pages) is
> easy to follow.
It's easy to follow and reach an understanding that it doesn't belong in the
Page Number dialog - and it's the UI expertise which was necessary. It also
looks like the discussion in the design meeting was not really concerned with
the UI aspects of the problem, which I and others have emphasized.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 159690] Manual line break forces automatic Wrap Text
https://bugs.documentfoundation.org/show_bug.cgi?id=159690 --- Comment #23 from Francewhoa --- Created attachment 193528 --> https://bugs.documentfoundation.org/attachment.cgi?id=193528=edit Francewhoa---Screenshot---4---Forced_zombie_wrap---V1.png -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159690] Manual line break forces automatic Wrap Text
https://bugs.documentfoundation.org/show_bug.cgi?id=159690 --- Comment #22 from Francewhoa --- Created attachment 193527 --> https://bugs.documentfoundation.org/attachment.cgi?id=193527=edit Francewhoa---Screenshot---3---1st_line_with_zombie_wrap---V1.png -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159690] Manual line break forces automatic Wrap Text
https://bugs.documentfoundation.org/show_bug.cgi?id=159690 --- Comment #21 from Francewhoa --- Created attachment 193526 --> https://bugs.documentfoundation.org/attachment.cgi?id=193526=edit Francewhoa---Screenshot---2---1st_line_without_wrap---V1.png -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159690] Manual line break forces automatic Wrap Text
https://bugs.documentfoundation.org/show_bug.cgi?id=159690 --- Comment #20 from Francewhoa --- Created attachment 193525 --> https://bugs.documentfoundation.org/attachment.cgi?id=193525=edit Francewhoa---Screenshot---1---Deactivated_wrap---V1.png -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159690] Manual line break forces automatic Wrap Text
https://bugs.documentfoundation.org/show_bug.cgi?id=159690 Francewhoa changed: What|Removed |Added CC||compost.idu_20231226_051738 ||@en.francewhoa.ca --- Comment #19 from Francewhoa --- Created attachment 193524 --> https://bugs.documentfoundation.org/attachment.cgi?id=193524=edit Francewhoa---Test_File---Zombie_Auto_Wrap---V1.ods Starting with this comment, I'm adding a few files Then I'll add a comment to confirm this challenge with recently released 24.2.2.2. Including both our steps to reproduce and some new information that might be useful to resolve this challenge. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160512] CRASH Writer Hangs completely when copying complete file, even small file
https://bugs.documentfoundation.org/show_bug.cgi?id=160512 --- Comment #10 from Peter Zwitser --- I really don't know what happened, but it looks like it is solved. Just for information I'll tell what I did (or actually: not did...) 1) removed libreOffice completely. 2) removed the PPA with libreOffice. 3) installed the default version from Neod. That's version 7 and something. 4) The problem still existed. So it started to look it had nothing to do with the latest update from LibreOffice. I noticed the problem the same day LibreOffice was updated, so I thought it had to do with that update. Maybe it was something in my system that was recently changed? That would also explain why it's hard to reproduce the bug for other people. 5) Logged out and logged in again, but this time not with X11 but with Wayland. Problem was gone. Ah, so it probably has something to do with the combination LibreOffice/X11. But Wayland has (for the moment) a lot of other problems, so I'd really prefer for the moment X11. 6) Logged out and logged in again, but now again with X11. I was planning to start reading about settings from X11. But to my big surprise the problem is gone. I copied all kind of texts about a hundred times, because I couldn't believe it, but it's really gone. Even restarted the system to be sure. I didn't change anything at all, except changing from X11 to Wayland and back. Sorry for the time you have spent, but since this happened just after the update from LibreOffice I really thought it had something to do with that update. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160514] Usability of accessibility check (Alt+7)
https://bugs.documentfoundation.org/show_bug.cgi?id=160514 Ulrich Windl changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160514] Usability of accessibility check (Alt+7)
https://bugs.documentfoundation.org/show_bug.cgi?id=160514 --- Comment #3 from Ulrich Windl --- Created attachment 193523 --> https://bugs.documentfoundation.org/attachment.cgi?id=193523=edit Test Document with accessibility issues reported For this test document only right-clicking on the links works; left-clicking does nothing. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160513] Table guides and margin formatting aids not visible after upgrade from 7.5.9 to 7.6.6
https://bugs.documentfoundation.org/show_bug.cgi?id=160513 Ulrich Windl changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #8 from Ulrich Windl --- (In reply to Stéphane Guillou (stragu) from comment #6) > Can you consider using a fresh profile? And possibly, when customising > again, you might find out which setting makes the issue reappear. My personal opinion: The difference between professional software and the rest is that you can upgrade professional software without having to re-install. Software you'll have to re-install frequently isn't worth using it. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160513] Table guides and margin formatting aids not visible after upgrade from 7.5.9 to 7.6.6
https://bugs.documentfoundation.org/show_bug.cgi?id=160513 --- Comment #7 from Ulrich Windl --- Created attachment 193522 --> https://bugs.documentfoundation.org/attachment.cgi?id=193522=edit Screenshot showing options Eventually I found the problem (see screenshot): The "Schema" for user-defined colors was blank; when I opened the pull-down list, there was only one choice available: "Automatic" As soon as I had selected that, the missing lines re-appeared. Of course such incompatibility is undesirable, and programmers should try to find out what went wrong. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 152438] Color popovers cutoff, overflow out of display (GTK, Wayland)
https://bugs.documentfoundation.org/show_bug.cgi?id=152438 --- Comment #10 from Caolán McNamara --- I think a new bug, but put me on cc. In the popovers inside the main window we seem to be able to get away with this "constraining" the popovers inside the main window and then we can be fairly sure we have enough main window for the popover to fit inside. But for dialogs that isn't always the case, I know there are dialogs smaller than the popover so we can't constrain them inside dialogs in the general case. We have to allow them to escape the surrounding dialog. And in the general wayland case we don't know where the dialog is on the screen to know which direction to position the popover. Assuming I'm guessing right about the remaining problem (include screenshot to be sure because for me the dialog appears in the center of the screen and I have lots of space in which to see the popover) I think the algorithm/hack that I saw used elsewhere was to default popovers to pop downwards if they are in the top half of the dialog, and pop upwards if they are in the bottom half. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160552] Strg+f replaced by ALT+F - WTF?!!!
https://bugs.documentfoundation.org/show_bug.cgi?id=160552 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m_a_riosv --- Please what is STRG key?, I guess is [Ctrl] Have you tested in Menu/Tools/Customize/Keyboard, how the combination is configured? Please test in safe mode, Menu/Help/Restart in Safe Mode Please paste here the information on Menu/Help/About LibreOffice (There is an icon to copy) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160550] Can't enable OpenCL even though it's supported by the hardware
https://bugs.documentfoundation.org/show_bug.cgi?id=160550 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #3 from m_a_riosv --- Please attach the file: 'opencl_devices.log' that you can find in the profile C:\Users\USER\AppData\Roaming\LibreOffice\4\cache -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160546] crash unknown trigger causing data loss
https://bugs.documentfoundation.org/show_bug.cgi?id=160546 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m_a_riosv --- Please attach a sample file, reduce the size as much as possible without private information, and paste the information in Menu/Help/About LibreOffice, there is a copy icon. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 141047] FORMATTING: Calc render 11pt font as 10,5pt when cell contains NBSP at 90% zoom
https://bugs.documentfoundation.org/show_bug.cgi?id=141047 ady changed: What|Removed |Added Summary|FORMATTING: Calc render 11 |FORMATTING: Calc render |pt Calibri font as 10,5 pt |11pt font as 10,5pt when |when cell contains NBSP at |cell contains NBSP at 90% |90% zoom|zoom -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160545] LO Writer not saving hyperlink in docx file
https://bugs.documentfoundation.org/show_bug.cgi?id=160545 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m_a_riosv --- Please attach a sample file, reduce the size as much as possible without private information, and paste the information in Menu/Help/About LibreOffice, there is a copy icon. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 141047] FORMATTING: Calc render 11 pt Calibri font as 10,5 pt when cell contains NBSP at 90% zoom
https://bugs.documentfoundation.org/show_bug.cgi?id=141047 --- Comment #16 from ady --- (In reply to Buovjaga from comment #15) > Then let's treat this as a regression. IDK about that; it might or might not be a regression. In LO 3.3.0.4, there is also a horizontal difference, but: * the specific zoom factors that show the difference might not be the same as in a recent 24.8 alpha, * the horizontal difference might be "inverted". Using the example from comment 14 and with a zoom factor that shows some difference in the horizontal length, cell A1 might be shown "longer" than A2 in LO 3.3.0.4, but in a recent 24.8 alpha cell A1 is shown "shorter" than A2. So, perhaps the difference in LO 3.3.0.4 is caused by something else; or maybe the basic reason is the same with some "minor" change in some commit. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160553] FILEOPEN RTF Section break between tables is not imported
https://bugs.documentfoundation.org/show_bug.cgi?id=160553 --- Comment #1 from Gabor Kelemen (allotropia) --- Created attachment 193521 --> https://bugs.documentfoundation.org/attachment.cgi?id=193521=edit The example file in Word 2016 and Writer -- You are receiving this mail because: You are the assignee for the bug.
[Bug 81234] [META] RTF filter issues
https://bugs.documentfoundation.org/show_bug.cgi?id=81234 Gabor Kelemen (allotropia) changed: What|Removed |Added Depends on||160553 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160553 [Bug 160553] FILEOPEN RTF Section break between tables is not imported -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160553] New: FILEOPEN RTF Section break between tables is not imported
https://bugs.documentfoundation.org/show_bug.cgi?id=160553 Bug ID: 160553 Summary: FILEOPEN RTF Section break between tables is not imported Product: LibreOffice Version: 3.5.0 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kelem...@ubuntu.com Blocks: 81234 Created attachment 193520 --> https://bugs.documentfoundation.org/attachment.cgi?id=193520=edit Example file Attached example file contains two tables with a section break. This is not imported in Writer, so the document is 1 pages instead of two in Word. 1. Open attached document -> 1 page instead of 2 Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: c9d4f99b2bb54ac7735b3e0d0cadbafbd0279518 CPU threads: 15; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: default started in 3.5, but it was good in 3.3 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=81234 [Bug 81234] [META] RTF filter issues -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160350] Replies to comment are in reverse order
https://bugs.documentfoundation.org/show_bug.cgi?id=160350 --- Comment #12 from Cor Nouws --- May I please ask @timur and @bogdanb to look at attachment 193483? There replies are shown below the comment on which they are done. What do you think of that situation? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160544] Quickfind sidebar: Make the sidebar the default for ctrl+F
https://bugs.documentfoundation.org/show_bug.cgi?id=160544 Cor Nouws changed: What|Removed |Added CC||c...@nouenoff.nl --- Comment #4 from Cor Nouws --- The quickfind works as follows: - Ctrl+F ESC => all as before. Will that also be the case with Find in de sidebar? Will ESC bring the sidebar to the state of before hitting Ctrl+F? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160552] New: Strg+f replaced by ALT+F - WTF?!!!
https://bugs.documentfoundation.org/show_bug.cgi?id=160552 Bug ID: 160552 Summary: Strg+f replaced by ALT+F - WTF?!!! Product: LibreOffice Version: 24.2.2.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: cys...@gmail.com Description: I'm using LibreOffice since many years and I've been a happy user - until I noticed a strange behavior on Windows 11 running the newest release these days. Strg+F didn't work. Any strange windows popped up... Look slike there is a stupid bug replacing the well known Strg+F with Alt+F - for no reason. Steps to Reproduce: 1.press STRG+F If any strange popup appears, you got the bug. I've tested this on two machines, both running the latest release. One works fine, one is using ALT+F instead. Really strange behavior... Actual Results: On one machine: open search - like it should be. another machine: open any strange popup I've never seen before... Expected Results: open search. Reproducible: Always User Profile Reset: No Additional Info: open search field -- You are receiving this mail because: You are the assignee for the bug.
[Bug 123972] UI menu disappears before submenu can open (GTK3 and Wayland)
https://bugs.documentfoundation.org/show_bug.cgi?id=123972 --- Comment #29 from lanaray --- For Bug 123972, which concerns the disappearance of the UI menu before the submenu can open on GTK3 and Wayland, the issue likely stems from a compatibility issue between GTK3 and the Wayland display server protocol. It seems that the menu system may be encountering a timing or rendering problem that causes it to vanish prematurely. To address this, developers may need to investigate and possibly modify the code related to menu rendering and interaction, ensuring proper synchronization between the UI elements and the Wayland display server. Additionally, testing across different environments and configurations could help pinpoint the root cause and facilitate the implementation of an effective solution. For further insights into photo editing apps that might offer alternative solutions or workarounds, you can explore our curated list of https://getreminiproapk.com/top-10-photo-editing-apps-for-ios-and-android//] -- You are receiving this mail because: You are the assignee for the bug.
[Bug 101522] [META] Media playback bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101522 --- Comment #23 from lanaray --- This insightful information is truly valuable for everyone seeking to broaden their knowledge horizons. It's incredibly enriching to receive such detailed insights, and I eagerly anticipate learning more along these lines.https://getreminiproapk.com/ai-in-photography/ -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160523] FILEOPEN Writer closes immediately after the odt document is Opened / Created in LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=160523 --- Comment #2 from stefan_lange...@t-online.de --- I have made additional tests with the pollux builds from LOdev 24.8: The bug was not reproduced with Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 6027c219444ade7274841a5ba45e62bdc1ea3238 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: CL threaded (from /daily/master/Win-x86_64@tb78-pollux-TDF/2024-04-02_06.16.52/) but with Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 5ebe81f068dba0c141ebe92f64731d0c95179dae CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: CL threaded (from /daily/master/Win-x86_64@tb78-pollux-TDF/2024-04-04_06.00.15/) Therefore the range to find the cange causing the bug reduces to between 6027c219444ade7274841a5ba45e62bdc1ea3238 and b0edb1909b9deb1a170497f935a528f8118c8308. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160551] Lossless export to .webm causes Hang
https://bugs.documentfoundation.org/show_bug.cgi?id=160551 Rainer Bielefeld Retired changed: What|Removed |Added CC||LibreOffice@bielefeldundbus ||s.de --- Comment #1 from Rainer Bielefeld Retired --- Ooops, sorry! "7. Open PNG in IrfanVIEW" is a Copy Paste Artefact, should not have been there! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160551] New: Lossless export to .webm causes Hang
https://bugs.documentfoundation.org/show_bug.cgi?id=160551 Bug ID: 160551 Summary: Lossless export to .webm causes Hang Product: LibreOffice Version: 24.8.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: libreoff...@bielefeldundbuss.de Steps how to reproduce with Installation of Version: 7.6.4.1 (X86_64) Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: Locale: de-DE (de_DE); UI: de-DE; Theme: Automatic (Colibre) Calc: CL threaded – Normal User Profile PC: AMD Ryzen 5 3600 6-Core Processor 3.60 GHz, 16,0 GB RAM 0. Download and unzip TestKit from "Bug 160485 - FILESAVE: Some Cells Text missing in EXPORT.png with highresolution." 1. Open SampldDocument.ods 2. Click cell CX3 and with select range CX3 - A1 3. Release Mouse Button » Area keeps highlighted / selected 4. Menu ˋFile → Export → Format = WEBP → (Keep Auto-Filename-Extension and "Selection" checked → Exportˊ » Export Dialog appears 5. ˋRadio button "Modify Dimensions" → in Width add a "00" (2 times zero) left from comma → for reaching Height fieldˊ » Height value also becomes more or less ten times as much, similar to width. 6. ˋCheck "Lossless" if not already done → [ok]ˊ » Expected: WEBP should be be created 7. Open PNG in IrfanVIEW Actual: Endless exporting. After 50 minutes still not done . I terminated LibO. Additional info: - a) before this test I tried with several files open; LibO crashed. b) I was not able to close the source calc document via WIN Task Manger Which successfully r Task list, but document kept open) or in any other way, had to reboot the PC -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160543] Quickfind sidebar: Search depends on F settings
https://bugs.documentfoundation.org/show_bug.cgi?id=160543 --- Comment #2 from V Stuart Foote --- =-testing-= TB78 - 20240405 Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 30c6e51fc9cb0fa864e1755271343d847fcced25 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160543] Quickfind sidebar: Search depends on F settings
https://bugs.documentfoundation.org/show_bug.cgi?id=160543 --- Comment #1 from V Stuart Foote --- QFS should have *no* dependency on the Find & Replace dialog, rather should come from config for the Findbar. Also, note there is a results "Search key found xx times" showing in the Find bar--that detail really belongs in the SB QFS content panel, not requiring the Find bar to be shown. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160542] Quickfind sidebar: Search term is not easy to spot
https://bugs.documentfoundation.org/show_bug.cgi?id=160542 --- Comment #1 from V Stuart Foote --- Yes, I've no issue with the applied bracket in the result "node" especially as focus on the node in SB repositions to and flashes its spot on document canvas. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160541] Quickfind sidebar: present results with some indication of location in document
https://bugs.documentfoundation.org/show_bug.cgi?id=160541 V Stuart Foote changed: What|Removed |Added Summary|Quickfind sidebar: Indicate |Quickfind sidebar: present |page breaks |results with some ||indication of location in ||document -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160540] Quickfind sidebar: find results all show as equal sized
https://bugs.documentfoundation.org/show_bug.cgi?id=160540 V Stuart Foote changed: What|Removed |Added Summary|Quickfind sidebar: Nodes|Quickfind sidebar: find |are equal sized |results all show as equal ||sized -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160538] Quickfind sidebar: ordering of results, Text in fields and frames comes first
https://bugs.documentfoundation.org/show_bug.cgi?id=160538 V Stuart Foote changed: What|Removed |Added Summary|Quickfind sidebar: Text in |Quickfind sidebar: ordering |fields and frames comes |of results, Text in fields |first |and frames comes first -- You are receiving this mail because: You are the assignee for the bug.
[Bug 102847] [META] Quick Find, Search and Replace
https://bugs.documentfoundation.org/show_bug.cgi?id=102847 V Stuart Foote changed: What|Removed |Added Depends on|160544 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160544 [Bug 160544] Quickfind sidebar: Make the sidebar the default for ctrl+F -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160544] Quickfind sidebar: Make the sidebar the default for ctrl+F
https://bugs.documentfoundation.org/show_bug.cgi?id=160544 V Stuart Foote changed: What|Removed |Added Blocks|102847 |95405 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=95405 [Bug 95405] Sidebar deck for find/search and replace https://bugs.documentfoundation.org/show_bug.cgi?id=102847 [Bug 102847] [META] Quick Find, Search and Replace -- You are receiving this mail because: You are the assignee for the bug.
[Bug 102847] [META] Quick Find, Search and Replace
https://bugs.documentfoundation.org/show_bug.cgi?id=102847 V Stuart Foote changed: What|Removed |Added Depends on|160543 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160543 [Bug 160543] Quickfind sidebar: Search depends on F settings -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160543] Quickfind sidebar: Search depends on F settings
https://bugs.documentfoundation.org/show_bug.cgi?id=160543 V Stuart Foote changed: What|Removed |Added Blocks|102847 |95405 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=95405 [Bug 95405] Sidebar deck for find/search and replace https://bugs.documentfoundation.org/show_bug.cgi?id=102847 [Bug 102847] [META] Quick Find, Search and Replace -- You are receiving this mail because: You are the assignee for the bug.
[Bug 102847] [META] Quick Find, Search and Replace
https://bugs.documentfoundation.org/show_bug.cgi?id=102847 V Stuart Foote changed: What|Removed |Added Depends on|160542 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160542 [Bug 160542] Quickfind sidebar: Search term is not easy to spot -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160542] Quickfind sidebar: Search term is not easy to spot
https://bugs.documentfoundation.org/show_bug.cgi?id=160542 V Stuart Foote changed: What|Removed |Added Blocks|102847 |95405 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=95405 [Bug 95405] Sidebar deck for find/search and replace https://bugs.documentfoundation.org/show_bug.cgi?id=102847 [Bug 102847] [META] Quick Find, Search and Replace -- You are receiving this mail because: You are the assignee for the bug.
[Bug 102847] [META] Quick Find, Search and Replace
https://bugs.documentfoundation.org/show_bug.cgi?id=102847 V Stuart Foote changed: What|Removed |Added Depends on|160541 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160541 [Bug 160541] Quickfind sidebar: Indicate page breaks -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160541] Quickfind sidebar: Indicate page breaks
https://bugs.documentfoundation.org/show_bug.cgi?id=160541 V Stuart Foote changed: What|Removed |Added Blocks|102847 |95405 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=95405 [Bug 95405] Sidebar deck for find/search and replace https://bugs.documentfoundation.org/show_bug.cgi?id=102847 [Bug 102847] [META] Quick Find, Search and Replace -- You are receiving this mail because: You are the assignee for the bug.
[Bug 102847] [META] Quick Find, Search and Replace
https://bugs.documentfoundation.org/show_bug.cgi?id=102847 V Stuart Foote changed: What|Removed |Added Depends on|160540 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160540 [Bug 160540] Quickfind sidebar: Nodes are equal sized -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160540] Quickfind sidebar: Nodes are equal sized
https://bugs.documentfoundation.org/show_bug.cgi?id=160540 V Stuart Foote changed: What|Removed |Added Blocks|102847 |95405 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=95405 [Bug 95405] Sidebar deck for find/search and replace https://bugs.documentfoundation.org/show_bug.cgi?id=102847 [Bug 102847] [META] Quick Find, Search and Replace -- You are receiving this mail because: You are the assignee for the bug.
[Bug 102847] [META] Quick Find, Search and Replace
https://bugs.documentfoundation.org/show_bug.cgi?id=102847 V Stuart Foote changed: What|Removed |Added Depends on|160539 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160539 [Bug 160539] Quickfind sidebar: Words are cut-off at beginning and end -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160539] Quickfind sidebar: Words are cut-off at beginning and end
https://bugs.documentfoundation.org/show_bug.cgi?id=160539 V Stuart Foote changed: What|Removed |Added Blocks|102847 |95405 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=95405 [Bug 95405] Sidebar deck for find/search and replace https://bugs.documentfoundation.org/show_bug.cgi?id=102847 [Bug 102847] [META] Quick Find, Search and Replace -- You are receiving this mail because: You are the assignee for the bug.
