Xidorn Quan dcd5c4908e Bug 1442521 - Make width/height attr on <window> mean the inner size in nsXULWindow. r=bz ... It seems that the layout system assumes those attributes are for size of the <window> element, i.e. inner window size, not outer window size. See for example nsContainerFrame::SyncWindowProperties. It reads {min,max}{width,height} attributes from the element via nsIFrame::GetXUL{Min,Max}Size, and passes them into SetSizeConstraints. The latter inflates the sizes with window decoration size before calling into widget code. It can also be seen that various XUL size related methods on nsBox and nsIFrame put the same assumption. The test test_windowminmaxsize.xul apparently puts the same assumption as the layout system on the meaning of those properties. (Another test test_resize_move_windows.xul, which tests effectiveness of features of window.open, also fails if we size the window earlier than current in bug 1439875, and doesn't fail with this patch on top. It may indicate that it makes use of the same assumption, but I can't really figure out how it does so.) MozReview-Commit-ID: IdMwDc59Ltg --HG-- extra : rebase_source : ae46c23e450f556cc4608b512890c4e27cf8623e		2018-03-02 22:42:57 +11:00
..
appshell	Bug 1442521 - Make width/height attr on <window> mean the inner size in nsXULWindow. r=bz	2018-03-02 22:42:57 +11:00
components	Bug 1425458 - Resource timing entries Workers - part 0 - NS_NewChannel, r=smaug	2018-01-24 17:17:31 +01:00