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
ui: correct match status for revoked matches #1772
Conversation
@martonp In toying with this issue, it looked like |
Oh, A related issue I noticed is that self revokes like:
get retired sometimes before the server revoke that triggers proper revoke handling. So if you try to look at these retired orders and matches they don't look revoked. When you restart dexc they seem to get reconciled again and they look proper. Going to switch gears for now. |
Just observed this when testing Decrediton update for v0.5 (not including this PR), where the two redeem txids get written the same: Having the order page open while a swap is settling where you are both sides highlights some of these issues. I think this one is also resolved by the order ID filter in this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also resolves #1760 for me.
this.order = order | ||
const bttn = page.cancelBttn | ||
if (bttn && order.id === this.orderID) { | ||
if (bttn && order.status > OrderUtil.StatusBooked) Doc.hide(bttn) | ||
page.status.textContent = OrderUtil.statusString(order) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know why this line would be conditional on bttn
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because we're omitting the element in the Go template instead of using class="d-hide"
. It's a silly way to do it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, so page.status
doesn't exist unless page.cancelBttn
exists too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<div class="order-datum">
<div>[[[Status]]]</div>
<div>
<span id="status">{{$ord.StatusString}}</span>
{{if $ord.Cancelable}}
<span id="cancelBttn" class="ico-cross fs12 ms-1 pointer hoverbg" data-tooltip="cancel order"></span>
{{end}
Looks like page.status
would be there even if page.cancelBttn
is not.
To be clear, I was calling out the line page.status.textContent = OrderUtil.statusString(order)
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wasn't commenting on why setting the status string was inside of the bttn conditional. Not sure on that, tbh.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gotcha. I highlighted too many lines with the github comment. The page.status
condition must have been an error.
ceb25aa
to
89ae96c
Compare
Resolves #1769