Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debounce the register name field #126

Open
Cygnusfear opened this issue Apr 3, 2018 · 5 comments
Open

Debounce the register name field #126

Cygnusfear opened this issue Apr 3, 2018 · 5 comments
Assignees

Comments

@Cygnusfear
Copy link

Currently the register name field is almost unusable as it looks up every character change.

@Bradymck
Copy link

Thanks. Appreciate the issue submission.

@Bradymck
Copy link

@madvas We have a lot of new people using NB as of late. Can we assign this to someone and get this fixed soon?

The issue is on the 'Keyword' search field here: https://namebazaar.io/offerings

If you type a letter it unfocuses from the search field and you have to click on it for each letter you type.

@cpcdev8499
Copy link

I am having the same issue. It is very painful to use NameBazaar when it keeps locking up every letter you type and you have multiple domains to manage through the auction process.

If this issue can be fixed I would prefer NameBazaar over MEW.

One possible solution:

Instead of firing the search after each letter, set a timer delay to search only after the user has stopped typing for 1 second or so.

@cpcdev8499
Copy link

cpcdev8499 commented Jan 15, 2019

I wasnt able to reveal a handful of domains in time because of this issue. Between having to reload the page after each transaction and having it lock up randomly, etc... with all that I was only able to successfully reveal some of my bids in time.

Please fix the issue ... it is affecting the entire part of the registration... placing, revealing and finalizing bids are all affected. It seems like a critical bug to me..

@fbielejec fbielejec removed their assignment Jan 15, 2019
@danielglauser
Copy link
Contributor

@Cygnusfear @chasecattaneo Just deployed a fix to production. Please let me know if it addresses this issue and I can close it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants