Statistics bar graph suddenly dripping water ;-)

Is this something new in HA?
Since today I am seeing this on my Energy usage bar chart, and also on my statistics bar chart for my water usage:


HA_waterverbruik_20230802-1138

It is raining a lot in my area for the last days, but I would think that this is not caused by that :wink:
Is anybody else seeing this as well?

Which web browser and which core version of HA?

It’s Firefox version 116.0 and HA is:
Home Assistant 2023.7.3
Supervisor 2023.07.1
Frontend 20230705.1 - latest

Very strange. I’m using the same browser and versions and do not see this.

This is what is shown in the Firefox Inspector:


I suppose it is not due to this style="overflow" :wink:

I did some more checks:
A restart of Firefox and a reboot of my PC did not change anything, and it is only shown in Firefox and not in Edge.

Another update on this issue: it happens on two laptops with Firefox 116.0 as well (all on Windows 10).
But on another Windows 10 PC with still an older version Firefox (114.0.2) it did not happen until after I updated to Firefox 116.0
So it is at least related to Firefox 116.0 on Windows 10.
Is nobody else seeing this?

I wasn’t actually on the latest version of ff. Now I am I see it:

I opened a frontend issue.

Looks like it is rendering the wrong segment of the top left hand corner radius. Instead of drawing radius from 9 o’clock to 12 o’clock it is rendering from 12 to 9.

Right!
Thanks.
However, I must say I don’t dislike it, especially for my water usage chart :wink:

Hi all,
i woke up this morning with the same graphic glitch.
Had 2023.7 (.2 i think…) this morning and updated to 2023.08 with no effect before start googling. RPi3 on external SSD with docker.
It’s strange because it worked with no problems, no reboots or whatever since the last version update.
The issue seems to be present only in Firefox. It’s not present on Chrome on the same pc or on the phone (android)

It appeared to be a bug in Firefox version 116.0 incorrectly rendering some chart elements, and is resolved with an update to Firefox version 116.0.1
See the bug report and release notes.

1 Like

When the bug appeared afer updatng firefox o 116.0, I sent a report to the mozilla support forum. I had no feedback. Maybe firefox devs finally read the forum after all :slight_smile:

And yes, the update fixed the issue.