Select to view content in your preferred language

Indicator numbers cutting off

5487
19
10-23-2020 08:44 AM
MikeSchonlau
Frequent Contributor

Is anyone else seeing this issue? I guess the simple solution is to shrink the font size, but I thought the font would auto-adjust to it's window??

indicator cutoff

19 Replies
TBWI
by
Occasional Contributor

Has anyone found a resolution to this issue? We are encountering it as well on our webpage. It cuts off the end and bottom of the indicator text upon initial webpage loading and resolves with refreshing. 

IonSola_Torralba
Occasional Contributor

Almost four years later this is still unresolved. Even if after refreshing the page the problem dissappears it is a HUGE aesthetic issue for users when they access the dashboard the first time. This should be a priority

EmilyAust1
Occasional Contributor

Seriously. What is going on, ESRI?

RoryMacGregor
Occasional Contributor

We also have this issue on all of our dashboards. It looks very amateur.

MarlboroughDistrict_Council
Frequent Contributor

All our dashboards do this too. Almost five years since this post was started and still no update ESRI?

KathrynWesson
Regular Contributor

I brought it up with @DavidNyenhuis1 at the Esri UC this past July. The devs are aware of the issue, and have tried multiple times to fix it, but it continues to revert back to doing this for some reason. They can't figure it out.

0 Kudos
MarlboroughDistrict_Council
Frequent Contributor

Thanks. Good to know ESRI are aware and have looked into this. Hopefully they find a fix one day!

0 Kudos
ZacharyVavra
Occasional Contributor

I've been experiencing the issue of content in Indicators not displaying properly for a long time. Something I noticed recently - the issue only appears to happen when using Firefox, but indicators appear fine when viewing the Dashboard in Chrome or Edge. Has anyone else notice this?

0 Kudos
TBWI
by
Occasional Contributor

We use Edge and still have this issue.

0 Kudos
KathrynWesson
Regular Contributor

I don't think it's a browser-specific problem, @ZacharyVavra. We use Chrome and still experience this issue. A quick F5 sorts it out temporarily, but my hope is that the development team can eventually address it on the backend for a permanent fix.