mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-11-25 05:41:12 +00:00
a3949a5f7a
Basically, the transferred min & max sizes shouldn't override the min & max sizing properties, so applying it earlier than these properties should be identical. This just makes the flex base size and main size be more correct at the beginning (and so other adjustments of sizes in flex algorithm can override the transferred min/max sizes), for non-replaced elements. Note: In Chromium code, it clamps the flex items' base size by transferred min & max sizes, but the computation of items' used min & used max sizes doesn't include the transferred min & max sizes. So in this patch, I'm trying to make this patch simple: we let minimum & maximum sizes only taken into account for flex base size and only for non-replaced elements for now. So the behavior should be similar to other browsers. And we may have to update this tentative solution once these spec words get updated. Differential Revision: https://phabricator.services.mozilla.com/D144499 |
||
|---|---|---|
| .. | ||
| awsy | ||
| condprofile | ||
| config | ||
| crashtest | ||
| docs | ||
| extensions | ||
| firefox-ui | ||
| fxrecord/perfdocs | ||
| geckodriver | ||
| gtest | ||
| jsshell | ||
| marionette | ||
| mochitest | ||
| modules | ||
| mozbase | ||
| mozharness | ||
| perfdocs | ||
| performance | ||
| profiles | ||
| raptor | ||
| runtimes | ||
| specialpowers | ||
| talos | ||
| tools | ||
| tps | ||
| web-platform | ||
| webcompat | ||
| webdriver | ||
| xpcshell | ||
| addtest.py | ||
| cppunittest.ini | ||
| mach_commands.py | ||
| moz.build | ||
| parse_build_tests_ccov.py | ||
| README.txt | ||
| remotecppunittests.py | ||
| runcppunittests.py | ||
| testinfo.py | ||
| testsuite-targets.mk | ||
Common testing tools for mozilla codebase projects, test suite definitions for automated test runs, tests that don't fit anywhere else, and other fun stuff