Description: Hello, I noticed that there is no margin or padding on the left of the cell name field. This is very annoying visually and is the first thing I notice after opening LO Calc. Steps to Reproduce: 1. Open LO Calc Actual Results: No margin on the left of the cell name filed Expected Results: A margin on the left of the cell name field Reproducible: Always User Profile Reset: No Additional Info: Wersja: 6.4.3.2 (x64) Identyfikator kompilacji: 747b5d0ebf89f41c860ec2a39efd7cb15b54f2d8 Wątki CPU: 2; System operacyjny: Windows 10.0 Build 19041; Render UI: domyślny; VCL: win; Ustawienia regionalne: pl-PL (pl_PL); Język UI: pl-PL Calc: threaded
Created attachment 160846 [details] Calc on Windows
Created attachment 160847 [details] Calc on Debian testing with GNOME
Also reproducible on: Version: 7.0.0.0.alpha1+ (x64) Build ID: 1ed7607454d1492f65c78443cb661d5873face6b Wątki CPU: 2; System operacyjny: Windows 10.0 Build 19041; Render UI: Skia/Raster; VCL: win; Locale: pl-PL (pl_PL); UI: pl-PL Calc: threaded
Created attachment 160879 [details] video with bug Hi, it is not a bug. The padding depends of the page zoom. See the video I made. Version: 7.0.0.0.alpha1 Build ID: 6a03b2a54143a9bc0c6d4c7f1... CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded
Are we talking about the same thing? Please see the field with _H10_ in the top left corner just under the font name _Liberation Sans_ on your video.
Ok, I see, there is a difference of padding on the left, but I think we talk about different OS, with different settings and looks.
Created attachment 161608 [details] Maybe (?) the padding in question marked The screenshot has the arrows that hopefully point to the padding in question. It seems that the address bar lacks padding that regular toolbar has. No idea if that's design choice (to align the name box with the cell grid) or some overlooked detail.
(In reply to Mike Kaganski from comment #7) > ... address bar A thinko: must had been "formula bar"
*** This bug has been marked as a duplicate of bug 133692 ***