<p></p>
<blockquote>
<p>One solution here is to have a publish button on the notification dialog. So when they get the notification they can publish with just one click(one click so all offers get published before mining fee changes).</p>
</blockquote>
<p>I'm personally against an auto-publishing as we have the two confirmation steps in place by intent. So as a first version I would go for publishing the offers one after the other. It is just two buttons presses anyways and after one got published the next one should be opened to confirm automatically. Changing this behavior would touch lots of trading related code and probably is too much risk for a first iteration.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/bisq/issues/5282#issuecomment-796565738">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNW4ED7EFPTDLT2SKRLTDB6GHANCNFSM4YXCEHZA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNSPZZTVQ6E65SM7JADTDB6GHA5CNFSM4YXCEHZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOF55KB2Q.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/bisq/issues/5282#issuecomment-796565738",
"url": "https://github.com/bisq-network/bisq/issues/5282#issuecomment-796565738",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>