Bug 57894 - Implement OS native highlighting on each component
Summary: Implement OS native highlighting on each component
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 55876 94784 (view as bug list)
Depends on:
Blocks: MacOS-Wishlist Selection
  Show dependency treegraph
 
Reported: 2012-12-04 19:37 UTC by Emir Sarı
Modified: 2019-02-02 15:27 UTC (History)
12 users (show)

See Also:
Crash report or crash signature:


Attachments
Calc cell highlighting (91.65 KB, image/png)
2012-12-04 19:38 UTC, Emir Sarı
Details
Numbers cell highlighting (210.63 KB, image/png)
2012-12-04 19:39 UTC, Emir Sarı
Details
NeoO native cell highlighting (122.20 KB, image/png)
2012-12-04 19:39 UTC, Emir Sarı
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Emir Sarı 2012-12-04 19:37:21 UTC
Hello,

Under another thread this has been mentioned, but I thought this deserves its own bug/enhancement thread.

LibreOffice uses its own highlighting instead the OS default and this looks inconsistent with the rest of the applications. While this looks ugly to some, it is mostly not feasible. Especially on Mac platform it is really cumbersome. 

I will attach a screenshot from Calc on OS X, as you will see it is nearly impossible to distinguish the selected cells from the rest of the spreadsheet.  

Also Numbers has also its own highlighting method, instead filling the cells, it uses a thick selection border, which is always distinguishable. 

But the best practice would be using native highlighting of each platform itself, establishing consistency with the rest of the system. 

Best regards,
Comment 1 Emir Sarı 2012-12-04 19:38:33 UTC
Created attachment 71009 [details]
Calc cell highlighting
Comment 2 Emir Sarı 2012-12-04 19:39:03 UTC
Created attachment 71010 [details]
Numbers cell highlighting
Comment 3 Emir Sarı 2012-12-04 19:39:51 UTC
Created attachment 71011 [details]
NeoO native cell highlighting
Comment 4 Emir Sarı 2012-12-04 19:43:01 UTC
Please feel free to add more screenshots/comparisons from different desktop environments.
Comment 5 Adolfo Jayme 2012-12-23 00:49:34 UTC
I agree. LibreOffice should use the native highlighting style of every platform, and remove these highlighting customization options that it currently has.
Comment 6 Roman Eisele 2012-12-27 11:15:00 UTC
> I agree. LibreOffice should use the native highlighting style of every
> platform, and remove these highlighting customization options that it
> currently has.

I agree completely. Using the native highlighting method on every platform would make LibreOffice *feel* native, and would make it immeditaly feel familiar and handy to new users. So, while on the *rational* side this is not one of the most urgent enhancement requests, it is of considerable importance on the *emotional* side.

A simple example of what I mean by rational/emotional importance:
I have resisted for a long time to use GIMP, not because it would not provide most of the features I need for everyday imaging work, but simply because it felt so “clumsy” to me; I was far too familiar (a) to the native Mac OS (X) UI and
(b) to Photoshop. Now GIMP 2.8 has got a semi-native Mac OS X UI, and suddenly I begin to feel comfortable with it, and actually to use it ...

Because of this personal experience I think it is really important to make the UI feel native and familiar to the users, especially the simple basics of the UI, and the highlighting is definitely a part of these basics.
Comment 7 Emir Sarı 2013-01-30 18:02:21 UTC
Since bug https://bugs.freedesktop.org/show_bug.cgi?id=38244 has been solved, and these text ranges still seem to use custom LO highlighting, I wonder if standard Mac highlighting could be tweaked to reflect standard Mac text highlighting colours (shown here: http://www.macmousecalls.com/files/system-preferences3.jpg)

Best regards,
Comment 8 Emir Sarı 2014-02-09 07:46:11 UTC
One downside of using custom highlighting (in this case LO highlighting), it does not really select the glyphs, it just covers them with a layer of its own, so character visibility declines. IMO this is bad m'kay.
Comment 9 Adolfo Jayme 2015-10-05 14:35:27 UTC
*** Bug 94784 has been marked as a duplicate of this bug. ***
Comment 10 Robinson Tryon (qubit) 2015-12-13 10:58:01 UTC Comment hidden (obsolete)
Comment 11 jani 2016-02-11 13:04:12 UTC
There are no code pointer
Comment 12 Yousuf Philips (jay) (retired) 2016-02-12 12:17:22 UTC
NEEDINFO isnt a suitable status for this bug as nothing is needed from the OP. If code pointers are needed and we want to track such bugs, then a whiteboard keyword would likely be the better option to do that.
Comment 13 Robinson Tryon (qubit) 2016-02-18 14:51:42 UTC Comment hidden (obsolete)
Comment 14 Adolfo Jayme 2017-09-03 04:41:50 UTC
*** Bug 55876 has been marked as a duplicate of this bug. ***