mirror of
https://github.com/mozilla/gecko-dev.git
synced 2025-03-04 07:40:42 +00:00

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
Bug 1436287 - Disable high-frequency intermittent failure until the proper fix is in place. r=botond
servo: Merge #20222 - Do not disable thread pool in the parent process (from upsuper:chrome-thread-pool); r=bholley
…
…
…
…
…
An explanation of the Mozilla Source Code Directory Structure and links to project pages with documentation can be found at: https://developer.mozilla.org/en/Mozilla_Source_Code_Directory_Structure For information on how to build Mozilla from the source code, see: https://developer.mozilla.org/en/docs/Build_Documentation To have your bug fix / feature added to Mozilla, you should create a patch and submit it to Bugzilla (https://bugzilla.mozilla.org). Instructions are at: https://developer.mozilla.org/en/docs/Creating_a_patch https://developer.mozilla.org/en/docs/Getting_your_patch_in_the_tree If you have a question about developing Mozilla, and can't find the solution on https://developer.mozilla.org, you can try asking your question in a mozilla.* Usenet group, or on IRC at irc.mozilla.org. [The Mozilla news groups are accessible on Google Groups, or news.mozilla.org with a NNTP reader.] You can download nightly development builds from the Mozilla FTP server. Keep in mind that nightly builds, which are used by Mozilla developers for testing, may be buggy. Firefox nightlies, for example, can be found at: https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/ - or - https://nightly.mozilla.org/
Description
Read-only Git mirror of the Mercurial gecko repositories at https://hg.mozilla.org. How to contribute: https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html
Languages
JavaScript
32.3%
C++
25.4%
HTML
21.1%
C
10.8%
Python
2.8%
Other
7.1%