I think it is not an issue.

The textTpl is used to calculate the needed addtimedisplayWidth to show the addtimedisplay-Text.

With "00:00 - 00:000" you can set the max. of width for all values (begin - end time) to get the best calculated needed width.

Perhaps the width was sometimes to small, so the textTpl was added by a next 0.

Have you tested your changes to "00:00 - 00:00" ?

I think not

If i change the textTpl to "00:00 - 00:00" the width for the time-text is to small.

(screenshots from Default-FHD skin)

Calculate with fix width like 180 is not a good idea, because this value is not equal in all skin resolutions and fonts.

So the developer has use the "00:00 - 00:000" as a solution and it is not an issue.

You don't have to frantically look for another solution, because the code works.

Its not a bug, its a feature.

This code is using since 9 years and i have not heard, that this has a problem in using the box.

You must not search for all "errors", which not really are errors.

A real error is, when i have problems in using the box.