2d5575ebd6047eff407005d0a69e5a6228b94b83: Bug 1622434 [wpt PR 22247] - Using WPT metadata to mark fetch.https.any.js test as slow., a=testonly
Lukasz Anforowicz <lukasza@chromium.org> - Sat, 14 Mar 2020 11:31:06 +0000 - rev 518874
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1622434 [wpt PR 22247] - Using WPT metadata to mark fetch.https.any.js test as slow., a=testonly Automatic update from web-platform-tests Using WPT metadata to mark fetch.https.any.js test as slow. This CL annotates cross-origin-resource-policy/fetch.https.any.js with: // META: timeout=long and removes [ Timeout ] expectations that this test has accumulated in blink/web_tests/TestExpectations over multiple sheriffing duties. Bug: 626703 Fixed: 1012599 Change-Id: Ia26c9200bc4182fb7fe51c98fd256079175c0801 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103074 Commit-Queue: Alex Moshchuk <alexmos@chromium.org> Auto-Submit: Łukasz Anforowicz <lukasza@chromium.org> Reviewed-by: Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#750320} -- wpt-commits: af71682c3fb9880458752eebc3f98aa2a708e8a9 wpt-pr: 22247
52841bab03e14c937c2ab4e53cc6667f190f5159: Bug 1622134 [wpt PR 22229] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 13 Mar 2020 20:58:30 +0000 - rev 518873
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1622134 [wpt PR 22229] - Update wpt metadata, a=testonly wpt-pr: 22229 wpt-type: metadata
1f0d7ace89f6a8f45b184380e27c675719973899: Bug 1622134 [wpt PR 22229] - WebXR - add WPTs for transient hit test API, a=testonly
Piotr Bialecki <bialpio@chromium.org> - Sat, 14 Mar 2020 11:30:59 +0000 - rev 518872
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1622134 [wpt PR 22229] - WebXR - add WPTs for transient hit test API, a=testonly Automatic update from web-platform-tests WebXR - add WPTs for transient hit test API Change-Id: I845e082ca413bcfa19a5ca4e06f587ebcb2cb254 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101713 Commit-Queue: Piotr Bialecki <bialpio@chromium.org> Reviewed-by: Alexander Cooper <alcooper@chromium.org> Cr-Commit-Position: refs/heads/master@{#750277} -- wpt-commits: 9610643196e6b5eb25b14c33016121290886dac2 wpt-pr: 22229
20e91f15a8e23b490defbba4469b5fbe28d5f16d: Bug 1621797 [wpt PR 22199] - WebOTP: Cleanup navigator.sms.receive(), a=testonly
Ayu Ishii <ayui@chromium.org> - Sat, 14 Mar 2020 11:30:54 +0000 - rev 518871
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1621797 [wpt PR 22199] - WebOTP: Cleanup navigator.sms.receive(), a=testonly Automatic update from web-platform-tests WebOTP: Cleanup navigator.sms.receive() This change removes the previous iteration of WebOTP, SMS Receiver API, which we ran for Origin Trial. This is now being removed in favor of the credential management version, WebOTP API [1]. WebOTP API Explainer: https://github.com/WICG/WebOTP I2E ending in M80: https://groups.google.com/a/chromium.org/d/topic/blink-dev/-bdqHhCyBwM/discussion Bug: 1045526 Change-Id: I1e73bed5018c814770fa34edcf64daafd234a543 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2097041 Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Victor Costan <pwnall@chromium.org> Commit-Queue: Ayu Ishii <ayui@chromium.org> Cr-Commit-Position: refs/heads/master@{#750226} -- wpt-commits: b6cf8f290e3d4053dbad33913473bc77532f0d89 wpt-pr: 22199
0fd57ef11ce69399a3d69d663001244956f77340: Bug 1622400 [wpt PR 22242] - Make LogicalHeightComputesAsNone check the override cb height, a=testonly
Christian Biesinger <cbiesinger@chromium.org> - Sat, 14 Mar 2020 11:30:49 +0000 - rev 518870
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1622400 [wpt PR 22242] - Make LogicalHeightComputesAsNone check the override cb height, a=testonly Automatic update from web-platform-tests Make LogicalHeightComputesAsNone check the override cb height If the override height is indefinite, this function should return true. This fixes the case of max-height: xx% on a replaced item in a flexbox, which otherwise would get resolved to 0 because resolving the percentage for replaced items would convert negative numbers to 0. Fixed: 1048051 Change-Id: I192e65b37a3670226fa764662448bdb4216c9fe1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2100771 Auto-Submit: Christian Biesinger <cbiesinger@chromium.org> Reviewed-by: David Grogan <dgrogan@chromium.org> Commit-Queue: Christian Biesinger <cbiesinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#750285} -- wpt-commits: 4c698c2c113d37c4a71f0bd0d1f32d631fa51a76 wpt-pr: 22242
2014080dbf937f7a20a88981ba0a90d535ec9308: Bug 1622419 [wpt PR 22246] - Revert "[ScrollTimeline] Support composited scroll-linked Web Animation", a=testonly
Alan Cutter <alancutter@chromium.org> - Sat, 14 Mar 2020 11:30:44 +0000 - rev 518869
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1622419 [wpt PR 22246] - Revert "[ScrollTimeline] Support composited scroll-linked Web Animation", a=testonly Automatic update from web-platform-tests Revert "[ScrollTimeline] Support composited scroll-linked Web Animation" This reverts commit 3254ad50926dbbd809cfa45b611d9081772ce7e8. Reason for revert: virtual/threaded/external/wpt/scroll-animations/two-animations-attach-to-same-scroll-timeline-cancel-one.html flaking on debug. https://ci.chromium.org/p/chromium/builders/ci/Linux%20Tests%20(dbg)(1)/87438 https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=blink_web_tests&tests=virtual%2Fthreaded%2Fexternal%2Fwpt%2Fscroll-animations%2Ftwo-animations-attach-to-same-scroll-timeline-cancel-one.html https://test-results.appspot.com/data/layout_results/Linux_Tests__dbg__1_/87463/blink_web_tests/layout-test-results/results.html Bug: 1060974 Original change's description: > [ScrollTimeline] Support composited scroll-linked Web Animation > > This patch integrates ScrollTimeline with cc::Animation. Major changes > include: > 1. blink::ScrollTimeline is able to create its compositor counterpart > 2. cc::ScrollTimeline is attached to cc::AnimationHost upon creation > 3. cc::AnimationHost ticks animations based on their timeline type > 4. Remove scroll_timeline_ from cc::WorkletAnimation and use the unified > animation_timeline_. > 5. Added virtual/threaded/external/wpt/scroll-animations/. > > See [1] for more details. > [1] https://docs.google.com/document/d/1RpJrYIDYHvtu0ia1vPv_EhBfan428QZ2sgsFhtnXb20/edit?usp=sharing > > To sheriffs: if any virtual tests become flaky, please add them to > TestExpectation instead of reverting the change. > > Bug: 1023508 > Change-Id: Ib4aa853bda34ce9b2c0abc943be9f99ac81e799a > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2084088 > Commit-Queue: Yi Gu <yigu@chromium.org> > Reviewed-by: David Bokan <bokan@chromium.org> > Reviewed-by: Majid Valipour <majidvp@chromium.org> > Cr-Commit-Position: refs/heads/master@{#749389} TBR=bokan@chromium.org,majidvp@chromium.org,yigu@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1023508 Change-Id: I15f5251d53f3d85936bb345acd00e9ead2f3e7e3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2100552 Reviewed-by: Alan Cutter <alancutter@chromium.org> Commit-Queue: Alan Cutter <alancutter@chromium.org> Cr-Commit-Position: refs/heads/master@{#750052} -- wpt-commits: f5d634dc5617cd639d24219b212461c186f9c23a wpt-pr: 22246
f321fd5d5975e1a05abf16718c543e4c9d1678ee: Bug 1622407 [wpt PR 6786] - Webidl legacy platform object tests, a=testonly
Tobie Langel <tobie@unlockopen.com> - Sat, 14 Mar 2020 11:30:39 +0000 - rev 518868
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1622407 [wpt PR 6786] - Webidl legacy platform object tests, a=testonly Automatic update from web-platform-tests Webidl legacy platform object tests (#6786) Co-authored-by: Tobie Langel <tobie@codespeaks.com> -- wpt-commits: 2f25e04b72f67b07001cb21a226f179342728f41 wpt-pr: 6786
976a2bd5b5b19b06acdab612bdbc8d68c43420ea: Bug 1621515 [wpt PR 22180] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 13 Mar 2020 21:43:36 +0000 - rev 518867
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1621515 [wpt PR 22180] - Update wpt metadata, a=testonly wpt-pr: 22180 wpt-type: metadata
af22de7403fdc9a55ae9d854eb1bd697ef40acf3: Bug 1621515 [wpt PR 22180] - [ScrollTimeline] Support composited scroll-linked Web Animation, a=testonly
Yi Gu <yigu@chromium.org> - Sat, 14 Mar 2020 11:30:31 +0000 - rev 518866
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1621515 [wpt PR 22180] - [ScrollTimeline] Support composited scroll-linked Web Animation, a=testonly Automatic update from web-platform-tests [ScrollTimeline] Support composited scroll-linked Web Animation This patch integrates ScrollTimeline with cc::Animation. Major changes include: 1. blink::ScrollTimeline is able to create its compositor counterpart 2. cc::ScrollTimeline is attached to cc::AnimationHost upon creation 3. cc::AnimationHost ticks animations based on their timeline type 4. Remove scroll_timeline_ from cc::WorkletAnimation and use the unified animation_timeline_. 5. Added virtual/threaded/external/wpt/scroll-animations/. See [1] for more details. [1] https://docs.google.com/document/d/1RpJrYIDYHvtu0ia1vPv_EhBfan428QZ2sgsFhtnXb20/edit?usp=sharing To sheriffs: if any virtual tests become flaky, please add them to TestExpectation instead of reverting the change. Bug: 1023508 Change-Id: Ib4aa853bda34ce9b2c0abc943be9f99ac81e799a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2084088 Commit-Queue: Yi Gu <yigu@chromium.org> Reviewed-by: David Bokan <bokan@chromium.org> Reviewed-by: Majid Valipour <majidvp@chromium.org> Cr-Commit-Position: refs/heads/master@{#749389} -- wpt-commits: 65dfaeccfa8044f290f22a13fd91fb0209cf50e1 wpt-pr: 22180
1520600a583881d5300bc8425e7ce472602a8686: Bug 1621725 [wpt PR 22195] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 13 Mar 2020 21:36:44 +0000 - rev 518865
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1621725 [wpt PR 22195] - Update wpt metadata, a=testonly wpt-pr: 22195 wpt-type: metadata
b7893b69cea5c05c66bb50d21ac0001e1e87b719: Bug 1621725 [wpt PR 22195] - Fix position:sticky when inside fixed subtree, a=testonly
David Bokan <bokan@chromium.org> - Sat, 14 Mar 2020 11:30:23 +0000 - rev 518864
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1621725 [wpt PR 22195] - Fix position:sticky when inside fixed subtree, a=testonly Automatic update from web-platform-tests Fix position:sticky when inside fixed subtree In https://crrev.com/4d25b125dae5 I changed the scroll tree parenting logic so that elements in position:fixed subtrees have the LayoutView's ScrollNode as the scroll parent. This made sense since scrolling over a fixed element should cause the document to scroll. However, this is slightly different from how the transform tree looks. Because scrolling the document doesn't cause position:fixed eement so translate, these nodes don't have the LayoutView's ScrollTranslation transform node as an ancestor. As a simple example, a scrolling document with a position:fixed <div> scroller will generate the following scroll and transform trees (approximately): *ScrollTree* *TransformTree* Root Root | | VisualViewport Translation VisualViewport | / \ LayoutView Translation / \ | Fixed LayoutView Fixed Scroller Translation The situation above makes sense for what parent-child relationships mean in each tree: the scroll tree encodes how scrolls chain; scrolling on a child should bubble up to its parent in this tree. The transform tree encodes the physical effect of scrolling a node. In the above example, scrolling from the fixed scroller should bubble up to the LayoutView (when the scroller is fully scrolled) but scrolling the LayoutView will not cause movement of the fixed scroller. The above makes sense but caused sticky code to get confused. A sticky constraint is attached to the scroll translation node. With the above situation, this meant that inside a fixed subtree, we'd attach it to the VisualViewport's scroll translation node. This was unexpected; the constraints are in "document coordinates", meaning that to translate them into the viewport space we must apply the scroll offset [1]. The compositor would use the visual viewport's (typically 0) scroll offset to adjust these values, leading to incorrect calculations. This previously worked because the scroll node used in a fixed subtree would be the visual viewport (before the CL mentioned at the top). In [2] we check whether the current overflow clip is also our scroller, prior to the CL this check have failed because "our scroller" was the visual viewport but our clip was the LayoutView. Now they are both the LayoutView. The fix in this CL is to make the check in [2] more stringent; we also want to make sure that our scroller is the nearest scroller in the transform tree. That is, if we scroll it, will we cause the current node to move? If not, we don't need a sticky constraint on the compositor because user scrolling can't change the sticky's offset relative to its clip. [1] https://cs.chromium.org/chromium/src/cc/trees/property_tree.cc?l=321&rcl=628f869d1fda631a85f051ad13b5d278319298fc [2] https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/paint/paint_property_tree_builder.cc?l=553&rcl=99a5a1266f303ba6ae46174a2b4cbd165ea7e934 Bug: 1019142 Change-Id: I781943ff43514905d399803c780c6081d7d47e8f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2097542 Reviewed-by: Robert Flack <flackr@chromium.org> Commit-Queue: David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#750264} -- wpt-commits: 1e6645ce41bc902a4c60d6f90a934f9d6d8a258a wpt-pr: 22195
c1ba1ca6ecd38b94c49c9c6304b4584943fa9406: Bug 1622035 [wpt PR 22221] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 13 Mar 2020 20:13:23 +0000 - rev 518863
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1622035 [wpt PR 22221] - Update wpt metadata, a=testonly wpt-pr: 22221 wpt-type: metadata
28d437391f6f15a4c7ad081b452e79fbc59b348b: Bug 1622035 [wpt PR 22221] - Migrate UnsizedMedia from feature policy to document policy, a=testonly
Charlie Hu <chenleihu@google.com> - Sat, 14 Mar 2020 11:30:15 +0000 - rev 518862
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1622035 [wpt PR 22221] - Migrate UnsizedMedia from feature policy to document policy, a=testonly Automatic update from web-platform-tests Migrate UnsizedMedia from feature policy to document policy This CL migrates UnsizedMedia from feature policy to document policy. Following web tests are being migrated: - unsized-media.tentative.https.sub.html - unsized-media-reporting.html Following web tests are removed, because document policy currently does not have a js API to list all features available. - feature-policy-unsized-media-disabled.html - feature-policy-unsized-media-enabled.html Bug: 993790 Change-Id: Id5e0189c0277c940177460380970eab0015109d0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2097028 Commit-Queue: Charlie Hu <chenleihu@google.com> Reviewed-by: Robert Sesek <rsesek@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Reviewed-by: Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#750246} -- wpt-commits: 550ab235e713dc584eb0e60ecc3861a11b644f02 wpt-pr: 22221
384a60fa440777dc5004970fc652af5fc7c1e95b: Bug 1622070 [wpt PR 22225] - Clamp sub-pixel borders accounting for zoom, a=testonly
Stephen Chenney <schenney@chromium.org> - Sat, 14 Mar 2020 11:30:10 +0000 - rev 518861
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1622070 [wpt PR 22225] - Clamp sub-pixel borders accounting for zoom, a=testonly Automatic update from web-platform-tests Clamp sub-pixel borders accounting for zoom A previous patch added clamping for sub-pixel borders to ensure they did not round to zero size. The change was done in paint code, leaving the borders as sub-pixel sized in layout. The code prior to that patch clamped the borders during style conversion but did not account for zoom, meaning borders disappeared under zoom. This change removes the clamping in paint and reverts to clamping in the style conversion code, only this time accounting for zoom when considering whether to clamp or not. This will prevent borders growing too large as content is made larger, while preventing sub-pixel borders from disappearing as content is made smaller. Design Doc: https://docs.google.com/document/d/1fAYkOFxp2Luh6OOoXxtwOehmvNRGNss58ibQtVXL0Tw/edit?usp=sharing Bug: 763402, 834489 Change-Id: Iba2ae80b0a981736b93453c1058fd586ba10212c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2097514 Commit-Queue: Stephen Chenney <schenney@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#750231} -- wpt-commits: 4b8af2e84553f4f1391a58251037ea1a4b152682 wpt-pr: 22225
f37f560e6540db8fc57a651d595becb686687af6: Bug 1621899 [wpt PR 22213] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 13 Mar 2020 21:21:23 +0000 - rev 518860
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1621899 [wpt PR 22213] - Update wpt metadata, a=testonly wpt-pr: 22213 wpt-type: metadata
e0db51ee811dc6abb6d0897bbbf56a8ed8fdb1f0: Bug 1621899 [wpt PR 22213] - Add tests for color-scheme and iframes., a=testonly
Rune Lillesveen <futhark@chromium.org> - Sat, 14 Mar 2020 11:30:02 +0000 - rev 518859
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1621899 [wpt PR 22213] - Add tests for color-scheme and iframes., a=testonly Automatic update from web-platform-tests Add tests for color-scheme and iframes. Iframes where the color-scheme of the iframe element and the iframe document's root does not match, will get a backdrop matching the color- scheme of the iframe's root element. Also adjust existing test according to spec change. See: https://github.com/w3c/csswg-drafts/issues/4772 Bug: 1058822 Change-Id: I82fd3cc3c2bbf5b4835b157a7522cb22c459ff20 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2095112 Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#750186} -- wpt-commits: 348adc5c7b2e3abb76763af063fbd921afb99ac5 wpt-pr: 22213
b2faa06cd912b3d9fdeae3e0ce1d4f03d8f88124: Bug 1620964 [wpt PR 22139] - Fix manifest writing in python3, a=testonly
Sergio <svillar@igalia.com> - Sat, 14 Mar 2020 11:29:57 +0000 - rev 518858
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1620964 [wpt PR 22139] - Fix manifest writing in python3, a=testonly Automatic update from web-platform-tests Fix manifest writing in python3 (#22139) Store more properties as text and convert to str for output. -- wpt-commits: d4cdf4021ab48c66b052fb62d91da1a06c8cbcf7 wpt-pr: 22139
3eb5aa166665294edba623b9ec502587b04f3763: Bug 1622072 [wpt PR 22226] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 13 Mar 2020 19:59:26 +0000 - rev 518857
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1622072 [wpt PR 22226] - Update wpt metadata, a=testonly wpt-pr: 22226 wpt-type: metadata
88b6c5710ce466879d3991f983b9d5397d60a222: Bug 1622072 [wpt PR 22226] - correct default expectation for existing mrow test, a=testonly
Brian Kardell <bkardell@gmail.com> - Sat, 14 Mar 2020 11:29:49 +0000 - rev 518856
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1622072 [wpt PR 22226] - correct default expectation for existing mrow test, a=testonly Automatic update from web-platform-tests correct default expectation for existing mrow test (#22226) * Update tabindex-001.html Attempting to match defaults defined in https://github.com/whatwg/html/pull/5248 definitely needs scrutiny.. * Update tabindex-001.html The default `.tabIndex` of an mrow should be 0 regardless of when it has an href or not, as a linkable element and matching historical (oddity) of other linkable things in HTML/SVG -- wpt-commits: 6b2fee71a825487369f34f82e7daa732920d186e wpt-pr: 22226
1109fcdb0f36a03cfe6d1b650f6bc244f9493dc0: Bug 1622229 [wpt PR 22236] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 13 Mar 2020 20:02:28 +0000 - rev 518855
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1622229 [wpt PR 22236] - Update wpt metadata, a=testonly wpt-pr: 22236 wpt-type: metadata
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip