Bug 1554725 - RFE: ibus emoji should hide missing characters by default
Summary: RFE: ibus emoji should hide missing characters by default
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: ibus
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: fujiwara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1626904 1626906
TreeView+ depends on / blocked
 
Reported: 2018-03-13 08:55 UTC by Jens Petersen
Modified: 2019-04-09 04:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1626904 1626906 (view as bug list)
Environment:
Last Closed: 2019-04-09 04:14:08 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Jens Petersen 2018-03-13 08:55:29 UTC 
Description of problem:
I feel it is better to hide glyphs without font coverage by default.

Version-Release number of selected component (if applicable):
ibus-1.5.18-1.fc28

How reproducible:
100%

Steps to Reproduce:
1. ibus emoji lists glyphs with no font coverage.
   (search for some less common character)

Actual results:
some tofu (unicode substitute character) glyphs listed

Expected results:
Better to hide missing glyphs by default
Comment 1 fujiwara 2018-03-14 05:44:45 UTC 
Why do you think they should be hidden?
I even want to show them.
E.g. Even if emojis are missed glyphs, the code points are useful.
E.g. some control chars U+0080 to U+009F in Unicode.
They just explain no glyphs and input, output, copy paste works fine.
Comment 2 Jens Petersen 2018-03-14 07:49:56 UTC 
Well you could have an option to show them. :)

Anyway close if you think it is a bad idea.
Comment 3 fujiwara 2018-03-14 08:05:42 UTC 
OK, I'd leave this bug for a while to get other opinions.
Comment 4 Jens Petersen 2018-12-12 03:39:19 UTC 
I don't see any missing emoji now... dunno if that is because of newer emoji font.
And search is moved to emoji input so I think this bug is already addressed.
Note You need to log in before you can comment on or make changes to this bug.