[Bug 160881] Forms: Checkboxes and Radiobuttons couldn't set readonly, only could set disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=160881 Stéphane Guillou (stragu) changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 161078] Allow direct formatting for page sequences instead of editing the style
https://bugs.documentfoundation.org/show_bug.cgi?id=161078 --- Comment #16 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #13) > We rather should drop all DF than adding more. > > => NAB/WF Now, wait a minute, Heiko. If I opened a new bug today, asking to remove the ability to apply DF to, say, characters - would you support it? Set it to NEW? Even though it would mean dropping almost all commands on the Formatting toolbar? Less facetiously though: Are there official, binding policies regarding the extent of DF and the eventual "fate" of DF? If there are, let's talk about how they apply to this bug. If there aren't, then if we ever "drop all DF" - we can drop the page sequence DF as well, and I don't see why it should be left out of DF'ing. Let us also not forget DFing in other modules, like Calc or Impress, which have even more DFable entities. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160874] Calc fails to suggest correction for formula cell without equal sign
https://bugs.documentfoundation.org/show_bug.cgi?id=160874 Stéphane Guillou (stragu) changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160869] Forms: Listboxes, set as "readonly", will be greyed out. Other controls, set "readonly", won't.
https://bugs.documentfoundation.org/show_bug.cgi?id=160869 --- Comment #3 from Robert Großkopf --- (In reply to Stéphane Guillou (stragu) from comment #2) > Following my bug 160881 comment 1, I think that the solution should be > "don't offer the read-only option for listboxes" rather than "don't grey out > read-only listboxes". That's because listboxes don't allow entering values > by hand, and therefore a read-only state is not useful. > > Copying UX/Design for opinion. Please don't set this as a solution: The content should be well readable in a read-only control. Read-only should only set "could not be choosen any new value" like it is for combo boxes. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160869] Forms: Listboxes, set as "readonly", will be greyed out. Other controls, set "readonly", won't.
https://bugs.documentfoundation.org/show_bug.cgi?id=160869 Stéphane Guillou (stragu) changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 161078] Allow direct formatting for page sequences instead of editing the style
https://bugs.documentfoundation.org/show_bug.cgi?id=161078 Dieter changed: What|Removed |Added CC||dgp-m...@gmx.de Severity|normal |enhancement --- Comment #15 from Dieter --- Reading the discussion, I think, it's not a bug, but an enhancement request. So I change severity. And I also don't see the need for DF of page styles -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 98902] Right clicking on selected text unselects it if the cursor is on a misspelled word
https://bugs.documentfoundation.org/show_bug.cgi?id=98902 --- Comment #14 from jose.ve...@urjc.es --- The behavior remains the same. Nothing changes in version 24.2.3.2. If you select text that contains misspelled words in Writer, right-clicking does not display the spell checker. However, in Impress, it does. Essentially, the behavior differs depending on whether you are in the Writer editor or a text box. Perhaps, this discrepancy could not be considered a bug, but the inconsistent behavior within the same program is confusing. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160650] allow to set comments/descriptions for conditional formattings
https://bugs.documentfoundation.org/show_bug.cgi?id=160650 Heiko Tietze changed: What|Removed |Added CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org, ||rb.hensc...@t-online.de Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Keywords|needsUXEval |needsDevAdvice Blocks||87351 Priority|medium |low --- Comment #2 from Heiko Tietze --- Sounds like a plan. But we have to consider cross-platform and -application compatibility. And the CF-name is probably not (yet) defined in ODF neither you can assign it in Excel, for example. Let's keep the ticket with low importance. The idea is to add another column to the Manage CF dialog that provides a user-defined name for CF rule-set. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=87351 [Bug 87351] [META] Conditional formatting bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 161078] Allow direct formatting for page sequences instead of editing the style
https://bugs.documentfoundation.org/show_bug.cgi?id=161078 --- Comment #13 from Heiko Tietze --- (In reply to Eyal Rozenberg from comment #11) > (In reply to Heiko Tietze from comment #7) > > While I fully agree with Mike's comments > Then please read my last comment and I'm sure you'll change your mind. Indeed, it changed my mind and I vote to not introduce any page level DF. Your blue background example strikes me as somewhat random, and even my more realistic orientation topic is prolly going to end in a lot headaches. We rather should drop all DF than adding more. => NAB/WF -- You are receiving this mail because: You are on the CC list for the bug.
