AKASHAorg / akasha-core

Monorepo for the AKASHA core framework
https://akasha.world
GNU Affero General Public License v3.0
50 stars 11 forks source link

HTTML codes are appearing after accessing "Change Ethereum Name" UI. #850

Closed EPforAkasha closed 3 years ago

EPforAkasha commented 3 years ago

When the user accesses the "Change Ethereum Name" UI, a HTTML codes appears on the UI.

Steps to reproduce the behavior:

  1. On the Profile UI, click the "Edit Profile" button.
  2. Choose the "Change Ethereum name".
  3. Observe the UI.

Expected behavior: There no HTTML should appear after accessing the "Change Ethereum Name" UI.

Screenshot: HTTML_ChangeEthereumName

Desktop: Apple MacBook Air 13'2017

Smartphone:

Wallet Used

kenshyx commented 3 years ago

Hey @EPforAkasha , an important info for these issues is to specify which wallet was used.

EPforAkasha commented 3 years ago

Hi @kenshyx, we used Metamask when we encountered this issue.

kenshyx commented 3 years ago

Ok, to prevent any loss, change the Metamask wallet to be on Rinkeby network

kenshyx commented 3 years ago

Also specify if it was metamask mobile wallet or web extension, this helps us a lot, thx!

EPforAkasha commented 3 years ago

Noted on this @kenshyx!

EPforAkasha commented 3 years ago

The issue is also occurring when using Desktop Browsers Microsoft Edge and Google Chrome.

Used Wallet Web Extension: -Metamask -Nifty

Peripherals and Browsers Used: Desktop | OS Windows 10 pro Microsoft Edge Version 88.0.705.81 (Official build) (64-bit) Mac mini (Late 2012) | OS 10.15.6 Google Chrome Version 88.0.4324.192 (Official Build) (x86_64)

EP(JFF)

Screenshot: Web_Browser

SeverS commented 3 years ago

I think this one is fixed. The remaining issue (with the error message area and error text) will be addressed separately when we rework this modal. @kenshyx am I right?

kenshyx commented 3 years ago

Yes, we need now just a section to display the error message.

ggolcher commented 3 years ago

We will review the design tomorrow :)

kenshyx commented 3 years ago

this was fixed, reopen if it still happens