I agree with Wesly.Zhang

@dmitriy-pisarets

Ok, glad to know that.

Let me wait till its final release and check the problem again, especially the localiazation problem....

if, I still remember it Half a year later.

@dmitriy-pisarets

Hi

Do you mean that right now we dont need to worry about it?

actually there is another situation that there are more than 99 days left that the space should be enough for three numbers.  Even four numbers.  Because users can buy 3 years of the product throwaway, so, 365x3=1095, four number need to display.

I believe the current design is that the reserved space is enough wide for three numbers.

but this design lacks flexibility, to display properly both 1 to 4 numbers. I do not know what is shows like in en-us, but not good in simplified chinese localiazation.

@jarvis

Both is ok, there is or there is no space between days and left.

but if there is extra space as designed to highlight the number, the number should be in the center of the empty space reserved in advance.

https://cloud.qainfo.ru/s/9lwfKNHcXYW2C45

as the screenshot shows

the number should be centered.

@wesly-zhang

you can try reproduce it.

use chrome and watch Huya. choose a hot room, like KPL, LPL.......

I know little about programming and those basic things.

@dmitriy-pisarets

Actually, I believe I can give you enough data but the difficulty is knowing what is really matter........

If I can though my laptop to your office, it would be much easiler.....

@wesly-zhang

I dont know

I do the test that disable those drivers. If klwtp is disabled, the problem is gone( of course once the driver is disabled, webAV is stoped). If you disable other driver, there is still the problem.

You may find the answer if you ask huang1111

 he do the test of disabling protections..... that is the first time we are requested by the tech support.

my driver test was the second time....tech support want more...

Frankly speaking, I believe that those tough and long barriers between dev and users cause the very long period which it takes to fix a localization problem.

Tech support always asking us provide tons of data again and again, after months, there still even no bug ID. Maybe, the problem is still not confirmed yet.........

Dont know what to do now.