Input Number Missing Value Text (non-LL)

[mynameisdaniel32]

Home Assistant release with the issue:
0.79.3 -> 0.80.0b5

Last working Home Assistant release (if known):
0.78.X

Browser and Operating System:
Browsers (on Windows 10):
Opera 56.0.3051.43
Chrome 69.0.3497.100
Firefox 62.0.3
Multiple Home Assistant installation methods affected (venv on Debian for me)

Description of problem:
For input number (box and slider) the actual value is missing. See home-assistant/core#16957 for more examples/info. This doesn't seem to be affecting Lovelace. Column width does not affect this, even with columns as wide as they go, the numbers do not display.

Javascript errors shown in the web inspector (if applicable):

Additional information:

[balloob]

it shows/hides depending on the width of the card

[pplucky]

it shows/hides depending on the width of the card

Issue 1: Slider labels seem to have disappeared for all cards... Any way of forcing to always appear?

Issue 2: Boxes don't appear at all

How it should appear:

How it appears:

[balloob]

Please fill in browser in issue template.

Forcing showing it will not happen.

[pplucky]

@balloob: but isn’t it strange that it worked perfectly (label visible) before updating and it doesn’t anymore after? Is this a new “functionality”?

[yunnanpl]

I have the same issue, and it seems that it was mentioned in numerous places:
home-assistant/core#9779
home-assistant/core#16957
and here.

I did some digging, and it seems that I solved the issue. I posted the answer here:
home-assistant/core#9779 (comment)

[mynameisdaniel32]

I've updated the original post with browser details and to show that this occurs even with columns at their native width.

[mynameisdaniel32]

This is still an issue as of 0.81.0b2 😢

[iantrich]

This should be resolved in final 0.81: #1861

[perozonp]

Should? I just upgraded to 0.81 and I still have this issue (Lovelace is not having it).

[perozonp]

hmmm... I'm having the issue in my android phone, but is not showing in my windows laptop (chrome). I'll do some additional test later...

[iantrich]

caching? Using the phone emulation view on Chrome shows it still. I only have dev instance up right now so can't really truly look on a phone.

[perozonp]

Not sure what happened, probably caching. My phone is ok now, input_numbers look fine. Thanks!

[Martin73Mac]

Still present on Android Chrome and native Android application.