Bugzilla

(as background: this particular Firefox behavior is the root problem in bug 1446442 that was causing trouble there, when we had `moz-document` parsing turned off in Nightlies for a little while.  For whatever reason, ansible's docs (the affected pages there) had a pattern similar to the one in my testcase here -- they had `td` elements that were effectively styled with `height:1px` (technically inheriting the `1px` from the `tr`); and then with the `td` containing a `height:100%` div; and Firefox was dutifully resolving the cell and the div to be 1px tall. Ansible had a `-moz-document` based CSS workaround to avoid the Firefox behavior here, which we stopped parsing for a little while as we explored removing that proprietary CSS token (hence bug 1446442 being filed), but the issue went away when we started passing their workaround again, per bug 1446442 comment 21.

(as background: this particular Firefox behavior is the root problem in bug 1446442 that was causing trouble there, when we had `moz-document` parsing turned off in Nightlies for a little while.  For whatever reason, ansible's docs (the affected pages there) had a pattern similar to the one in my testcase here -- they had `td` elements that were effectively styled with `height:1px` (technically inheriting the `1px` from the `tr`); and then with the `td` containing a `div` with `height:100%`; and Firefox was dutifully resolving the cell and the div to be 1px tall, though in fact their layout required both the `td` and the `div` to be content-sized. Ansible had a `-moz-document` based CSS workaround to avoid the Firefox behavior here, which we stopped parsing for a little while as we explored removing that proprietary CSS token (hence bug 1446442 being filed), but the issue went away when we started passing their workaround again, per bug 1446442 comment 21.

(as background: this particular Firefox behavior is the root problem in bug 1446442 that was causing trouble there, when we had `moz-document` parsing turned off in Nightlies for a little while.  For whatever reason, ansible's docs (the affected pages there) had a pattern similar to the one in my testcase here -- they had `td` elements that were effectively styled with `height:1px` (technically inheriting the `1px` from the `tr`); and then with the `td` containing a `div` with `height:100%`; and Firefox was dutifully resolving the cell and the div to be 1px tall, though in fact their design required both the `td` and the `div` to be content-sized, which is the layout that Chrome and WebKit ended up giving. Ansible had a `-moz-document` based CSS workaround to avoid the Firefox behavior here, which we stopped parsing for a little while as we explored removing that proprietary CSS token (hence bug 1446442 being filed), but the issue went away when we started passing their workaround again, per bug 1446442 comment 21.

(as background: this particular Firefox behavior is the root problem in bug 1446442 that was causing trouble there, when we had `moz-document` parsing turned off in Nightlies for a little while.  For whatever reason, ansible's docs (the affected pages there) had a pattern similar to the one in my testcase here -- they had `td` elements that were effectively styled with `height:1px` (technically inheriting the `1px` from the `tr`); and then with the `td` containing a `div` with `height:100%`; and Firefox was dutifully resolving the cell and the div to be 1px tall, though in fact their design required both the `td` and the `div` to be content-sized, which is the layout that Chrome and WebKit ended up giving. Ansible had a `-moz-document` based CSS workaround to avoid the Firefox behavior here to get the content-based sizing that they really wanted; and we stopped parsing that workaround for a little while as we explored removing that proprietary CSS token (hence bug 1446442 being filed), which is when this behavior-difference started causing trouble there; but the issue went away when we started passing their workaround again, per bug 1446442 comment 21.

(as background: this particular Firefox behavior is the root problem in bug 1446442 that was causing trouble there, when we had `moz-document` parsing turned off in Nightlies for a little while.  For whatever reason, ansible's docs (the affected pages there) had a pattern similar to the one in my testcase here -- they had `td` elements that were effectively styled with `height:1px` (technically inheriting the `1px` from the `tr`); and then with the `td` containing a `div` with `height:100%`; and Firefox was dutifully resolving the cell and the div to be 1px tall, though in fact their design required both the `td` and the `div` to be content-sized, which is the layout that Chrome and WebKit ended up giving. Ansible had a `-moz-document` based CSS workaround to avoid the Firefox behavior here to get the content-based sizing that they really wanted; and we stopped parsing that workaround for a little while as we explored removing that proprietary CSS token (hence bug 1446442 being filed), which is when this behavior-difference started causing trouble there; but the issue went away when we started passing their workaround again, per bug 1446442 comment 21.)