[Bug 160011] Hidden columns should not prevent text from preceding columns from overflowing over their cells
https://bugs.documentfoundation.org/show_bug.cgi?id=160011 Cor Nouws changed: What|Removed |Added CC||c...@nouenoff.nl --- Comment #15 from Cor Nouws --- Hi Miguel, (In reply to m_a_riosv from comment #11) > I think the main issue about changing the behavior is the modification of > the display for existing documents, without any warning to the user. Personally I would not mind if the behavior changes from A CD ###|| | || | to A CD applepie| | || | Honestly I think I would have avoided such a situation to exist. If we have no indication of serious problems, I would suggest changing is useful. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160230] MRU Recent files list entries numbered, no need to be
https://bugs.documentfoundation.org/show_bug.cgi?id=160230 --- Comment #6 from Eyal Rozenberg --- > Those numbers have no significance, no actual meaning. Isn't it the order of recency? That could help the user remember which document is which. (In reply to V Stuart Foote from comment #4) > But only working for documents 1 - 9. That's good enough. The 10th most recent document? Not super interesting. Anyway, I say keep this. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 157591] context menu: "add to dictionary" -- no need to deselect word before
https://bugs.documentfoundation.org/show_bug.cgi?id=157591 --- Comment #5 from Shantanu --- >> Or maybe we combine context menu #1 and #2 >> specifically for misspelled words so that the user can correct >> misspelled words, add to dictionary, stylize words, etc. >> regardless of whether or not the misspelled word is selected/deselected Yes. That is what being asked. It looks like a reasonable feature request. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 157591] context menu: "add to dictionary" -- no need to deselect word before
https://bugs.documentfoundation.org/show_bug.cgi?id=157591 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||103341 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103341 [Bug 103341] [META] AutoCorrect and Word Completion bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 157591] context menu: "add to dictionary" -- no need to deselect word before
https://bugs.documentfoundation.org/show_bug.cgi?id=157591 Kira Tubo changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Keywords||needsUXEval Version|unspecified |Inherited From OOo CC||libreoffice-ux-advise@lists ||.freedesktop.org --- Comment #4 from Kira Tubo --- @peter josvai, thanks for clarifying! This makes much more sense now. But I wonder if this is by design. Because the way I see it: 1. Context menu of the unselected misspelled word gives the user the option to spell check/add to dictionary. 2. Context menu of selected misspelled word gives the user the option to stylize the word (rather than correcting/add to dictionary). If we were to replace context menu from #2 with #1, the user will no longer be able to stylize a misspelled word from a context menu. If we were to add only 'Add to dictionary' to context menu of #2, I don't know if it would be right to just add this category without giving the user the option to also correct misspelled words. Or maybe we combine context menu #1 and #2 specifically for misspelled words so that the user can correct misspelled words, add to dictionary, stylize words, etc. regardless of whether or not the misspelled word is selected/deselected. Adding UX team to advise. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160282] Ranges references text colors for in-cell editing of formulas are too dark for dark mode, causing low contrast
https://bugs.documentfoundation.org/show_bug.cgi?id=160282 --- Comment #2 from Jeff Fortin Tam --- I would not recommend* making those colors configurable. I believe they should simply have light vs dark variants "designed to work". This advice of mine would also apply to the "see also" issues above, and to bug #160160, bug #160159, bug #158032, etc. *: …for the reasons presented here: https://youtube.com/watch?v=rRvmS0mABC0 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160282] Ranges references text colors for in-cell editing of formulas are too dark for dark mode, causing low contrast
https://bugs.documentfoundation.org/show_bug.cgi?id=160282 Rafael Lima changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org --- Comment #1 from Rafael Lima --- >From all I know, these colors are hardcoded in: /core/sc/source/ui/app/rfindlst.cxx Maybe they should be configurable? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 148184] FORMATTING create a means to represent an integer as an IP Address
https://bugs.documentfoundation.org/show_bug.cgi?id=148184 --- Comment #3 from Eyal Rozenberg --- I believe the best thing to implement would be OP's alternative suggestion: > Alternatively, a means to create a personalized format representation with a > module function would be also be a way to enhance the personalized format > feature. That really scratches the itch IMHO. As for the main ask here - I weakly-support it, because: 1. IP addresses, while not a very common use cases, are not a tiny niche; and tables of data involving IP addresses are often the result of event logging on the Internet. 2. We already support a variety of number formatting types, in several categories, and do not lack anything in the UI for enabling this support. 3. "Third-party" support requires either keeping every element of the IP in a separate column (which many not even be possible with IPv6), or doing a lot of string processing. Both are cumbersome to work with and I'm worried about performance when using them. 4. Either MS Excel has it, in which case - competitor parity; or it doesn't have it, in which case: one-upping the competition :-) I realize that someone might argue "oh, but shall we now add another number format option for any number of niche formats?" - and the answer to that is, that AFAICT, there are extremely few, if any, other such requests, and I doubt the adoption of IP formatting will change this. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160011] Hidden columns should not prevent text from preceding columns from overflowing over their cells
https://bugs.documentfoundation.org/show_bug.cgi?id=160011 --- Comment #14 from Eyal Rozenberg --- Created attachment 193204 --> https://bugs.documentfoundation.org/attachment.cgi?id=193204=edit Calc document exhibiting the bug - column B is hidden This document is the result of following the reproduction instructions in the opening comment. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160011] Hidden columns should not prevent text from preceding columns from overflowing over their cells
https://bugs.documentfoundation.org/show_bug.cgi?id=160011 --- Comment #13 from Eyal Rozenberg --- I support the request change as per the bug title, because: 1. Hidden should mean hidden, i.e. the sheet presents as though the column did not exist. Otherwise it's effectively width-0. 2. Like Heiko mentioned in comment #6, MSO parity I am not worried about breakage, for two reasons: 1. Whoever uses hidden columns must expect users to sometimes unhide the columns, and plan for how their sheet will display when that happens. 2. Whoever uses hidden columns should expect the file to also work in MS Excel, where the behavior is different. 3. One can achieve the width-0 before with a literal width-0, non-hidden, column, so the breakage can be rectified relatively easily. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160241] Scrollbar ignores accessibility setting on Windows
https://bugs.documentfoundation.org/show_bug.cgi?id=160241 Heiko Tietze changed: What|Removed |Added CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org, ||mikekagan...@hotmail.com, ||m.wegh...@posteo.de Keywords|needsUXEval | Ever confirmed|0 |1 Blocks||101912, 105957 Summary|Scrollbar arrows not always |Scrollbar ignores |visible despite Windows |accessibility setting on |settings|Windows Status|UNCONFIRMED |NEW Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=101912 [Bug 101912] [META] Accessibility (a11y) bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=105957 [Bug 105957] [META] Scrollbar-related bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160241] Scrollbar arrows not always visible despite Windows settings
https://bugs.documentfoundation.org/show_bug.cgi?id=160241 --- Comment #2 from Heiko Tietze --- Created attachment 193190 --> https://bugs.documentfoundation.org/attachment.cgi?id=193190=edit Screenshot Confirming that we do not respect the "Always show scrollbar" setting. But even with this option, W11 wont show the scrollbar buttons aka arrows. And I disagree with CSS-like styling of one UI element, ie. either we allow to change the design of every control or none. Let's handle in this ticket the fact that we do not obey the a11y setting from Windows. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160255] Named Ranges Should Be Able to be Used in Conditional Formatting Dialog Box
https://bugs.documentfoundation.org/show_bug.cgi?id=160255 --- Comment #3 from BillMal --- You are welcome. Thank you both for your comments and also the Chart equivalent bug link. Given that premise, to be complete, I would expect Calc to recognize an underlying geometry change of a named range and reflect that within any utilized range pickers: Chart, Conditional Formatting, etc. Otherwise, one would necessitate manually changing the range everywhere it is referenced, outside of formulas where named ranges work fine in my experience. Appreciate the support. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160241] Scrollbar arrows not always visible despite Windows settings
https://bugs.documentfoundation.org/show_bug.cgi?id=160241 V Stuart Foote changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vsfo...@libreoffice.org Keywords||accessibility, needsUXEval Component|LibreOffice |UI Severity|normal |enhancement --- Comment #1 from V Stuart Foote --- Assistive Technology tool support of decorating the VCL scrollbars by browser extension in this case is really only applicable to Win11 users. By extension or licensing, incurs a support tail if reimplemented by community. No issues with Win10, so lets get bug 151238 Win11 WDM scrollbar arrow visibility issue resolved, and go from there. Otherwise for general use customization/decoration of the scrollbars seems suited to extension, not core AT support. IHMO => WF for this enhancement request. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160255] Named Ranges Should Be Able to be Used in Conditional Formatting Dialog Box
https://bugs.documentfoundation.org/show_bug.cgi?id=160255 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=66 ||250 URL||https://ask.libreoffice.org ||/t/calc-how-to-apply-condit ||ional-formatting-color-scal ||e-or-data-bar-to-a-named-ra ||nge-or-expression/60688 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160255] Named Ranges Should Be Able to be Used in Conditional Formatting Dialog Box
https://bugs.documentfoundation.org/show_bug.cgi?id=160255 Stéphane Guillou (stragu) changed: What|Removed |Added CC||er...@redhat.com, ||libreoffice-ux-advise@lists ||.freedesktop.org, ||stephane.guillou@libreoffic ||e.org --- Comment #2 from Stéphane Guillou (stragu) --- Thanks for the suggestion. I guess this is an issue that applies to various features that make sure of a range picker; e.g. see bug 66250 for the Chart equivalent of this request. Eike, is there any reason why this shouldn't work? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160227] Add timer/clock to single-screen presentation
https://bugs.documentfoundation.org/show_bug.cgi?id=160227 --- Comment #2 from Heiko Tietze --- Strikes me rather as a 3rd party extension. Remember that we use application and platform agnostic file format including the export to html and svg. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160230] MRU Recent files list entries numbered, no need to be
https://bugs.documentfoundation.org/show_bug.cgi?id=160230 --- Comment #5 from Heiko Tietze --- (In reply to V Stuart Foote from comment #4) > I guess either fix that to reach the full MRU listing, or strip out the > numbering. Or keep as it is. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 122834] STATUSBAR: Improve visibility of statusbar in small windows
https://bugs.documentfoundation.org/show_bug.cgi?id=122834 --- Comment #11 from Heiko Tietze --- Statusbar panels have a mandatory flag which keeps the panel visible on resize. Both, language and overwrite mode are set to false [1] and disappear but I guess from left to right. Reason for the report is probably the attempt to keep zoom visible as requested in bug 86612 by making many other panels non-mandatory. A possible band-aid is to swap language and overwrite mode. But ultimately the solution is bug 113828 - user customization. [1] https://opengrok.libreoffice.org/xref/core/sw/uiconfig/swriter/statusbar/statusbar.xml?r=62a0eb0a -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 122834] STATUSBAR: Improve visibility of statusbar in small windows
https://bugs.documentfoundation.org/show_bug.cgi?id=122834 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=62 ||678 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 122834] STATUSBAR: Improve visibility of statusbar in small windows
https://bugs.documentfoundation.org/show_bug.cgi?id=122834 --- Comment #10 from Stéphane Guillou (stragu) --- Created attachment 193172 --> https://bugs.documentfoundation.org/attachment.cgi?id=193172=edit screenshot of status bar when Language section just disappeared -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 122834] STATUSBAR: Improve visibility of statusbar in small windows
https://bugs.documentfoundation.org/show_bug.cgi?id=122834 Stéphane Guillou (stragu) changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||stephane.guillou@libreoffic ||e.org --- Comment #9 from Stéphane Guillou (stragu) --- There's two aspects to this issue: 1. Prioritisation of the language information in the status bar: currently, it is hidden before the "Overwrite mode", "Selection mode" and "Digital Signature" sections, which from my experience are not used as often as the Language section. There's even a section that looks empty, I can't figure out what it is for. (See screenshot in next comment.) 2. I like the idea of abbreviating the language to its code before it is completely hidden (e.g. going from "English (Australia)" to "en-AU") Design/UX, what do you think? Some kind of easyhack once it's scoped out? Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 39663a323c3330c18b610fcdc9e9c75ddac770f1 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160230] MRU Recent files list entries numbered, no need to be
https://bugs.documentfoundation.org/show_bug.cgi?id=160230 V Stuart Foote changed: What|Removed |Added Version|24.8.0.0 alpha0+ Master |Inherited From OOo --- Comment #4 from V Stuart Foote --- Oh, wait! In fact the numbered entries are picked up as accelerator mnemonics for their respective documents. Opening the main File -> Recent Documents each "numbered" document can be keyboard opened via its number. But only working for documents 1 - 9. Doesn't work for 2 digit entries. I guess either fix that to reach the full MRU listing, or strip out the numbering. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160230] MRU Recent files list entries numbered, no need to be
https://bugs.documentfoundation.org/show_bug.cgi?id=160230 V Stuart Foote changed: What|Removed |Added Summary|Writer: recent files list |MRU Recent files list |with numbers (bad) -- |entries numbered, no need |should be (in my opinion) |to be |without numbers | -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160230] Writer: recent files list with numbers (bad) -- should be (in my opinion) without numbers
https://bugs.documentfoundation.org/show_bug.cgi?id=160230 V Stuart Foote changed: What|Removed |Added Blocks||61174 Status|NEW |UNCONFIRMED CC||andreas.heini...@yahoo.de, ||heiko.tietze@documentfounda ||tion.org, ||libreoffice-ux-advise@lists ||.freedesktop.org, ||vsfo...@libreoffice.org Keywords||needsUXEval Component|Writer Web |UI Ever confirmed|1 |0 --- Comment #3 from V Stuart Foote --- Yes, don't see much point to numbering the MRU. It is not like there is a keyboard means to open a specific entry directly using its number, rather just keyboard cursor movements or mouse pointer and click. The numbering is not helpful. +1 to purge the numbering. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=61174 [Bug 61174] [META] Recent Documents List -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160227] Add timer/clock to single-screen presentation
https://bugs.documentfoundation.org/show_bug.cgi?id=160227 Rafael Lima changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||rafael.palma.l...@gmail.com --- Comment #1 from Rafael Lima --- Makes sense to me. Let's hear the UX team. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160194] Add all 3 Spotlight commands (Paragraph Style, Character Style, Direct Formatting) to Style Inspector
https://bugs.documentfoundation.org/show_bug.cgi?id=160194 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org --- Comment #2 from V Stuart Foote --- While available to activate as individual checkboxes now from main menu Format -> Spotlight, or as single checkbox on each of the SB Stylist deck for PS or CS. And the UNO can be further customized for KB or menu/contextmenu use. But Spotlight's ability to visually locate paragraph or character styles applied in document text makes it very useful for making pointer selections when working from the SB 'Style Inspector' deck. I have to agree that having a checkbox toggle for each of the three current Spotlight flavors available on the 'Style Inspector' deck would make for better UX--enable disable from there. And would self-guide users in the style review of their page content. +1 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159533] Add custom separators to all field variables
https://bugs.documentfoundation.org/show_bug.cgi?id=159533 Heiko Tietze changed: What|Removed |Added URL||https://ask.libreoffice.org ||/t/separator-after-custom-n ||umber-range-without-heading ||-number/101549/3 --- Comment #11 from Heiko Tietze --- (In reply to William Friedman from comment #10) > Fields | Variables | Number Range | Format And how do you cross-reference this field? > Is there any reason not to file an enhancement request to fix them? You are getting me onboard - but still no cigar :-) Seriously, you define a use case that needs to be solved, not a solution that we have to implement. UX should verify the use case, ensure it's generic, without impact on other workflows, and eventually suggesting the UI/UX part of implementation. Technically we are limited by the format. ODF 1.2 defines 7.4.13 The element has the following attributes: style:num-format 19.500 style:num-format The values of the style:num-format attribute are 1, i, I, a value of type string 18.2, an empty string, a or A. 19.503 style:num-suffix The style:num-prefix and style:num-suffix attributes specify what to display before and after the number. I read this as if we can access the style:num-format in a text:sequence but not the style:num-suffix. It requires a change to the file format (that needs to be implemented in all applications - and all other formats too). -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159533] Add custom separators to all field variables
https://bugs.documentfoundation.org/show_bug.cgi?id=159533 --- Comment #10 from William Friedman --- Thank you, Heiko. The reason I didn't see this feature is because Fields | Variables | Number Range | Format doesn't allow a user-defined format, whereas Set Variable does (and, when incremented in this way, basically reproduce Number Range). Is there a reason not to allow user-defined formats for Number Range? The limitations you point out -- no apparent way to reference an individual element, no way to display the total number of elements -- are severe. Is there any reason not to file an enhancement request to fix them? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160185] Would like a width control for Web view in Writer (like in Google Docs' Pageless view)
https://bugs.documentfoundation.org/show_bug.cgi?id=160185 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||8349 --- Comment #3 from V Stuart Foote --- (In reply to Heiko Tietze from comment #2) And there is the suggestion for a new MUFFIN mode in bug 128349 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159860] Use "Delete unused master slides" independently from "Minimize Presentation" tool
https://bugs.documentfoundation.org/show_bug.cgi?id=159860 --- Comment #5 from Timur --- Created attachment 193111 --> https://bugs.documentfoundation.org/attachment.cgi?id=193111=edit PPTX with large number of master slides (In reply to Heiko Tietze from comment #4) > I wonder in what situation this may happen. We had a case, explosion of number that was fixed in bug 157740. Whoever used saving to PPTX might have gotten many master slides that sow down Impress. Since original from bug 155512 does not give warning in MSO, I attach modified one that does. > Attachment 188496 [details] from bug 156400 has ~400 master slides. Is it a > constructed example? It does not give warning in MSO, cannot say why. Maybe it is about duplicated master slides. > Fixing bug 158773 sounds more reasonable to me than alerting the user at > some random number. I think those are different issues. MSO loads prez very fast but still warns for unusual number of master slides, that may plague the usage. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159923] Add max shrink and space width customization options to upcoming smart justification feature
https://bugs.documentfoundation.org/show_bug.cgi?id=159923 Heiko Tietze changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED Blocks||114534 --- Comment #6 from Heiko Tietze --- We discussed the topic in the design meeting. Since the function intends to improve compatibility any customization would be wrong. And such option sounds like over-engineering, without a use case and no user request. So we recommend to not add this (at least not in the UI) until users ask for it with a good use case. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=114534 [Bug 114534] [META] Paragraph alignment bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159380] UNO command to close all documents
https://bugs.documentfoundation.org/show_bug.cgi?id=159380 Heiko Tietze changed: What|Removed |Added CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org, ||hoss...@libreoffice.org, ||mentoring@documentfoundatio ||n.org Status|UNCONFIRMED |NEW See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=77 ||590 Keywords|needsUXEval |difficultyInteresting, ||easyHack, skillCpp Summary|close all (documents / |UNO command to close all |windows) Writer |documents Ever confirmed|0 |1 Blocks||86899 --- Comment #12 from Heiko Tietze --- We discussed the topic in the design meeting. The requested command could be implemented but not added to the UI (just for customization). It should close documents from all modules as it intends to re-open the start center. Alternatively, and probably the better solution, is to show the start center while modules are open, see bug 77590. Adding a UNO command is not too difficult, prototypes are likely in the resolved issues at the META ticket. Hossein, please add some code pointer how to close all open documents. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=86899 [Bug 86899] [META] Requests for the addition of UNO commands -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159985] Changing Macro Security level should warn about the need to reload the file to apply the settings
https://bugs.documentfoundation.org/show_bug.cgi?id=159985 Heiko Tietze changed: What|Removed |Added Keywords|needsUXEval | Blocks||116885, 107659 CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #15 from Heiko Tietze --- We discussed the topic in the design meeting. Both proposals, to show an infobar requesting the user to reload and a label in the macros security option dialog or the restart confirmation box sound like a reasonable solution. In any case we should inform the user about the need to reload. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107659 [Bug 107659] [META] Macro bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=116885 [Bug 116885] [META] Privacy and data security issues -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159543] Proper feedback needed when resizing a frame or graphical objects wont be accepted
https://bugs.documentfoundation.org/show_bug.cgi?id=159543 Heiko Tietze changed: What|Removed |Added Hardware|x86-64 (AMD64) |All Keywords|needsDevAdvice, needsUXEval | Summary|Cannot resize graphical |Proper feedback needed when |objects that overlap|resizing a frame or |header/footer |graphical objects wont be ||accepted CC|libreoffice-ux-advise@lists | |.freedesktop.org| Ever confirmed|0 |1 Blocks||108357 Status|UNCONFIRMED |NEW --- Comment #15 from Heiko Tietze --- We discussed the topic in the design meeting. It likely feels wrong to block the vertical sizing and/or to hide the handles. We also rejected the idea to show an infobar on drop when the resizing is rejected internally (although it might be easy to implement). The best solution is to give a proper feedback during the resizing, which could be a red frame when the new size is not accepted. That depends on the height and width and means to recalculate on-the-fly. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108357 [Bug 108357] [META] Writer frame/image/OLE style bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159533] Add custom separators to all field variables
https://bugs.documentfoundation.org/show_bug.cgi?id=159533 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159533] Add custom separators to all field variables
https://bugs.documentfoundation.org/show_bug.cgi?id=159533 --- Comment #9 from Heiko Tietze --- Created attachment 193110 --> https://bugs.documentfoundation.org/attachment.cgi?id=193110=edit Example file Checked the function and it works out of the box. You need to set a self-referencing variable and define an "Additional (number) formats..." where the number is followed by the parenthesis, like "0)". But I have no idea how you would add a cross-reference to a specific item in this SEQ-list. And you also don't know the total number before the sequence starts, only afterwards. (In reply to William Friedman from comment #4) > Issue X is discussed in [*3*] sources: *1*) A, *2*) B, *3*) C. According to > source [*1*] See the attached document. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 148184] FORMATTING create a means to represent an integer as an IP Address
https://bugs.documentfoundation.org/show_bug.cgi?id=148184 Heiko Tietze changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159860] Use "Delete unused master slides" independently from "Minimize Presentation" tool
https://bugs.documentfoundation.org/show_bug.cgi?id=159860 Heiko Tietze changed: What|Removed |Added Blocks||108392 CC||kelem...@ubuntu.com --- Comment #4 from Heiko Tietze --- (In reply to Timur from comment #2) > It may be useful to warn about large number of unused master slides... I wonder in what situation this may happen. The shipped templates have a reasonable number of master slides. Perhaps if you play with the Master Slides sidebar deck or the Change Slide Master... function. Attachment 188496 from bug 156400 has ~400 master slides. Is it a constructed example? Fixing bug 158773 sounds more reasonable to me than alerting the user at some random number. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108392 [Bug 108392] [META] Master slide bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160194] Add all 3 Spotlight commands (Paragraph Style, Character Style, Direct Formatting) to Style Inspector
https://bugs.documentfoundation.org/show_bug.cgi?id=160194 --- Comment #1 from Heiko Tietze --- The spotlight is available via Stylist for PS and CS and the main menu for all three. Another route to enable the view sounds like over-engineering to me and clutters the simple Styles Inspector unnecessarily. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160185] Would like a width control for Web view in Writer (like in Google Docs' Pageless view)
https://bugs.documentfoundation.org/show_bug.cgi?id=160185 Heiko Tietze changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #2 from Heiko Tietze --- The pandora's box for a distraction-free view is bug 37817. With a similar request in bug 37967 about an "Option like MS WORD's normal view". The web-view (along with html editing features) is a legacy that we should get rid of. "Pageless" is an oxymoron for text processors, in my opinion. Keep in mind that a text may have content in header/footer. Some tickets discuss the whitespace feature. Bug 94164 asking for less spacing between pages (resolved WFM) and bug 130023 requesting a reasonable space between pages. Assuming that "I am looking for something akin to the 'pageless' view in Google Docs" intends to have a distraction free view mode, I suggest to make this ticket a duplicate. Agreed, David? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160185] Would like a width control for Web view in Writer (like in Google Docs' Pageless view)
https://bugs.documentfoundation.org/show_bug.cgi?id=160185 Stéphane Guillou (stragu) changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||stephane.guillou@libreoffic ||e.org Keywords||needsUXEval Blocks||103302 Summary|Would like a width control |Would like a width control |for Web view in Writer |for Web view in Writer ||(like in Google Docs' ||Pageless view) Component|Writer |Writer Web See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0111 --- Comment #1 from Stéphane Guillou (stragu) --- As mentioned in bug 160111: Google Docs allows changing the text width easily from View > Text Width, with four options available: Narrow, Medium, Wide, Full. I do agree that it would help with readability. See also https://en.wikipedia.org/wiki/Line_length Currently, the workarounds I can think of: - user might intuitively play with the horizontal ruler's indent controls, which only affects the current paragraph and has surprising consequences when changing back to Normal view. - Change the width of the actual window, which is not ideal as it will hide parts of the UI. But this also ties into what is discussed in bug 37817 and bug 53895, as well as the Normal View topic in bug 37967 and 67698. Design/UX team, what do you think? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103302 [Bug 103302] [META] Writer's web layout/view bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160194] Add all 3 Spotlight commands (Paragraph Style, Character Style, Direct Formatting) to Style Inspector
https://bugs.documentfoundation.org/show_bug.cgi?id=160194 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||134554 Severity|normal |enhancement Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=134554 [Bug 134554] [META] Style Inspector -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160194] New: Add all 3 Spotlight commands (Paragraph Style, Character Style, Direct Formatting) to Style Inspector
https://bugs.documentfoundation.org/show_bug.cgi?id=160194 Bug ID: 160194 Summary: Add all 3 Spotlight commands (Paragraph Style, Character Style, Direct Formatting) to Style Inspector Product: LibreOffice Version: 7.6.0.3 release Hardware: All OS: All Status: UNCONFIRMED Keywords: needsUXEval Severity: normal Priority: medium Component: Writer Assignee: libreoffice-b...@lists.freedesktop.org Reporter: stephane.guil...@libreoffice.org CC: libreoffice-ux-advise@lists.freedesktop.org, rayk...@gmail.com The new spotlight features (for paragraph styles, character styles and direct formatting) we got in LO 7.6 are a great match for using with the Style Inspector, which lists details about all three. I suggest adding three tick boxes in the sidebar to control these commands: Spotlight: [ ] Paragraph Styles [ ] Character Styles [ ] Direct Formatting Because of the length of the labels, icons might be a better fit, to keep it in a single row: Spotlight: [PS] [CS] [DF] Relevant UNO commands are: .uno:SpotlightParaStyles (since 24.2) .uno:SpotlightCharStyles (since 24.2) .uno:HighlightCharDF (since 7.6) -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159906] A11Y sidebar: Too many issue reports about direct character formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=159906 --- Comment #5 from Stéphane Guillou (stragu) --- (In reply to V Stuart Foote from comment #4) > -1 for an action button, stripping out the DF in bulk doesn't encourage the > author to review the DF impact on accessible content. Maybe there's a good opportunity here to link to our new 7.6 "Format > Spotlight > Character Direct Formatting" feature (bug 106556), so the user can review? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159860] Use "Delete unused master slides" independently from "Minimize Presentation" tool
https://bugs.documentfoundation.org/show_bug.cgi?id=159860 Stéphane Guillou (stragu) changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org Priority|medium |low Keywords||needsUXEval Summary|Add command to clean up |Use "Delete unused master |unused master slides|slides" independently from ||"Minimize Presentation" ||tool --- Comment #3 from Stéphane Guillou (stragu) --- OK, let's see what UX/Design think then. This would likely require a new UNO command. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159543] Cannot resize graphical objects that overlap header/footer
https://bugs.documentfoundation.org/show_bug.cgi?id=159543 --- Comment #14 from Cor Nouws --- (In reply to Bob Harvey from comment #6) > Woah, just a minute. > > That's not "invalid". That's a hidden solution. Where in the user > interface is that exposed? where in the help pages does it tell you to do > that if you can't drag the handles? How the blue blistering blazes is > someone supposed to guess they can do that? Basically one needs an expert at the desk to help with any question ;) (In reply to Bob Harvey from comment #10) > I just expect the drag handles to work if the cursor knows they are there > and changes shape to suggest they should. That's all I expect. Changing the handles is further dragging is blocked, looks a nice improvement to me. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159380] close all (documents / windows) Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=159380 Cor Nouws changed: What|Removed |Added Version|24.2.0.0 alpha0+|Inherited From OOo -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159380] close all (documents / windows) Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=159380 Cor Nouws changed: What|Removed |Added CC||c...@nouenoff.nl --- Comment #11 from Cor Nouws --- (In reply to Eyal Rozenberg from comment #9) > I'm not sure this is important enough to merit a slot on the file menu by > default. Indeed. Esp. since there is a quit, and restarting is fast enough.. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159985] Changing Macro Security level should warn about the need to reload the file to apply the settings
https://bugs.documentfoundation.org/show_bug.cgi?id=159985 Cor Nouws changed: What|Removed |Added Version|24.8.0.0 alpha0+ Master |Inherited From OOo -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159985] Changing Macro Security level should warn about the need to reload the file to apply the settings
https://bugs.documentfoundation.org/show_bug.cgi?id=159985 Cor Nouws changed: What|Removed |Added CC||c...@nouenoff.nl --- Comment #14 from Cor Nouws --- (In reply to Bdac from comment #13) > Maybe, when the user changes the value (ex. set level from High to Low) a > confirmation window could ask if it’s really sure to apply the change, and > inform at the same time that his validation requires a file reload ? Would be a bit more nagging then the following.. (In reply to Mike Kaganski from comment #12) > The maximal tolerable level of nagging would be an infobar. My preferred > solution would be an infotip in the security dialog. No intrusive prompts. which looks fine to me. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159543] Cannot resize graphical objects that overlap header/footer
https://bugs.documentfoundation.org/show_bug.cgi?id=159543 Cor Nouws changed: What|Removed |Added Version|7.6.4.1 release |Inherited From OOo CC||c...@nouenoff.nl OS|Windows (All) |All -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 148184] FORMATTING create a means to represent an integer as an IP Address
https://bugs.documentfoundation.org/show_bug.cgi?id=148184
--- Comment #2 from cson...@halmai.hu ---
I came here to read the motivation behind this feature request.
I cannot see too many reasons why someone would store an IP address as an
integer rather than a string. I had only one idea: creating subsequent IP
addresses via autofill. To me, it looks like a very rare edge case and I would
rather do it by this formula in A2 to convert the integer of A1:
=TEXTJOIN(".", 0,
BITRSHIFT(A1, 24),
BITAND(BITRSHIFT(A1, 16), 255),
BITAND(BITRSHIFT(A1, 8), 255),
BITAND(A1, 255)
)
I may be wrong and there can be more valid use cases. If this is the case,
could you show some, please?
--
You are receiving this mail because:
You are on the CC list for the bug.
[Bug 159906] A11Y sidebar: Too many issue reports about direct character formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=159906 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org --- Comment #4 from V Stuart Foote --- Given that the 'accessibility check' feature resident in the SB is to *assist* the author with preparing accessible text, organizing it to do so efficiently makes sense. It is really not performing validation--rather it just indicates some text span that may need consideration. Currently each instance of "Text formatting conveys additional meaning" flag is picked up for *each* DF the author has assigned. Grouping by Paragraph would certainly help the author proceed through the document. But if the author does not want to consider each instance, they can already collapse the 'Formatting' exposure arrow. And doing so "by paragraph" or "by section" would be reasonable improvement and, suited to task of checking document accessibility. However would note that currently assigning a defined 'Character style' (e.g. Emphasis, Strong Emphasis) unlike the DF does not trigger the same additional meaning flag. Why not? -1 for an action button, stripping out the DF in bulk doesn't encourage the author to review the DF impact on accessible content. Beyond that, it is up to the users chosen Assistive Technology tool to consume and respond to document formatting--fonts, attributes, super/subscript, emphasis, highlight/marking, styling and color. Such DF and styling within a document are not incorrect, rather the author should be made aware where they have applied them--and the potential impact their formatting choices can have. Viewed in that context, +1 to organize by Paragraph, -1 to strip out ALL DF in a single pass, but fine to review/process at paragraph or section. And need to consider handling of applied Character styling in an accessible text context. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159533] Add custom separators to all field variables
https://bugs.documentfoundation.org/show_bug.cgi?id=159533 --- Comment #8 from Mike Kaganski --- Thanks Michael; then please ignore me - since the mentioned feature isn't appropriate for inline list creation, then no objections to have some "before"/"after" affixes for number range fields, similar to what lists have. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159533] Add custom separators to all field variables
https://bugs.documentfoundation.org/show_bug.cgi?id=159533 --- Comment #7 from Michael Stahl (allotropia) --- (In reply to Mike Kaganski from comment #6) > There is already an implementation of "inline lists", which IIRC Michael > Stahl had implemented for Word compatibility; it is implemented by marking > the "paragraph mark" as hidden. It has no UI for now, as well as other > "paragraph mark" properties; and IMO, the proper thing would be to implement > the UI. I remember that there was some "missing UI for paragraph mark" bug > report (or maybe some mention in another bug) ... yes the UI for this is missing, forgot if there is a bug for it... you want to create "inline lists" by hiding paragraph marks? ... i have just tried this in Word and am happy to report that it doesn't work, you get only the first paragraph's list number :) -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160167] Bullets and Numbering dialog: Selection label
https://bugs.documentfoundation.org/show_bug.cgi?id=160167 Heiko Tietze changed: What|Removed |Added CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Status|NEW |ASSIGNED Blocks||103364 Keywords|needsUXEval | Assignee|libreoffice-b...@lists.free |heiko.tietze@documentfounda |desktop.org |tion.org --- Comment #2 from Heiko Tietze --- Yes, let's remove this label. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103364 [Bug 103364] [META] Bullets and numbering dialog bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159906] A11Y sidebar: Too many issue reports about direct character formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=159906 --- Comment #3 from Heiko Tietze --- +1 for a "Clear" (DF) interaction at the issue. But if this is going to be implemented we cannot merge all DF from one paragraph into the same issue. I would keep every single issue separate. I wonder if "text formatting conveys additional meaning" is the actual problem with DF. Ultimately it's the same whether you apply italic or Emphasis to a word. DF may be used inconsistently however. Other issues: Double-click on a hyperlink is very much unexpected. Text selection is not possible. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159533] Add custom separators to all field variables
https://bugs.documentfoundation.org/show_bug.cgi?id=159533 Mike Kaganski changed: What|Removed |Added CC||michael.st...@allotropia.de --- Comment #6 from Mike Kaganski --- (In reply to Heiko Tietze from comment #5) > Mike, what do you think? There is already an implementation of "inline lists", which IIRC Michael Stahl had implemented for Word compatibility; it is implemented by marking the "paragraph mark" as hidden. It has no UI for now, as well as other "paragraph mark" properties; and IMO, the proper thing would be to implement the UI. I remember that there was some "missing UI for paragraph mark" bug report (or maybe some mention in another bug) ... -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159533] Add custom separators to all field variables
https://bugs.documentfoundation.org/show_bug.cgi?id=159533 Heiko Tietze changed: What|Removed |Added CC||mikekagan...@hotmail.com --- Comment #5 from Heiko Tietze --- Mike, what do you think? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159906] A11Y sidebar: Too many issue reports about direct character formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=159906 Stéphane Guillou (stragu) changed: What|Removed |Added Keywords||accessibility, needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||stephane.guillou@libreoffic ||e.org Whiteboard| QA:needsComment| Status|UNCONFIRMED |NEW Blocks||107318 Ever confirmed|0 |1 --- Comment #2 from Stéphane Guillou (stragu) --- Agreed, this is too overwhelming and should be handled more gracefully. + 0.5 for grouping by paragraph, +1 for offering an action button. Maybe UX/Design team can chime in? This issue applies to many accessibility warnings, and there could be a solution that applies to most cases. For example: - only show the first X repeated warnings (with their individual Fix It buttons if they exists); - followed by a right-aligned string like "...and X more similar issues." with a "Fix All" button next to it. Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: f42363c51672a5b3685b0b9b11e932680530dce3 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107318 [Bug 107318] [META] Clear formatting and clear direct formatting issues -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160167] Bullets and Numbering dialog: Selection label
https://bugs.documentfoundation.org/show_bug.cgi?id=160167 Buovjaga changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159533] Add custom separators to all field variables
https://bugs.documentfoundation.org/show_bug.cgi?id=159533 William Friedman changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159533] Add custom separators to all field variables
https://bugs.documentfoundation.org/show_bug.cgi?id=159533 --- Comment #4 from William Friedman --- The use case, as I said, is to try to implement in-line lists. I admit it's a kludge, but until the normal list function allows for in-line lists, the only way to create an in-line list is to use variables. I'm not sure what's unclear about the use case. They are the same use cases as ordinary lists. Here's an example of how one might use this: Issue X is discussed in [*3*] sources: *1*) A, *2*) B, *3*) C. According to source [*1*], blah; according to source [*2*], blah blah. According to source [*3*], however, ... In this example, *1*, *2*, and *3* are the field variables. The content of the square brackets are references to those variables. The first one refers to the largest numbered variable, and the next three refer to the individual variables of the list. What I'm asking for, specifically, is the ability to customize the separator surrounding each of those variables -- the close parenthesis in this example -- just like I can customize the separator after ordinary list numbers in Bullets and Numbering | Customize | Separator. Again, this wouldn't be necessary if Lists & Numbering supported in-line lists, but it doesn't. This also wouldn't be necessary if one could search and replace field variables, but that also isn't a possibility. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159794] Zero 'before text' indent first before removing paragraph break
https://bugs.documentfoundation.org/show_bug.cgi?id=159794 Heiko Tietze changed: What|Removed |Added Keywords|needsUXEval | CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Summary|inconsistency in|Zero 'before text' indent |backspacing through indents |first before removing ||paragraph break -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 33603] Presenter notes should be available in normal view as a scrolling pane
https://bugs.documentfoundation.org/show_bug.cgi?id=33603 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bz.apache.org/ooo/s ||how_bug.cgi?id=56172 Whiteboard|target:24.8.0 |target:24.8.0 ||inReleaseNotes:24.8 Hardware|Other |All CC||stephane.guillou@libreoffic ||e.org --- Comment #53 from Stéphane Guillou (stragu) --- I mentioned it in the release notes: https://wiki.documentfoundation.org/index.php?title=ReleaseNotes%2F24.8=revision=744253=744249 We can of course update later on if need be. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159794] inconsistency in backspacing through indents
https://bugs.documentfoundation.org/show_bug.cgi?id=159794 --- Comment #7 from Dieter --- (In reply to Heiko Tietze from comment #6) > Any objection? OK for me. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159985] Changing Macro Security level should warn about the need to reload the file to apply the settings
https://bugs.documentfoundation.org/show_bug.cgi?id=159985 --- Comment #13 from Bdac --- Maybe, when the user changes the value (ex. set level from High to Low) a confirmation window could ask if it’s really sure to apply the change, and inform at the same time that his validation requires a file reload ? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159543] Cannot resize graphical objects that overlap header/footer
https://bugs.documentfoundation.org/show_bug.cgi?id=159543 --- Comment #13 from Bdac --- Maybe, the 3rd solution is the better one : don't enable autosize by default to make user aware of it. Give more freedom and flexibility... -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159380] close all (documents / windows) Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=159380 --- Comment #10 from Bdac --- Many different programs (like Krita and others) use this concept about « Close all » function and this feature comes in handy when you want to close any open session but continue to use the sotfware already open. In relation to what Peter was saying, it’s true that the various functions are often grouped together by logic at the end of the file menu : Close, Close all and Exit program. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 157981] personal / custom dictionaries should be easily portable
https://bugs.documentfoundation.org/show_bug.cgi?id=157981 --- Comment #4 from Heiko Tietze --- Adding it to a dictionary means you need being able to pick one in the spell-checking dialog (there is for sure a ticket), if it's the auto-correction we don't have such thing yet. In both cases it requires an enhancement to the document format. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159533] Add custom separators to all field variables
https://bugs.documentfoundation.org/show_bug.cgi?id=159533 Heiko Tietze changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #3 from Heiko Tietze --- The use case is still weak. Why is the inline list sorted, and how do you access the items later. Basically we are bound to the standardized document format. And fields just do not have a separator attribute that could be read by alternative office programs. Using some macro is of course always an option, in particular since you probably want to use a shortcut for the list item field. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160114] ZOOM factor: make it change in all Writer instances (in all writer windows)
https://bugs.documentfoundation.org/show_bug.cgi?id=160114 Heiko Tietze changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #2 from Heiko Tietze --- (In reply to peter josvai from comment #0) > It would be extremely useful.. Why? In general I disagree with making simple dialogs more complex, as you do by adding another confirmation button. Not to speak about the long labels. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 153979] AutoCorrect: Many symbol replacements should be defined for [All], not language-by-language, and work in [None]
https://bugs.documentfoundation.org/show_bug.cgi?id=153979 --- Comment #5 from Klaus --- (In reply to V Stuart Foote from comment #3) > Would agree with populating a listing [ALL] for common use, where a majority > of current replacements across all locales/supported langs should be > consolidated and delivered. > > Then the delivered locale/lang specific autocorrection listings could be > reduced. As a user, another advantage would be making customization easier. For instance, I write documents in German and English and if I want to customize language-independent auto-replacements like :alpha:, I need to manually do so for each language that I use. > The [All] listing of corrections is present, but empty. Requiring user > action to populate. > > Don't see a need to invest in a [None]. Please keep in mind, that currently [All] and [None] are somehow conflated, with replacement rules defined for [All] being applied to text with language [None], but to no other language. (In reply to Eike Rathke from comment #1) > I beg to differ: > [None] means exactly that, _no language tool processing at all_. > > [All] should be processed in, well, all languages except [None]. Currently, my use-case can be made to work with the workaround of 1. Editing the auto-corrections for English (USA) and [All] to ensure that ~/.config/libreoffice/4/user/autocorr/acor_en-US.dat ~/.config/libreoffice/4/user/autocorr/acor_und.dat both exists. 2. Close LibreOffice. 3. Replace acor_und.dat by a copy of acor_en-US.dat. This workaround works, because currently the replacement rules for [All] are actually used for [None] text. If in the future [None] text uses no auto-correction rules at all, the workaround will not work anymore. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160114] ZOOM factor: make it change in all Writer instances (in all writer windows)
https://bugs.documentfoundation.org/show_bug.cgi?id=160114 Stéphane Guillou (stragu) changed: What|Removed |Added Keywords||needsUXEval Blocks||107923 CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||stephane.guillou@libreoffic ||e.org --- Comment #1 from Stéphane Guillou (stragu) --- Thanks for the suggestion. Let's see what UX/Design think. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107923 [Bug 107923] [META] Zoom issues -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159794] inconsistency in backspacing through indents
https://bugs.documentfoundation.org/show_bug.cgi?id=159794 --- Comment #6 from Heiko Tietze --- (In reply to lvm from comment #5) > Essentially treat (any) indent as tab characters +1 from my side It means the indentation before text is zeroed on backspace similar to the first line indent. Any objection? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 51824] CONFIGURATION: Zoom button should also close the dialog (which should be made non-modal)
https://bugs.documentfoundation.org/show_bug.cgi?id=51824 --- Comment #9 from Heiko Tietze --- Agree with Stuart on the WF verdict. The zoom dialog offers a couple of special zoom levels such as "Fit to Width". I see no need to play with those settings or to see what this exactly means. For frequent zooming we provide access via the statusbar. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 153979] AutoCorrect: Many symbol replacements should be defined for [All], not language-by-language, and work in [None]
https://bugs.documentfoundation.org/show_bug.cgi?id=153979 Heiko Tietze changed: What|Removed |Added CC||so...@libreoffice.org --- Comment #4 from Heiko Tietze --- These are defined in extras/source/autocorr/*/DocumentList.xml for >ls af-ZA da en-AU es ga-IE is lb-LU nl-BE pt-PT sl sr-Latn-RS th zh-CN bg de en-GB fa hr it lt pl ro sr-CS sr-ME tr zh-TW ca dsb en-US fi hsbja mn pt ru sr-Latn-CS sr-RS vi cs el en-ZA fr hu ko nl pt-BR sk sr-Latn-ME sv vro Meaning Hebrew, for example, has no replacement for -->. But it feels to me as if this is controlled by the local community since we have no configuration for [All], whether it is actually none or any. My take is WF. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159883] In lowriter's Help Menu I want to see "Keyboard shortcuts"
https://bugs.documentfoundation.org/show_bug.cgi?id=159883 Heiko Tietze changed: What|Removed |Added Blocks||98259 Component|Writer |Documentation Keywords|needsUXEval | Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org, ||olivier.hallot@libreoffice. ||org, ||rafael.palma.l...@gmail.com --- Comment #4 from Heiko Tietze --- We have different kind of shortcuts: those that are assigned to a UNO command and thereby listed with the command label in the menu, eg. View > Formatting Marks (Ctrl+F10). Some commands are not available in the main menu like "Multiselection On" (available in the status bar) and you can learn about this shortcut Shift+F8 (ridiculous assignment!) from the mentioned customization dialog. And there are hard-coded key combinations such as Ctrl+Q to close the application that requires to read the documentation (or being used to the shortcut). Learn more at https://books.libreoffice.org/en/GS74/GS7414-KeyboardShortcuts.html or at the more recently version at https://nextcloud.documentfoundation.org/s/JZPbqLcjYt4oayD. Seems to me as if the shortcuts are now located at the respective chapter. The idea to have something like Help > Keyboard shortcuts listing all combinations sounds wrong to me as it would present way too many and unsorted results. At least not per inbuilt functionality but maybe per extension... I vaguely remember something similar built-in. Anyway, forwarding the topic to documentation and resolving it as WF. Feel free to revert the state. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=98259 [Bug 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160125] Standard Palette - Dark Blue 1 (from COL_DEFAULT_SHAPE_STROKE) is lighter than Blue
https://bugs.documentfoundation.org/show_bug.cgi?id=160125 Heiko Tietze changed: What|Removed |Added CC|heiko.tietze@documentfounda | |tion.org| Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #5 from Heiko Tietze --- (In reply to V Stuart Foote from comment #3) > Otherwise => WF I see no urgent need to make the base colors appear exactly at some point in the color space. => WF (Feel free to reopen, Raymond, ideally with a use case that makes it clear why this is a serious bug.) -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159880] FILEOPEN When I say "lowriter foo.txt" and foo.txt does not exist, it should open a new empty document that saves to that name instead of dying
https://bugs.documentfoundation.org/show_bug.cgi?id=159880 --- Comment #11 from Mike Kaganski --- Additional code pointer could be the MediaDescriptor service [1], which has SuggestedSaveAsDir and SuggestedSaveAsName members. So your command line option could set them, or even its URL - the latter would skip the dialogs in case of direct Save. [1] https://api.libreoffice.org/docs/idl/ref/servicecom_1_1sun_1_1star_1_1document_1_1MediaDescriptor.html -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160125] Standard Palette - Dark Blue 1 (from COL_DEFAULT_SHAPE_STROKE) is lighter than Blue
https://bugs.documentfoundation.org/show_bug.cgi?id=160125 Julien Nabet changed: What|Removed |Added CC|serval2...@yahoo.fr | --- Comment #4 from Julien Nabet --- Thank you V Stuart for detailed feedback. I read some comments on tdf#112541 and I just discovered about RYB. (thought it was a typo for "RGB"). I agree with Raymond and it's a pity that "Dark blue" is lighter than "Blue" but don't know at all what to change about QA tests. => uncc myself. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159883] In lowriter's Help Menu I want to see "Keyboard shortcuts"
https://bugs.documentfoundation.org/show_bug.cgi?id=159883 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org --- Comment #3 from V Stuart Foote --- (In reply to Dieter from comment #2) Agree, the Tools -> Customize dialog fulfills both needs. Identifying the commands available to assign to Keyboard (but also the other UI elements) and showing the assignments already made. The Help and Wiki articles, and module specific User Guides are also available. No real advantage to crafting a "Keyboard shortcuts" entry on the Help menu, and a support/l10n tail to maintain if we were to do so. IMHO => WF -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 153979] AutoCorrect: Many symbol replacements should be defined for [All], not language-by-language, and work in [None]
https://bugs.documentfoundation.org/show_bug.cgi?id=153979 V Stuart Foote changed: What|Removed |Added CC||nem...@numbertext.org, ||vsfo...@libreoffice.org --- Comment #3 from V Stuart Foote --- Would agree with populating a listing [ALL] for common use, where a majority of current replacements across all locales/supported langs should be consolidated and delivered. Then the delivered locale/lang specific autocorrection listings could be reduced. The [All] listing of corrections is present, but empty. Requiring user action to populate. Don't see a need to invest in a [None]. @Lásló, how do you see this? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 153979] AutoCorrect: Many symbol replacements should be defined for [All], not language-by-language, and work in [None]
https://bugs.documentfoundation.org/show_bug.cgi?id=153979 Dieter changed: What|Removed |Added CC||dgp-m...@gmx.de, ||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval Blocks||103341 --- Comment #2 from Dieter --- Since it is an enhancement request let's ask design-team Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103341 [Bug 103341] [META] AutoCorrect and Word Completion bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159883] In lowriter's Help Menu I want to see "Keyboard shortcuts"
https://bugs.documentfoundation.org/show_bug.cgi?id=159883 Dieter changed: What|Removed |Added CC||dgp-m...@gmx.de, ||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval --- Comment #2 from Dieter --- Martin, you can customise shortcuts with Tools -> Customize and this is explained in help page. So I don't think, that a new entry in help menu is really needed, but we can ask dsign-tea of course. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160125] Standard Palette - Dark Blue 1 (from COL_DEFAULT_SHAPE_STROKE) is lighter than Blue
https://bugs.documentfoundation.org/show_bug.cgi?id=160125 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||2541 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160125] Standard Palette - Dark Blue 1 (from COL_DEFAULT_SHAPE_STROKE) is lighter than Blue
https://bugs.documentfoundation.org/show_bug.cgi?id=160125 V Stuart Foote changed: What|Removed |Added Summary|Palette - Dark Blue 1 is|Standard Palette - Dark |lighter than Blue |Blue 1 (from ||COL_DEFAULT_SHAPE_STROKE) ||is lighter than Blue CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vsfo...@libreoffice.org Blocks||104118 Keywords||needsUXEval --- Comment #3 from V Stuart Foote --- This was by design to minimally impact the QA build testing. For bug 114719 the standard pallet "Light Blue 2" tint and "Dark Blue 1" shade were assigned [1] colors slightly off from the trilinear tensor calculated value to retain standard fill (COL_DEFAULT_SHAPE_FILLING) and stroke (COL_DEFAULT_SHAPE_STROKE) called out by xdef.hxx used extensively in test files used by the existing QA tests. At the time, it was decided that the shift of these tints/shades in the generated standard pallet was more efficient than reworking the QA tests and sample files, as the xdef.hxx defined colors had to appear on the pallet. It is feasible to replace all the impacted QA test files and scripts, but still a lot of effort. IMHO probably not worth the dev effort, but for a devotee to color theory it might be appealing to tackle the changes. Otherwise => WF =-ref-= [1] https://gerrit.libreoffice.org/48887 where these colors for Standard RYB pallet are defined: Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=104118 [Bug 104118] [META] Color palette bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 51824] CONFIGURATION: Zoom button should also close the dialog (which should be made non-modal)
https://bugs.documentfoundation.org/show_bug.cgi?id=51824 V Stuart Foote changed: What|Removed |Added Resolution|--- |WONTFIX Status|NEW |RESOLVED -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 51824] CONFIGURATION: Zoom button should also close the dialog (which should be made non-modal)
https://bugs.documentfoundation.org/show_bug.cgi?id=51824 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org --- Comment #8 from V Stuart Foote --- will close the dialog without action. Also, have "Zoom In" (.uno:ZoomPlus) "Zoom Out" (.uno:ZoomMinus) available from 7.1 as for bug 45705 to assign to keyboard, menu or toolbar customization, and at 7.6 assigned default matching mouse wheel zoom in/out steps. Doing anything additional with the "Zoom..." dialog (.uno:Zoom) no longer seems needed. Open select and apply, or escape. Otherwise customize to zoom in or out with keyboard, mouse, menu or toolbar button as desired. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 51824] CONFIGURATION: Zoom button should also close the dialog (which should be made non-modal)
https://bugs.documentfoundation.org/show_bug.cgi?id=51824 Stéphane Guillou (stragu) changed: What|Removed |Added Version|3.5.4 release |Inherited From OOo Summary|CONFIGURATION: Zoom button |CONFIGURATION: Zoom button |doesn't operate in the same |should also close the |manner as other buttons |dialog (which should be ||made non-modal) Severity|minor |enhancement CC||hoss...@libreoffice.org, ||libreoffice-ux-advise@lists ||.freedesktop.org, ||stephane.guillou@libreoffic ||e.org Keywords||needsUXEval --- Comment #7 from Stéphane Guillou (stragu) --- I guess this would require the zoom dialog to be made non-modal, as the button can't be interacted with currently - which in my opinion would be an improvement (i.e. moving the dialog off canvas to see the effect of zoom settings. But it would then mean that an "apply" button would need to be added to the Zoom dialog. UX/Design, do you agree? Hossein, what kind of easyHack could this be? For implementation, check that the status bar zoom factor works the same as the toolbar button. Repro in recent trunk build: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 98c42f7e961e77d7f1c02d53862e4e78ecd07653 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded And Ooo 3.3. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159380] close all (documents / windows) Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=159380 --- Comment #9 from Eyal Rozenberg --- I'm not sure this is important enough to merit a slot on the file menu by default. How about a command for closing all the documents which the user can, optionally, place on a menu? Peter, do you find that sufficient? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159985] Changing Macro Security level should warn about the need to reload the file to apply the settings
https://bugs.documentfoundation.org/show_bug.cgi?id=159985 --- Comment #12 from Mike Kaganski --- I disagree. When I work with many documents, and at some point, I open a specific document, and realize that it requires a different security level. I modify the level, and may want to reload that specific file. But I would hate to have a nagging prompt. The maximal tolerable level of nagging would be an infobar. My preferred solution would be an infotip in the security dialog. No intrusive prompts. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159985] Changing Macro Security level should warn about the need to reload the file to apply the settings
https://bugs.documentfoundation.org/show_bug.cgi?id=159985 --- Comment #11 from Eyal Rozenberg --- (In reply to Rafael Lima from comment #9) > What about we simply reload all opened files right after the security > options are changed? This would be invisible to the user and would make the > macros work. Invisibility is inappropriate of course (as Mike points out). But - why not give a prompt for reloading documents? That could explain why it may be important to reload. And the user could choose whether they want to (save and) reload everything or nothing (and perhaps individual files? Not sure.) (In reply to Mike Kaganski from comment #10) > I suggest even do it without saving all the unsaved changes ;-P What about prompting the user about a reload? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159794] inconsistency in backspacing through indents
https://bugs.documentfoundation.org/show_bug.cgi?id=159794 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160072] Inconsistent handling of objects on Calc sheets with select all (Delete, clear contents, copy-paste)
https://bugs.documentfoundation.org/show_bug.cgi?id=160072 --- Comment #7 from jollytall --- I never had a problem with the object being copied, and I did not comment on it. I do not think we should make users unhappy. I had two issues: - The original was that if an object is considered part of a sheet or attached to some cells, then it should be treated consistently, i.e. if I select it, it should also be deleted with Del. I do not see why Cut should be different than Del. - In your quoted sentence I just replied to your comment that selecting cells does not select the object, while actually selecting enough cells, selects the object as well. My issue here was again not the fact that it can be copied, but that it cannot be deleted the same way. That led me to the thought that it would be logic to see when the object is selected and when it is not. Thinking more on it, this highlights why the current working is inconsistent. Imagine that a selection is always clearly visible (orange dots or animated dashes), what probably would be good anyway. What would we see now when Ctrl-A? This is one step and should only have one result, either or: Option 1. If the object is marked selected (so it should be selected!) then why it is not deleted when I press Del? Option 2. If the object is not marked selected (so it surely is not selected) then why is it Cut, Copied, when I press Ctrl-X or Ctrl-C? I still think that there should be one answer. I personally do not have a preference, whether Option 1 or 2 is better, but I think it should be marked on the object. If it were marked then the user could also easily add the object to the selection (in case of Option 2) with a Ctrl-Click or similarly could remove it (Option 1) before Del, Ctrl-X, Ctrl-C. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159533] Add custom separators to all field variables
https://bugs.documentfoundation.org/show_bug.cgi?id=159533 William Friedman changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159533] Add custom separators to all field variables
https://bugs.documentfoundation.org/show_bug.cgi?id=159533 --- Comment #2 from William Friedman --- The use case is for an in-line list. The fields are not cross-references, just numbers enumerating the elements of the list, just like in ordinary lists. Since one can customize the separator for regular lists, the enhancement request is to add the possibility of using separators for field variables as well, since there is no other way of making an in-line list. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 157981] personal / custom dictionaries should be easily portable
https://bugs.documentfoundation.org/show_bug.cgi?id=157981 Stéphane Guillou (stragu) changed: What|Removed |Added URL|https://ask.libreoffice.org |https://ask.libreoffice.org |/t/saving-personal-dictiona |/t/how-do-i-attach-a-custom |ry-the-words-i-added-to-lib |-dictionary-to-a-libreoffic |reoffice-dictionary-saving- |e-document/30535 |or-copying-them-to-another- | |computer/30781 | Severity|normal |enhancement CC||libreoffice-ux-advise@lists ||.freedesktop.org Version|24.2.0.0 alpha0+|Inherited From OOo Blocks||108728 Keywords||needsUXEval --- Comment #3 from Stéphane Guillou (stragu) --- Thanks for clarifying, Peter. I found an even better match on Ask.LO: someone asking for a way to attach a dictionary to a file (like we allow embedding fonts): https://ask.libreoffice.org/t/how-do-i-attach-a-custom-dictionary-to-a-libreoffice-document/30535 (on top of the related https://ask.libreoffice.org/t/saving-personal-dictionary-the-words-i-added-to-libreoffice-dictionary-saving-or-copying-them-to-another-computer/30781) I can see the use case, where a file with specialist language that will probably only ever pertain to that specific document, needs sharing around to different contributors, or editing on different computers. The example of writing fiction with heavy world-building. UX/Design team, what do you think about supporting attaching a dictionary to a file? Has it been suggested before? Would involve extending the format and a fair bit of UI changes, I guess... Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108728 [Bug 108728] [META] Dictionaries bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159794] inconsistency in backspacing through indents
https://bugs.documentfoundation.org/show_bug.cgi?id=159794 lvm changed: What|Removed |Added CC||lmiro...@yandex.ru --- Comment #5 from lvm --- Actually in Word's numbered list backspace promotes the numbering and when no more numbering is left starts removing indents; paragraph break is removed only when nothing more is left to remove. Personally I think the Word way is more efficient as it lets one remove outdent without diving deep into formatting dialogues. Essentially it treats indents as tab characters. -- You are receiving this mail because: You are on the CC list for the bug.
