| Summary: | Cannot write directly to the Component picker | ||
|---|---|---|---|
| Product: | [Community] Bugzilla | Reporter: | Milan Crha <mcrha> |
| Component: | Creating/Changing Bugs | Assignee: | PnT DevOps Devs <hss-ied-bugs> |
| Status: | CLOSED WONTFIX | QA Contact: | tools-bugs <tools-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 4.5 | CC: | huiwang, mtahir, qgong |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-01-30 05:55:53 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Milan Crha
2016-01-19 16:42:11 UTC
The selectize widget [1] has a plugin "restore_on_backspace" which does the "backspace == edit what's there" behavior. I'm not sure if we should default that on or make it a user preference, I'll chat with the team about that. 1: http://selectize.github.io/selectize.js/ The speed issue is something we are looking in to. It saves a similar time on page load so the net effect across all users is a positive. The widget does cache search results but of course the first search has an empty cache. We could add a user option to preload the component list and not use ajax, but then you will pay the load time for that every time you load a bug, even if you aren't going to change the component. The component list is large and has a noticeable affect on page load times. I think a lot of people would get miffed if we auto selected from the list if there was only one match. People make typos and it'd be very annoying if it auto selected a typo and you had to delete it and type again. We could probably make a user preference to do this if you really want it. There doesn't look to be an upstream plugin for this so we'd have to write our own. I think we should address issue 1 in this bug and if you are still keen on having 2 and 3 addressed please open separate bugs for each of them. In preparation for entering maintenance mode we are closing bugs that are unlikely to be scheduled in maintenance sprints. |