[FragmentItem] Use same logic for storing inkoverflow in outsets vs. ptr
Previously we used slightly different logic for storing ink-overflow in the compressed "outsets" format, and the "NGSingleInkOverflow" object format. This resulted in differences in when running a 64bit binary (typical) vs. a 32bit binary with large ink-overflows (which are relative uncommon). This patch changes the "NGSingleInkOverflow" to have the same outset logic. Change-Id: If9d5146ec3fad1de27cfda2c13980312886b1e79 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2304143Reviewed-by:Koji Ishii <kojii@chromium.org> Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#789669}
Showing
Please register or sign in to comment