Tristate buffers repeatedly set output if disabled

[PeanutbutterWarrior]

Describe the bug
When the enable pin of the tristate buffer is grounded, not passing through the input, it will cause a Simulation Stack Limit Exceeded error if the output is connected to the input.

To Reproduce
Steps to reproduce the behavior:

1. Create circuit as shown below
   
2. Connect A to B
3. See error

Expected behavior
As the input is not passed through, and the output does not rely on the input, it should not cause a cycle.

Device Information [optional]:

• OS: Windows 10
• Browser: Firefox 99.0 (64 bit)

Additional context
This can be worked around by including another gate in the path, as seen below:

After looking at the code, the tristate will set the output to undefined if it is not already. I suspect that the input element sets the output to a defined value repeatedly, so the tristate sets it to undefined repeatedly. I have been unable to find how signals are propagated, so am unable to check this.

Are you working on this issue? No