| Version |
Date |
User |
Field ID |
Field |
Difference |
| 5 |
2023-05-30 14:29 |
josaphat.imani |
238 |
Resolution Status |
|
| 4 |
2023-05-23 13:26 |
josaphat.imani |
53 |
Assigned to |
| - | developer |
+ | josaphat.imani |
|
| |
|
|
171 |
Related |
| - | Search usability: Search bar: no results/wrong results for unended words, Tiki trackers auto-complete: Suggested values for text fields: improve, Search usability: When searching for related tasks to link to in a tracker item, visually separate "in title" matches from "full text search" matches by highlighting the search query words in the titles, "Tag selector / tag picker" and context-dependent tags suggestions (and autocompletion) when editing a page's properties metadata |
+ | Search usability: Search bar: no results/wrong results for unended words, Tiki trackers auto-complete: Suggested values for text fields: improve, Search usability: When searching for related tasks to link to in a tracker item, visually separate "in title" matches from "full text search" matches by highlighting the search query words in the titles, "Tag selector / tag picker" and context-dependent tags suggestions (and autocompletion) when editing a page's properties metadata, Search UI: Tiki24 with Elasticsearch vs Tiki trunk (25) with Manticore: Nice UI (Select2) to select facets is missing, Tracker item fields autocompletion with tab, not just enter, Search Usability: Research search front-ends |
|
| |
|
|
238 |
Resolution Status |
|
| 3 |
2022-10-05 00:58 |
Marc Laporte |
169 |
Assigned by |
|
| |
|
|
171 |
Related |
| - | |
+ | Search usability: Search bar: no results/wrong results for unended words, Tiki trackers auto-complete: Suggested values for text fields: improve, Search usability: When searching for related tasks to link to in a tracker item, visually separate "in title" matches from "full text search" matches by highlighting the search query words in the titles, "Tag selector / tag picker" and context-dependent tags suggestions (and autocompletion) when editing a page's properties metadata |
|
| 2 |
2022-08-10 17:59 |
Jeff Fortin T. |
54 |
Description |
| | This probably is a generic problem that ought to be fixed everywhere (?), but I'm reporting an annoyance of mine with """"what I can see right in front of me"""" here: | | This probably is a generic problem that ought to be fixed everywhere (?), but I'm reporting an annoyance of mine with """"what I can see right in front of me"""" here: |
| | * given how extensive the amount of wiki pages (and tickets) in the intranet, the """"Find"""" quick searchbar at the top-right of this website fails to fulfill its purpose for me because in the majority of cases I don't know which result I want to look at, so I want to look at multiple ones, but the autocompletion results do not properly hyperlink the items so I can't middle-click with the mouse to open various search results (selectively) in new tabs. | | * given how extensive the amount of wiki pages (and tickets) in the intranet, the """"Find"""" quick searchbar at the top-right of this website fails to fulfill its purpose for me because in the majority of cases I don't know which result I want to look at, so I want to look at multiple ones, but the autocompletion results do not properly hyperlink the items so I can't middle-click with the mouse to open various search results (selectively) in new tabs. |
| - | ** When an autocompletion result line is clickable, it should have a hyperlink-style """"becomes underlined on mouse-over""""; this communicates the UI affordance easily, and is ''much'' better than the current hover styling which is way too subtle (text goes from gray to black). Please do not rely on subtle low-contrast color differences to convey hover status, get rid of the gray and make it regular hyperlink color with on-hover underline, please. |
+ | ** When an autocompletion result line is clickable, it should have a hyperlink-style """"becomes underlined on mouse-over""""; this communicates the UI affordance easily, and is ''much'' better than the current hover styling which is way too subtle (text goes from gray to black). Please do not rely on subtle low-contrast color differences to convey hover status, get rid of the gray and make it regular hyperlink color with on-hover underline, please... or it should simply use the same styling as menu items (which, depending on the theme, typically use a very clearly contrasting background color on hover to indicate interactive status, instead of underline or subtle shades of grey) |
| | * Furthermore: | | * Furthermore: |
| | ** when left-clicking (instead of middle-clicking) a result, or selecting it then pressing the Enter key after choosing it with the up/down arrow keys, it does not trigger the """"visit the page"""" action... you have to press the Enter key a second time, which is quite unexpected behavior for a search field. Maybe not for a regular field, but for a search field, I would expect Enter or left-click to immediately trigger either the """"visit selected result"""" or """"run full search"""" action, like in other apps. | | ** when left-clicking (instead of middle-clicking) a result, or selecting it then pressing the Enter key after choosing it with the up/down arrow keys, it does not trigger the """"visit the page"""" action... you have to press the Enter key a second time, which is quite unexpected behavior for a search field. Maybe not for a regular field, but for a search field, I would expect Enter or left-click to immediately trigger either the """"visit selected result"""" or """"run full search"""" action, like in other apps. |
| | ** the """"visit page"""" action that gets triggered when pressing Enter twice is SLOW, it takes something like 2-3 seconds between the time you press Enter and the time the browser starts loading the page; if it's just visiting another page, why is it not instantaneous? | | ** the """"visit page"""" action that gets triggered when pressing Enter twice is SLOW, it takes something like 2-3 seconds between the time you press Enter and the time the browser starts loading the page; if it's just visiting another page, why is it not instantaneous? |
|
| 1 |
2022-08-10 17:57 |
Jeff Fortin T. |
54 |
Description |
| | This probably is a generic problem that ought to be fixed everywhere (?), but I'm reporting an annoyance of mine with """"what I can see right in front of me"""" here: | | This probably is a generic problem that ought to be fixed everywhere (?), but I'm reporting an annoyance of mine with """"what I can see right in front of me"""" here: |
| | * given how extensive the amount of wiki pages (and tickets) in the intranet, the """"Find"""" quick searchbar at the top-right of this website fails to fulfill its purpose for me because in the majority of cases I don't know which result I want to look at, so I want to look at multiple ones, but the autocompletion results do not properly hyperlink the items so I can't middle-click with the mouse to open various search results (selectively) in new tabs. | | * given how extensive the amount of wiki pages (and tickets) in the intranet, the """"Find"""" quick searchbar at the top-right of this website fails to fulfill its purpose for me because in the majority of cases I don't know which result I want to look at, so I want to look at multiple ones, but the autocompletion results do not properly hyperlink the items so I can't middle-click with the mouse to open various search results (selectively) in new tabs. |
| | + | ** When an autocompletion result line is clickable, it should have a hyperlink-style """"becomes underlined on mouse-over""""; this communicates the UI affordance easily, and is ''much'' better than the current hover styling which is way too subtle (text goes from gray to black). Please do not rely on subtle low-contrast color differences to convey hover status, get rid of the gray and make it regular hyperlink color with on-hover underline, please. |
| | * Furthermore: | | * Furthermore: |
| | ** when left-clicking (instead of middle-clicking) a result, or selecting it then pressing the Enter key after choosing it with the up/down arrow keys, it does not trigger the """"visit the page"""" action... you have to press the Enter key a second time, which is quite unexpected behavior for a search field. Maybe not for a regular field, but for a search field, I would expect Enter or left-click to immediately trigger either the """"visit selected result"""" or """"run full search"""" action, like in other apps. | | ** when left-clicking (instead of middle-clicking) a result, or selecting it then pressing the Enter key after choosing it with the up/down arrow keys, it does not trigger the """"visit the page"""" action... you have to press the Enter key a second time, which is quite unexpected behavior for a search field. Maybe not for a regular field, but for a search field, I would expect Enter or left-click to immediately trigger either the """"visit selected result"""" or """"run full search"""" action, like in other apps. |
| | ** the """"visit page"""" action that gets triggered when pressing Enter twice is SLOW, it takes something like 2-3 seconds between the time you press Enter and the time the browser starts loading the page; if it's just visiting another page, why is it not instantaneous? | | ** the """"visit page"""" action that gets triggered when pressing Enter twice is SLOW, it takes something like 2-3 seconds between the time you press Enter and the time the browser starts loading the page; if it's just visiting another page, why is it not instantaneous? |
|
| |
|
|
733 |
Emails |
|