We had to disable some tests recently for other reasons and it looks like we never updated our internal tests to isolate tests for AL custom dates separately.
What I believe is the source of the bug: There was recently a bug where interacting with a hidden (show if, I believe) date field blocked the field just below. We then started skipping hidden fields to avoid the bug. Unfortunately, the way we interact with the ThreePartsDate/BirthDate fields is through their hidden field because of complications in trying to get it to otherwise submit the final value.
We'll have to find another solution to one of those problems.
[We may have an additional problem on top of that one. Not sure what it is yet. Something's not being filled in.]
We had to disable some tests recently for other reasons and it looks like we never updated our internal tests to isolate tests for AL custom dates separately.
What I believe is the source of the bug: There was recently a bug where interacting with a hidden (show if, I believe) date field blocked the field just below. We then started skipping hidden fields to avoid the bug. Unfortunately, the way we interact with the
ThreePartsDate/BirthDatefields is through their hidden field because of complications in trying to get it to otherwise submit the final value.We'll have to find another solution to one of those problems.
[We may have an additional problem on top of that one. Not sure what it is yet. Something's not being filled in.]