> Sören Hentzschel second the builds and pointed out that this time Intl.RelativeTimeFormat and Intl.DateTimeFormat were completed around that date.
To clarify since there was a little misunderstanding: I don't know if there is a relation between these APIs and the reported problem. I just wanted to clarify in the linked forum post that the fact that the relative timings in the earlier builds did not work _could_ mean that some parts of the used APIs were implemented in a later Firefox version (I have not checked that). I also have not debugged whether there is a relation between the non working relative timings in previous builds and the broken table selecting in later builds. I only confirmed that I got a change in the Firefox 74 timeframe as regressor and that mozregression was not able to bisect further.
Bug 1843725 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> Sören Hentzschel second the builds and pointed out that this time Intl.RelativeTimeFormat and Intl.DateTimeFormat were completed around that date.
To clarify since there was a little misunderstanding: I don't know if there is a relation between these APIs and the reported problem. I just wanted to clarify in the linked forum post that the fact that the relative timings in the earlier builds did not work _could_ mean that some parts of the used APIs were implemented in a later Firefox version (I have not checked that). I also have not debugged whether there is a relation between the non working relative timings in previous builds and the broken table selecting in later builds. I only confirmed that I also got a change in the Firefox 74 timeframe as regressor and that mozregression was not able to bisect further.