Skip to content
This repository has been archived by the owner on Oct 16, 2023. It is now read-only.

Investigate autocomplete operation selector #619

Closed
d47853 opened this issue Oct 23, 2018 · 6 comments
Closed

Investigate autocomplete operation selector #619

d47853 opened this issue Oct 23, 2018 · 6 comments
Assignees

Comments

@d47853
Copy link
Member

d47853 commented Oct 23, 2018

Sometimes (often after deleting an operation), the autocomplete comes up with a blank box (ie not displaying the operations and their descriptions).

@d47853 d47853 added this to the Backlog milestone Oct 23, 2018
@GCHQ-9182621 GCHQ-9182621 self-assigned this Feb 5, 2019
@g609bmsma
Copy link
Contributor

Hi, I've been having a look/investigate of this error and I can't seem to duplicate this error - the autocomplete box always has options in, no matter how many times I have deleted other operations in a chain. Are there any more details I could use to try and find the cause/circumstances?

@d47853
Copy link
Member Author

d47853 commented Feb 19, 2019

So I get it when I load in an operation from the "Previous queries" page, then highlight the select operation autocomplete field by clicking it and deleting the text.

@d47853
Copy link
Member Author

d47853 commented Feb 19, 2019

There's no errors in the logs and the options come back once text is inputted so it's not the end of the world - just a slight annoyance

@g609bmsma
Copy link
Contributor

Having done a bit of rooting around in other md-autocomplete issues, this one seems most like this issue:

Steps:

  1. Click md-autocomplete field
  2. Select any suggestion
  3. Click reset from the end of the field
  4. Click md-autocomplete field

Expected outcome:
I get list of suggestions like in the beginning.

Actual outcome:
Suggestions not showing up. I have to click outside md-autocomplete field and then click back inside the field to get suggestions."

This ended up being an issue with the version of Angular being used, and was an issue they had solved, as seen here.

Not a solution as yet, but definitely something related I think? Solution could be either to use a more up to date/different version of Angular, or maybe to look into their fix and find what was added and see if we can use it to fix our issue

@d47853
Copy link
Member Author

d47853 commented Feb 20, 2019

There's no reason we can't update

@n3101 n3101 modified the milestones: Backlog, v2_backlog Aug 25, 2021
@n3101 n3101 removed the p:low label Feb 15, 2022
@n3101
Copy link

n3101 commented Dec 6, 2022

The UI fails to meet our Accessibility policy. It is unmaintainable and will be removed shortly.

@n3101 n3101 closed this as completed Dec 6, 2022
@n3101 n3101 removed this from the post-v2.0_backlog milestone Dec 6, 2022
@n3101 n3101 closed this as not planned Won't fix, can't repro, duplicate, stale Dec 6, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants