PrimeDAO / prime-launch-dapp

https://launch.prime.xyz
6 stars 13 forks source link

Seed Dashboard: Cannot Read Token names inside tokenPrice div #292

Open BartuCulha opened 3 years ago

BartuCulha commented 3 years ago

Navigate here: https://primelaunchtest.primedao.io/seed/0x3E6cf7C98fB20e627752BD1739db89D40d629620

Tested this with Iphone 12 pro max on Safari. I was unable to see the token names.

However it is visible on other phones such as samsung s21, iphone X and lesser.

WhatsApp Image 2021-10-07 at 14 39 24 (3)

dkent600 commented 3 years ago

@BartuCulha I cannot tell where in the UI you are talking about.

BartuCulha commented 3 years ago

I am talking about the class called tokenPrice where the user sees how much funding tokens equals to project tokens (eg: 1 Prime = 10 DAO).

dkent600 commented 3 years ago

I see you mean where the UI has "= 10". Didn't catch that before.

BTW, we should always refer to the UI, not to the code, thanks!

BartuCulha commented 3 years ago

I agree with you but this certain element of the UI was a bit tough to explain since it doesn't have a text or a title above it. I thought it might be easier if I told you the class name. That being said, I'll not refer to the code in the future 👍

dkent600 commented 3 years ago

I agree with you but this certain element of the UI was a bit tough to explain since it doesn't have a text or a title above it. I thought it might be easier if I told you the class name.

screenshot works well, and you can if needed circle or point to an element on the screenshot itself. Thanks!

testing-life commented 2 years ago

for what it's worth, i've tried testing it with lambdatest and got this result on iphone8 image someone with access to an iphone should have a look at it, is my point :P

dkent600 commented 2 years ago

I can see on my iPhone the bug that Bartu reported

dkent600 commented 2 years ago

Recommend we wait until the stacks css issue is fixed before spending more time on this.

dkent600 commented 2 years ago

The stacks issue is fixed, so we should revisit this now.

dkent600 commented 2 years ago

THe bug is still there