[Libreoffice-ux-advise] [Bug 148447] Replace All in Writer comments
https://bugs.documentfoundation.org/show_bug.cgi?id=148447 Dieter changed: What|Removed |Added Keywords||needsUXEval Whiteboard| QA:needsComment| CC||dgp-m...@gmx.de, ||libreoffice-ux-advise@lists ||.freedesktop.org --- Comment #1 from Dieter --- I support this enhancement request, but I'm not a member of design-team cc: Design-Team -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 127294] Add more tips of the day (and make it module-specific eventually)
https://bugs.documentfoundation.org/show_bug.cgi?id=127294 --- Comment #79 from sdc.bla...@youmail.dk --- Proposal for a new ToD: Never use certain arrow styles? Remove them with the Delete button on the Format > Text Box and Shape > Line > Arrow Styles tab. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148732] UI: Default Character in Format Styles is called No Character Style in character styles deck of the sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=148732 Telesto 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.
[Libreoffice-ux-advise] [Bug 148673] Should the Bullet and Numbering toolbar also appear with unnumbered (chapter) headings?
https://bugs.documentfoundation.org/show_bug.cgi?id=148673
--- Comment #9 from sdc.bla...@youmail.dk ---
(In reply to Mike Kaganski from comment #8)
> No strong opinion on this ...
Aww..that is disappointing. I was sure that at least you would like the idea
of removing the offer to apply DF numbering to Heading N paragraphs in an
outline bar.
> except one: please stop using "headings" here.
No problem. See comment 3 ("neutral about name change").
I appreciate that there is much confusion/debate about this terminology -- and
I am not trying to participate in that discussion -- or to promote particular
terminology.
But I needed to use some words to communicate about the functionality. Sorry if
my "lay" terms were a source of distress. But today you have given some
technical definitions, which are fine with me -- so from bug 141452 comment
#24:
>* Heading is a paragraph having an outline level other than "Text Body".
That was also my understanding. And that was also my intended meaning of
"heading" here. Concretely, whenever the cursor is in a paragraph with outline
level other than Text Body, then a special toolbar (not Bullets and Numbering)
should appear.
But after some experiments and reflection, I now see/believe that it only makes
sense for a context-sensitive toolbar to appear when the cursor is placed in a
Heading N PS paragraph – for the primary reason that it is not possible to
change the outline level of Heading paragraphs that are non-Heading N (using
toolbar/menu commands). (which by luck was also the OP).
With that additional condition (only show context-sensitive toolbar for Heading
N PS), then it makes a lot of sense to call a context-sensitive toolbar for
“Outline” (which is also the name that the Organizer uses to show “List Style”
for Heading N PS).
--
You are receiving this mail because:
You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148723] Request improvement :Create a REFLECT text effect in Font attributes like italic, bold...
https://bugs.documentfoundation.org/show_bug.cgi?id=148723 V Stuart Foote changed: What|Removed |Added Keywords||needsUXEval Ever confirmed|1 |0 Status|NEW |UNCONFIRMED CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vstuart.fo...@utsa.edu --- Comment #2 from V Stuart Foote --- Well this is not is ODF spec. We can do it manually after a fashion, with a conversion of the text string to curve, a copy paste, an invert and some fiddling with the resulting SVG. ODF supports that, but not very convenient--and this is a convenience feature. Do wonder what happens on LO import of OOXML text with that "attribute" in use. Doing it seamlessly as a font attribute seems out of scope to project, with no need to extend ODF to accomodate. But there could be valid interoperability issues to address. IMHO => WF -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148728] Should Format -> Character/ Paragraph entry's not be called Paragraph/Character Direct Formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=148728 Xisco Faulí changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||xiscofa...@libreoffice.org -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148272] Cross-reference to numbering wrongly includes separator character
https://bugs.documentfoundation.org/show_bug.cgi?id=148272 --- Comment #8 from Charles Valente --- (In reply to Heiko Tietze from comment #7) > Created attachment 179725 [details] > Example > > Using numbers instead of literals works the same (and without the locale > bug). Thank you for your reply, but I still can't get it. What exactly should we do to have the same behavior as before? For me, the "bug" still happens, and the print screen you sent haven't clarified much. What I am unfortunately having to do now to number the paragraphs is a 'brute force' approach, creating an arabic numerical field variable specific as a 'paragraph number'. Cross-references to this variable are obviously correct now, but I have to manually insert the separation character. But for other files I have written before 7.2.6 (some of them with hundreds of pages), I cannot use that workaround. Botton line is: I will stop upgrading LO, because it is getting worse in a sense. I do not doubt the current development team has the best of intentions, but I am very thankful to those developing color television standards in the 1950s and 1960s, because instead of making all the millions of black and white television sets obsolete, they created a backward compatible system, so that those with the old TVs could watch a color transmission. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148320] Explicit toggle for ToC/Index title
https://bugs.documentfoundation.org/show_bug.cgi?id=148320 --- Comment #7 from Heiko Tietze --- (In reply to Eyal Rozenberg from comment #6) > ... the user is unlikely to realize that an empty title means no-title Don't think so. And, as Dieter pointed out, we have a preview. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148320] Explicit toggle for ToC/Index title
https://bugs.documentfoundation.org/show_bug.cgi?id=148320 --- Comment #6 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #5) > I don't see this pattern, meaning consistency in terms of input fields that > are in use if a checkbox is checked or otherwise mean empty content. Ah. So, I didn't mean consistency in terms of an input field, but rather consistency in terms of dichotomy between non-empty and non-existence: Footer can be empty Header can be empty Footnote can be empty, sort of Endnotecan be empty, sort of Heading paragraph can be empty Commentcan be empty Captioncan be empty ToC title can't be empty Given all the rest, the user is unlikely to realize that an empty title means no-title, and would waste time trying to look for a checkbox which doesn't exist. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148320] Explicit toggle for ToC/Index title
https://bugs.documentfoundation.org/show_bug.cgi?id=148320 --- Comment #5 from Heiko Tietze --- (In reply to Eyal Rozenberg from comment #2) > ... is not consistent with other behavior in LO. I don't see this pattern, meaning consistency in terms of input fields that are in use if a checkbox is checked or otherwise mean empty content. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148597] FORMATTING request enhancement: create formatted Table of Figures using tabs before and after index
https://bugs.documentfoundation.org/show_bug.cgi?id=148597 Heiko Tietze changed: What|Removed |Added CC||mikekagan...@hotmail.com --- Comment #1 from Heiko Tietze --- You align the content label (Figure) at left and the number right, followed by a left aligned caption. Such a layout can be done only per table or in a ToC, by right-aligning a tab stop. But apparently we have a bug here, see bug 32360 and bug 94661. The actual request is going beyond the ToC. You could also expect the text of headings to align at the second line. This can be done per indentation (positive value before text and negative for first line). If you give enough space for large numbers this works well. And it should do the trick as well for ToC if you modify the "Contents x" PS properly. My take: NAB (or duplicate). What do you think, Mike? -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148320] Explicit toggle for ToC/Index title
https://bugs.documentfoundation.org/show_bug.cgi?id=148320 --- Comment #4 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #3) > I don't see a pattern. Can you explain that phrase? -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148272] Cross-reference to numbering wrongly includes separator character
https://bugs.documentfoundation.org/show_bug.cgi?id=148272 --- Comment #7 from Heiko Tietze --- Created attachment 179725 --> https://bugs.documentfoundation.org/attachment.cgi?id=179725=edit Example Using numbers instead of literals works the same (and without the locale bug). -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148629] The "Demote" command is always active in Draw (and Impress), but does not do anything on non-list paragraphs
https://bugs.documentfoundation.org/show_bug.cgi?id=148629 Heiko Tietze changed: What|Removed |Added Keywords|needsUXEval |difficultyMedium, easyHack, ||skillCpp, topicUI CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org, ||mentoring@documentfoundatio ||n.org --- Comment #4 from Heiko Tietze --- Commands that are temporarily unavailable should become disabled. Writer disables the uno:DecrementLevel unless a list style is used. We should do the same on Draw/Impress. Medium easyhack, some debugging needed. Code pointer in c2. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148320] Explicit toggle for ToC/Index title
https://bugs.documentfoundation.org/show_bug.cgi?id=148320 --- Comment #3 from Heiko Tietze --- Better compare with caption and if you leave the field empty you get an empty caption. Wouldn't expect anything else. Admittedly, the checkbox is convenient (and we have space) but I don't see a pattern. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148643] Feature Request: Categories of Fonts
https://bugs.documentfoundation.org/show_bug.cgi?id=148643 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Heiko Tietze --- Some related tickets: bug 130396 Improvement of font list bug 119915 Make it easier to work with different fonts bug 60626 Allow custom font sorting bug 119199 Selected choice of available fonts bug 116446 Font selection widget with hierarchy, filters, favorites bug 113089 Font selector box should filter on substrings bug 88416 Allow hiding fonts from font drop down list in options dialog Good to have all at one place. Let's make it a duplicate. *** This bug has been marked as a duplicate of bug 91130 *** -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148591] Rename "page text area top" and "page text area bottom" to "Above (or Below) page text area
https://bugs.documentfoundation.org/show_bug.cgi?id=148591 Heiko Tietze changed: What|Removed |Added Keywords|needsUXEval | CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org --- Comment #4 from Heiko Tietze --- The topic was on the agenda of the design meeting. Bug 148593 comment 9 summarizes the discussion. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148593] "Left page border" and "right page border" options for Horizontal "to" position in Position and Size for shapes are misleading names, which should be changed
https://bugs.documentfoundation.org/show_bug.cgi?id=148593 Heiko Tietze changed: What|Removed |Added Ever confirmed|0 |1 Keywords|needsUXEval | CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Status|UNCONFIRMED |NEW --- Comment #9 from Heiko Tietze --- We discussed the topic at the design meeting. To summarize, the label must not use "Margin", "Padding" nor "Border". Long labels might be more precise for those who understand the function but not easier for laymen. And we do have a nice preview that clearly shows where the object is positioned (this could be better placed next to the controls). CSS/PDF use Media-, Trim-, Bleed-, Crop-, and Artbox but this is not likely to be an advantage for understanding. Rearranging the controls so the labels read as a sentence make sense. And, if possible, we should allow to always have an offset not only for "From Left" making this entry obsolete. Something like: [Start (Left)/End (Right)/Center resp. Inside/Outside/Center] of [Paragraph area/Paragraph text area/Left paragraph region/Right paragraph region/Left page region/Right page region/Entire Page/Page Text Area] at [ 0 cm]. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 141452] Rename Tools > Chapter Numbering back to Outline Numbering
https://bugs.documentfoundation.org/show_bug.cgi?id=141452 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||7281 -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 141452] Rename Tools > Chapter Numbering back to Outline Numbering
https://bugs.documentfoundation.org/show_bug.cgi?id=141452 --- Comment #25 from Mike Kaganski --- (In reply to Mike Kaganski from comment #24) > * Outline is a concept of paragraphs having the associated levels, creating > corresponding structure. My poor English made that point rather bad. Rather: * Outline is a concept of hierarchical document structure, created using respective levels assigned to (some) document paragraphs. I must stress that my wording itself may be flawed *because of my poor language*. Anyway, the corrected meaning must reflect the Writer's concepts, and only be loosely related to the human language words of the same spelling (just to create some association in user, as in "it is similar to", nothing more). -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148465] Rework Sparklines's context menus
https://bugs.documentfoundation.org/show_bug.cgi?id=148465 Heiko Tietze changed: What|Removed |Added Keywords|needsUXEval | CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org --- Comment #3 from Heiko Tietze --- The topic was on the agenda for the design meeting. To summarize, do not list sparkline commands at all for cells w/o sparklines (my take) or at least have only "Insert Sparkline" at the root level. With SL context it's not needed to have Insert but users expect Edit. Ideally we show/enable Ungroup only if we have a group and vice versa. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148513] Poor nomenclature for Manual Break
https://bugs.documentfoundation.org/show_bug.cgi?id=148513 Heiko Tietze changed: What|Removed |Added Keywords|needsDevAdvice, needsUXEval | CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org --- Comment #23 from Heiko Tietze --- We discussed the topic in the design meeting. To summarize, me prefers a simple solution (comment 8), Seth proposes a more verbose solution (comment 14), and Eyal commented to better use Start/End. What we not discussed but might be the best solution is to show a thumbnail that illustrates what "Start (Left)" and "Full Line Next" means. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 141452] Rename Tools > Chapter Numbering back to Outline Numbering
https://bugs.documentfoundation.org/show_bug.cgi?id=141452
--- Comment #24 from Mike Kaganski ---
(In reply to Eyal Rozenberg from comment #23)
Please note that you try to force some *dictionary* meaning of terms into
Writer. This is wrong.
Outline, chapter, and heading are OK to (and *must*) have *special* and
specific meaning in Writer. When you write "Most documents people write don't
have Chapters anyway" (and the like), you are completely away from the problem
of correct use of specific Writer term, confusing different entities (and
making a potential fix much harder).
So:
* Heading is a paragraph having an outline level other than "Text Body".
* Chapter is a part of text starting from a heading with outline level 1, and
up to the next heading with outline level 1.
* Outline is a concept of paragraphs having the associated levels, creating
corresponding structure.
Having some styles with word "heading" in them is just fine, and simply must be
accompanied with word "style" ("paragraph style") each time, like in "Heading 1
paragraph style".
Trying to make it more complex, by mixing with so insanely complex matter as
human language is (aggravated by translations, which multiply the associated
meanings) is a mistake.
--
You are receiving this mail because:
You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148469] Give alert for unsaved when sending document in email
https://bugs.documentfoundation.org/show_bug.cgi?id=148469 Heiko Tietze changed: What|Removed |Added CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Keywords|needsUXEval | --- Comment #6 from Heiko Tietze --- We discussed the topic at the design meeting and recommend to do what Thomas suggested in comment 5. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 147837] When merging cells, it is not good that 'Keep the contents of the hidden cell' is the default
https://bugs.documentfoundation.org/show_bug.cgi?id=147837 Heiko Tietze changed: What|Removed |Added Severity|normal |enhancement Blocks||108320 CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Hardware|x86-64 (AMD64) |All Keywords|needsUXEval | --- Comment #10 from Heiko Tietze --- The topic was on the agenda of the design meeting. MSO can read hidden content from merged cells but when applied on MSO365 it offers only to remove the content. We provide all options and to keep the content is a convenient feature. On the other hand, the security/privacy argument is valid. While a warning/infobar on save is not possible and on load is probably too late, the recommendation is to show an indicator (optionally) for hidden content. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108320 [Bug 108320] [META] Calc cells merging and splitting bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 141452] Rename Tools > Chapter Numbering back to Outline Numbering
https://bugs.documentfoundation.org/show_bug.cgi?id=141452 --- Comment #23 from Eyal Rozenberg --- (In reply to Mike Kaganski from comment #21) > I strongly believe this proposal should be done, and tdf#104151 was badly > misguided. So, it seems I'm in rare agreement withe Mike on something :-) > We have multiple confusion here. ... We have currently just a mess. Yes, and even when a user figures things out, it's not that they create coherent notions in their mind; they're still in a situation of "I have to memorize semi-equivalences on not-intuitively-equivalent concepts, and what-term-applies-where-and-how". > Outline is the concept that should be used when the structure (including > chapters and sections, and applied by the levels in paragraphs) is meant. It > also must be used in Navigator instead of the "Headings". Well, either instead of, or separately from, but yes. > Chapter is only used when first outline level is used (as in ToC's Create > Index or Table of Contents For - note how the Chapter used there is > *different* in the meaning from what tdf#104151 assigned it to). and there isn't a good enough indication that Heading 1 is supposed to be equivalent to Chapter; nor, in fact, is that a good idea. Most documents people write don't have Chapters anyway. > Heading should be used very carefully - to refer to paragraphs having > outline level applied; Here we disagree. "Heading" means "paragraph with Heading/Heading N" styles. That's how the lay user understands it. Paragraph with outline level can be called something involving the word outline: "Outlines", "Outlined", "Outlined paragraphs" or whatever. > and also to refer to Heading N paragraph style - but > these two uses must be disambiguated in writing. So, my disagreement above is how I suggest disambiguate. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 141452] Rename Tools > Chapter Numbering back to Outline Numbering
https://bugs.documentfoundation.org/show_bug.cgi?id=141452 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||8718 -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 141452] Rename Tools > Chapter Numbering back to Outline Numbering
https://bugs.documentfoundation.org/show_bug.cgi?id=141452 --- Comment #22 from Mike Kaganski --- (In reply to Mike Kaganski from comment #21) > I strongly believe this proposal should be done, and tdf#104151 was badly > misguided. Sorry, tdf#107573 was meant. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 141452] Rename Tools > Chapter Numbering back to Outline Numbering
https://bugs.documentfoundation.org/show_bug.cgi?id=141452 --- Comment #21 from Mike Kaganski --- (In reply to Regina Henschel from comment #1) > I think "Chapter" is the only way to make in unambiguous. Heh, if only it were true... I strongly believe this proposal should be done, and tdf#104151 was badly misguided. We have multiple confusion here. Outline is the concept that should be used when the structure (including chapters and sections, and applied by the levels in paragraphs) is meant. It also must be used in Navigator instead of the "Headings". Chapter is only used when first outline level is used (as in ToC's Create Index or Table of Contents For - note how the Chapter used there is *different* in the meaning from what tdf#104151 assigned it to). Heading should be used very carefully - to refer to paragraphs having outline level applied; and also to refer to Heading N paragraph style - but these two uses must be disambiguated in writing. We have currently just a mess, with more proposals coming to make it worse - see the use of "heading" term in comments in tdf#148673, caused by complete lack of distinction between these related, but different concepts. See also tdf#138748, also dealing with a similar problem - the misuse of related but different terms, leading to real user confusion (e.g., tdf#137175). -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148673] Should the Bullet and Numbering toolbar also appear with unnumbered (chapter) headings?
https://bugs.documentfoundation.org/show_bug.cgi?id=148673 --- Comment #8 from Mike Kaganski --- (In reply to sdc.blanco from comment #7) No strong opinion on this ... except one: please stop using "headings" here. There *already* exists a confusion introduced by "outline" and "chapter" meaning the same (in some contexts; and different things in some other contexts: cf. "chapter numbering" renamed from "outline numbering", which made "chapter equal to outline"; while "chapter" means some more narrow thing in ToC dialog, where "Create Index or Table of Contents For" has a "Chapter" choice). So use of *Headings* as another wrong and confusing synonym here is no-go. Headings are already used in this way in Navigator, giving even more headaches. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148673] Should the Bullet and Numbering toolbar also appear with unnumbered (chapter) headings?
https://bugs.documentfoundation.org/show_bug.cgi?id=148673 --- Comment #7 from sdc.bla...@youmail.dk --- (In reply to Mike Kaganski from comment #6) > It could be done; however, So...exploring the idea a little further... > or that two "identical" toolbars pop > up sometimes - when in numbered headings, both toolbar for lists and toolbar > for outlines will appear, and many people already frown upon toolbar popups). Oh! That was not my idea. IIUC -- headings and lists (at least conceptually) should be treated differently so, when ... - cursor in Chapter Heading (numbered or unnumbered), then only "Outline" (or "Heading") toolbar pops up. - cursor in List (DF or List Style): - only "List" toolbar pops up. AFAICT -- no need to modify content of Bullet and Numbering toolbar (including its name, which would avoid having to update the help pages) And for a new Headings bar (starting with current B default) a. Can remove .uno:OutlineBullet (and the hidden uno:DefaultBullet, .uno:DefaultNumbering, .uno:SetOutline) (isn't is a problem or at least undesired to use these DF controls on Headings?) b. Could also remove .uno:InsertNeutralParagraph and .uno:ContinueNumbering (which gives a leaner toolbar with no greyed out icons) c. Can use TargetURL so that different names/tooltips can be given to "arrows" that promote/demote, and move up and down for Headings and for Lists (that was sort of an intent in bug 144493, but it was not fully possible, bug 147107) d. Is there a .uno for Tools > Chapter Numbering? That could appropriately be added to a Heading bar. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148673] Should the Bullet and Numbering toolbar also appear with unnumbered (chapter) headings?
https://bugs.documentfoundation.org/show_bug.cgi?id=148673 --- Comment #6 from Mike Kaganski --- (In reply to sdc.blanco from comment #5) > What about making two separate context-sensitive toolbars -- one for > "Chapter Headings" and one for "Lists"? It could be done; however, I believe it would be redundant (having very similar set of controls); and also confusing (to the point when users will be upset that they customized the toolbar appearing on lists, and then it shows without customizations when in unnumbered headings (they would fail to see that these are different toolbars); or that two "identical" toolbars pop up sometimes - when in numbered headings, both toolbar for lists and toolbar for outlines will appear, and many people already frown upon toolbar popups). -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148673] Should the Bullet and Numbering toolbar also appear with unnumbered (chapter) headings?
https://bugs.documentfoundation.org/show_bug.cgi?id=148673 --- Comment #5 from sdc.bla...@youmail.dk --- (In reply to Mike Kaganski from comment #4) > Please note that name change is *essential* for the OP Ok. So a next logical step would be to ask: What about making two separate context-sensitive toolbars -- one for "Chapter Headings" and one for "Lists"? -- You are receiving this mail because: You are on the CC list for the bug.
