[1] Smartcoin flag re-enables itself after cancelled 'save changes' login prompt?

[grctest]

Describe the bug
I attempted to permanently disable the "Allow issuer to force a global settling" permission within Hertz, but after completing the saved changes I noticed that the flag was still enabled..

I attempted the change again, and it re-enabled itself!

To Reproduce
Steps to reproduce the behavior:

1. Go to a bitasset's update page.
2. Go to the permissions.
3. Disable the "Allow issuer to force a global settling" permission.
4. Hit "Save Changes"
5. Cancel the password prompt.
6. Observe a ghost re-enabling the permission!

Expected behavior
The flag does not self-configure itself.

Screenshots

Desktop (please complete the following information):

• OS: Windows
• Browser: N/A - light client
• Version 180926

Additional context

Hopefully the reverse doesn't occur to someone..

[grctest]

Just attempted to disable this setting with the latest client release, paid the fee, tx '1.11.534986968' and it re-enabled itself after confirming the changes... Is this because the supply is greater than 0? I'd have expected a warning if that was the case.

[HarukaMa]

Maybe clicking save triggered UI refresh even though the wallet is not unlocked?

[grctest]

I attempted the change again, I first fully unlocked my wallet, changed a price feed publisher and attempted to permanently disable the flag, the transaction confirmation included the changes, I paid the fee and the flag re-enabled itself after confirmation.

[abitmore]

"the flag re-enabled itself" is just a UI display issue, right?

[clockworkgr]

"the flag re-enabled itself" is just a UI display issue, right?

i'd seriously hope so

[grctest]

@abitmore I've not attempted to remove the permission via the CLI or using a python script, solely using the Bitshares UI. I'm unable to remove the permission in the UI after multiple attempts.

[grctest]

Anyone experiencing this issue could workaround this by burning the asset-owner permissions, creating the same effect - effectively permanently disabling the "Allow issuer to force a global settling" permissions as there'd be no issuer capable of forcing the global settlement.

[sschiessl-bcp]

There was a bug in asset_utils that the flag global_settle was always set in UI.