[Libreoffice-ux-advise] [Bug 152157] Update Available icon (on menu bar) messes up ability to work with multiple Calc windows

2022-11-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152157

Adolfo Jayme Barrientos  changed:

   What|Removed |Added

Summary|Update Available icon (on   |Update Available icon (on
   |InfoBar) messes up ability  |menu bar) messes up ability
   |to work with multiple Calc  |to work with multiple Calc
   |windows |windows

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 152157] Update Available icon (on InfoBar) messes up ability to work with multiple Calc windows

2022-11-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152157

--- Comment #12 from Caolán McNamara  ---
reducing/removing the padding makes toolbars (and this thing is a little
toolbar inside the menu area) in general look nasty. Making the menubar always
large enough for the toolbar makes the menubar higher than it "should" be, so
looks a little different to everything else on Windows. Making the icons
visible on all menubars, not just the active one, sounds the most attractive
solution. Albeit needs some effort.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 152111] [UI] Add a 'protection-against-deletion' checkbox to table/index generation dialog, in addition to the existing 'Protected against manual changes' checkbox

2022-11-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152111

Cor Nouws  changed:

   What|Removed |Added

Summary|[UI] Add a  |[UI] Add a
   |'protection-against-deletio |'protection-against-deletio
   |n' checkbox to table/index  |n' checkbox to table/index
   |generation dialog, in   |generation dialog, in
   |addition to the existing|addition to the existing
   |'protect' checkbox  |'Protected against manual
   ||changes' checkbox

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 152111] [UI] Add a 'protection-against-deletion' checkbox to table/index generation dialog, in addition to the existing 'protect' checkbox

2022-11-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152111

Cor Nouws  changed:

   What|Removed |Added

 CC||c...@nouenoff.nl
Summary|Add a   |[UI] Add a
   |protection-against-deletion |'protection-against-deletio
   |checkbox to table/index |n' checkbox to table/index
   |generation dialog   |generation dialog, in
   ||addition to the existing
   ||'protect' checkbox

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 152116] Navigator: State of outline headings is lost when navigator is closed then reopened

2022-11-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152116

--- Comment #8 from V Stuart Foote  ---
(In reply to R. Green from comment #7)

> I'm referrring to the free-floating navigator, not the sidebar one.

So don't close it?  The floating Navigator  (which is the same SB framework as
the Navigator deck) is stateful and can be dragged out of the way on your
desktop as you continue to work. Even onto another display if multi-headed. 

Exactly as the Sidebar Deck can now be collapsed to Tab bar or fully hidden out
of the way.

And closing either fully will clear the treeview, and I think that is
appropriate default behavior.

Doing more to hold full treeview status between launches of the Navigator in
current session, or of pushing it out to MRU history in profile, would take
some effort and likely be non-performant. Probably not worth any dev effort for
the "temporary" Navigator--which goes away when we can finally undock decks
(bug 85905).

IMHO => WF

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 152116] Navigator: State of outline headings is lost when navigator is closed then reopened

2022-11-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152116

R. Green  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.

[Libreoffice-ux-advise] [Bug 152116] Navigator: State of outline headings is lost when navigator is closed then reopened

2022-11-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152116

--- Comment #7 from R. Green  ---
(In reply to Stéphane Guillou (stragu) from comment #6)
> R. Green does not mention the sidebar, so this report might only be about
> the separate dialog. I think the current behaviour of the sidebar might not
> need fixing (given that sidebar users will rarely close it but instead fold
> it out of the way, I assume). However, I can see users frustrated by losing
> it every time the Navigator window is closed.
> 
> R. Green, can you please clarify?

I'm referrring to the free-floating navigator, not the sidebar one.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 143886] Consider removing Attribute Blinking in Find and Replace dialog

2022-11-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143886

--- Comment #4 from Eike Rathke  ---
Even if Blinking was removed, or even more then, the option to replace Blinking
should stay as someone may want to use another visual indicator instead.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 152116] Navigator: State of outline headings is lost when navigator is closed then reopened

2022-11-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152116

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||stephane.guillou@libreoffic
   ||e.org
 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO

--- Comment #6 from Stéphane Guillou (stragu) 
 ---
Not sure if the navigator sidebar deck is handled differently to the navigator
dialog, but the two different things might introduce confusion here.

I tested releases from 6.3 to 7.5.

* Navigator sidebar deck:

I tried folding the sidebar and closing the sidebar deck: the unfolding of the
heading tree is persistent.
Only closing the entire sidebar (with View > Sidebar, or Ctrl + F5) resets the
heading tree.

* View > Navigator (or F5):

Closing the separate navigator window does lose the unfolding of the heading
tree.

R. Green does not mention the sidebar, so this report might only be about the
separate dialog. I think the current behaviour of the sidebar might not need
fixing (given that sidebar users will rarely close it but instead fold it out
of the way, I assume). However, I can see users frustrated by losing it every
time the Navigator window is closed.

R. Green, can you please clarify?

Versions:

Version: 6.3.6.2
Build ID: 2196df99b074d8a661f4036fca8fa0cbfa33a497
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3; 
Locale: de-DE (en_AU.UTF-8); UI-Language: en-US
Calc: threaded

to

Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: deb7bc82de19ea8e20c767fdf21f9ba4feb5e9f0
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 152115] Hyperlink Target in document: The last user setting is not remembered

2022-11-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152115

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   Keywords||bibisectRequest, regression
 CC||stephane.guillou@libreoffic
   ||e.org
Version|unspecified |7.4.2.3 release

--- Comment #3 from Stéphane Guillou (stragu) 
 ---
Repro in:

Version: 7.4.2.3 / LibreOffice Community
Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: de-DE (en_AU.UTF-8); UI: en-US
Calc: threaded

LO would remember and keep the heading tree unfolded (up to the last selected
item) in 7.3:

Version: 7.3.7.2 / LibreOffice Community
Build ID: e114eadc50a9ff8d8c8a0567d6da8f454beeb84f
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: de-DE (en_AU.UTF-8); UI: en-US
Calc: threaded

Therefore, regression.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 143886] Consider removing Attribute Blinking in Find and Replace dialog

2022-11-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143886

Buovjaga  changed:

   What|Removed |Added

 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org
   Keywords||needsUXEval

--- Comment #3 from Buovjaga  ---
(In reply to lol from comment #2)
> Yes, you are right. Blinking attributes are present in LO => 7. You can find
> them.
> 
> Now the question is: Is that still needed?

UX team: maybe this attribute was used so rarely that it is not a big deal to
remove the entry from Find & Replace?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 152157] Update Available icon (on InfoBar) messes up ability to work with multiple Calc windows

2022-11-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152157

--- Comment #11 from Heiko Tietze  ---
(In reply to Heiko Tietze from comment #10)
> Maybe to ensure a minimum size?

Or the idea was to just change the icon size but keep the button width/height.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 152157] Update Available icon (on InfoBar) messes up ability to work with multiple Calc windows

2022-11-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152157

--- Comment #10 from Heiko Tietze  ---
(In reply to Caolán McNamara from comment #9)
>  ImplAddButtonBorder in toolbox.cxx is adding 7pixels

And ImplDrawItem() deducts it later. Maybe to ensure a minimum size?

-- 
You are receiving this mail because:
You are on the CC list for the bug.