thirty seconds , you're right - this is due to the expansion of the fields. I was in a similar situation. However, you cannot say that this is only a FireFox error. In fact, in Chrome my fields were not used for collapse even without a float. In FireFox, on the other hand, the fields crashed for me, despite the broken float (with overflow: hidden / automatic, cleared element in between or something else). Funnily enough, the fields are crumbling between the child and the parent, which should not happen in accordance with the W3C specifications. Moreover, a positive addition fixed this problem.
As a conclusion, I can say that no browser complies with 100% W3C / IEEE / ISO standards. However, I don't care which browser complies with the exact standard. The important thing is that they all comply with the same standard. This does not happen, and I doubt it will ever be.
source share