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

Validation issues while creating buy/sell offer #3866

Open
beingindot opened this issue Jan 7, 2020 · 3 comments
Open

Validation issues while creating buy/sell offer #3866

beingindot opened this issue Jan 7, 2020 · 3 comments

Comments

@beingindot
Copy link
Contributor

Description

Validation error is not properly showing when next step button not enabled.

Version

1.2.5

Steps to reproduce

  1. create buy offer
  2. try to fill fields using newly created account (used chasequickpay)
  3. select seeded account which has more buy limit
  4. fill 0.1 btc and 2000 usd then see that next button not enabled
  5. note that no validation errors

Expected behaviour

validation errors should be there

Actual behaviour

validation errors not present

Screenshots

Screenshot from 2020-01-07 12-44-25

Device or machine

Additional info

may be this replicates in sell offer too.

@niyid
Copy link
Contributor

niyid commented Feb 3, 2020

@beingindot
Hi. Can I have access to your logs? You can try this again and send the most recent logs to make it easy to pinpoint where it went wrong.

Regards.

@ripcurlx
Copy link
Contributor

ripcurlx commented Feb 5, 2020

@beingindot
Hi. Can I have access to your logs? You can try this again and send the most recent logs to make it easy to pinpoint where it went wrong.

Regards.

Logs won't help to fix this issue. There is no logging for focus events by default.

@niyid
Copy link
Contributor

niyid commented Feb 5, 2020

@beingindot
Hi. Can I have access to your logs? You can try this again and send the most recent logs to make it easy to pinpoint where it went wrong.
Regards.

Logs won't help to fix this issue. There is no logging for focus events by default.

That is fine. There may be other information in the logs apart from the actual event which was supposed to fire.

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

No branches or pull requests

3 participants