Not sure if this is a bug or not, but it's a behavior-difference with WebKit at least, so I figured I'd file to at least have a place to post a testcase and potentially hash things out. STR: 1. Load attached testcase. ACTUAL RESULTS: The reported height is `0` MAYBE-EXPECTED RESULTS: Maybe the reported height should be 300? That's what we get if I remove `display:none` at least. Firefox and Chrome both give ACTUAL RESULTS. WebKit gives MAYBE-EXPECTED RESULTS. This came across my radar because twisniewski noticed https://github.com/WebKit/WebKit/commit/7d4f344fa9a70f3b92972faeaf1352c03d384b74 which is an optimization to this WebKit behavior (though the behavior predates that commit, if I'm understanding correctly) In particular, the first few lines of that commit (from webkit committer alanbaradlay): > 1. we do _not_ construct renderers for “display: none” iframes > 2. we do construct render tree for the “display: none” iframe’s content > > we do #2 because JS may ask for geometry information on content inside a “display: none” iframe. Firefox/Chrome do not do #2 as far as I know. I don't know for sure if any sites happen to break as a result of that.
Bug 1883997 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Not sure if this is a bug or not, but it's a behavior-difference with WebKit at least, so I figured I'd file to at least have a place to post a testcase and potentially hash things out. STR: 1. Load attached testcase. ACTUAL RESULTS: The reported height is `0` MAYBE-EXPECTED RESULTS: Maybe the reported height should be 300? That's the height that the element is styled to have, and it's what we get if I remove `display:none` at least. Firefox and Chrome both give ACTUAL RESULTS. WebKit gives MAYBE-EXPECTED RESULTS. This came across my radar because twisniewski noticed https://github.com/WebKit/WebKit/commit/7d4f344fa9a70f3b92972faeaf1352c03d384b74 which is an optimization to this WebKit behavior (though the behavior predates that commit, if I'm understanding correctly) In particular, the first few lines of that commit (from webkit committer alanbaradlay): > 1. we do _not_ construct renderers for “display: none” iframes > 2. we do construct render tree for the “display: none” iframe’s content > > we do #2 because JS may ask for geometry information on content inside a “display: none” iframe. Firefox/Chrome do not do #2 as far as I know. I don't know for sure if any sites happen to break as a result of that.