mfbt/STYLE
author Morten Stenshorne <mstensho@chromium.org>
Tue, 09 Oct 2018 04:14:13 +0000
changeset 495959 13844f50ee32e17f513b7c1013c2348200e21b8c
parent 378420 89b895c219f2b97fc0ded8877b30c337e697bdaa
child 556830 0fd41e9dbd2a56e544d6b836e066fbbbd9f78b84
permissions -rw-r--r--
Bug 1496274 [wpt PR 13345] - [LayoutNG] Correct clip-path reference box calculation., a=testonly Automatic update from web-platform-tests[LayoutNG] Correct clip-path reference box calculation. We used coordinates relatively to the line box, while we were expected by the caller to be relative to the containing block. Flipping for writing mode was bogus for NG (but needed by legacy), since NG uses truly physical coordinates. Hardened tests to contain a leading line and padding, and leading content on the first line of the clipped child. Bug: 641907 Change-Id: I2b1b9ff4ea92a6405fcdffcf139842458b46442f Cq-Include-Trybots: luci.chromium.try​:linux_layout_tests_layout_ng Reviewed-on: https://chromium-review.googlesource.com/c/1257913 Reviewed-by: Koji Ishii <kojii@chromium.org> Reviewed-by: Fredrik Söderquist <fs@opera.com> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#596554} -- wpt-commits: e9a0828c85819340f721f121aac19ab8eefa3439 wpt-pr: 13345

MFBT uses standard Mozilla style, with the following exceptions.

- Some of the files use a lower-case letter at the start of function names.
  This is because MFBT used to use a different style, and was later converted
  to standard Mozilla style. These functions have not been changed to use an
  upper-case letter because it would cause a lot of churn in other parts of the
  codebase. However, new files should follow standard Mozilla style and use an
  upper-case letter at the start of function names.

- Imported third-party code (such as decimal/*, double-conversion/source/*, and
  lz4*) remains in its original style.