1b3006e52e6e6665837c25e50932ff18cc5cfbd0: Bug 1672035 [wpt PR 26164] - Update interfaces/screen-orientation.idl, a=testonly
autofoolip <auto@foolip.org> - Sat, 24 Oct 2020 10:37:29 +0000 - rev 554410
Push 37894 by dluca@mozilla.com at Tue, 27 Oct 2020 04:41:26 +0000
Bug 1672035 [wpt PR 26164] - Update interfaces/screen-orientation.idl, a=testonly Automatic update from web-platform-tests Update interfaces/screen-orientation.idl (#26164) Source: https://github.com/w3c/webref/blob/38e9fdf/ed/idl/screen-orientation.idl Build: https://travis-ci.org/w3c/webref/builds/190892914 -- wpt-commits: 4e501c19a3ecb6a3c675549bdec54b97bc95fe26 wpt-pr: 26164
b594684bbb8ae98b66435ce8e76e7ff30c0697cd: Bug 1672034 [wpt PR 26163] - Update interfaces/pointerlock.idl, a=testonly
autofoolip <auto@foolip.org> - Sat, 24 Oct 2020 10:37:27 +0000 - rev 554409
Push 37894 by dluca@mozilla.com at Tue, 27 Oct 2020 04:41:26 +0000
Bug 1672034 [wpt PR 26163] - Update interfaces/pointerlock.idl, a=testonly Automatic update from web-platform-tests Update interfaces/pointerlock.idl (#26163) Source: https://github.com/w3c/webref/blob/38e9fdf/ed/idl/pointerlock.idl Build: https://travis-ci.org/w3c/webref/builds/190892914 -- wpt-commits: d0c9044f6ab9ad23679cd977470aeb32378d6274 wpt-pr: 26163
ba7c315a87458b064c94c4c37a588b84982a2e5a: Bug 1672033 [wpt PR 26140] - webrtc: add wpt to test unbundled payload type demuxing, a=testonly
Philipp Hancke <philipp.hancke@googlemail.com> - Sat, 24 Oct 2020 10:37:23 +0000 - rev 554408
Push 37894 by dluca@mozilla.com at Tue, 27 Oct 2020 04:41:26 +0000
Bug 1672033 [wpt PR 26140] - webrtc: add wpt to test unbundled payload type demuxing, a=testonly Automatic update from web-platform-tests webrtc: add wpt to test unbundled payload type demuxing BUG=chromium:1139052 Change-Id: I7c6449b6569251ac6b2320da5a373f637dd4be00 -- wpt-commits: 3859c75eb9c25ce3031dc117aec1f2aa6876c8db wpt-pr: 26140
e6cf9d673b9e42a54827e8d4333a86b34b2cbca5: Bug 1672032 [wpt PR 26150] - [:is/:where] Make is-where-error-recovery.html non-tentative, a=testonly
Anders Hartvoll Ruud <andruud@chromium.org> - Sat, 24 Oct 2020 10:37:20 +0000 - rev 554407
Push 37894 by dluca@mozilla.com at Tue, 27 Oct 2020 04:41:26 +0000
Bug 1672032 [wpt PR 26150] - [:is/:where] Make is-where-error-recovery.html non-tentative, a=testonly Automatic update from web-platform-tests [:is/:where] Make is-where-error-recovery.html non-tentative It's now in the spec, so it should be fair to remove the .tentative tag. Bug: 568705 Change-Id: I527632906e49f6d4f9909c75750acbc6e5e91c82 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2479364 Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by: Emilio Cobos Álvarez <emilio@chromium.org> Cr-Commit-Position: refs/heads/master@{#818401} -- wpt-commits: ab1f90a9e866ec7d479c17eafc05df4380159ee2 wpt-pr: 26150
8a4a3fa6346919b9d84fe04cab7d9156f1062ceb: Bug 1670225 [wpt PR 26064] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 19 Oct 2020 19:59:37 +0000 - rev 554406
Push 37894 by dluca@mozilla.com at Tue, 27 Oct 2020 04:41:26 +0000
Bug 1670225 [wpt PR 26064] - Update wpt metadata, a=testonly wpt-pr: 26064 wpt-type: metadata
e2492e30a154594184c88a175a90206123852c2d: Bug 1670225 [wpt PR 26064] - [WPT] Migrate most of import-maps resolution tests out of blink internals, a=testonly
Hiroshige Hayashizaki <hiroshige@chromium.org> - Sat, 24 Oct 2020 10:37:14 +0000 - rev 554405
Push 37894 by dluca@mozilla.com at Tue, 27 Oct 2020 04:41:26 +0000
Bug 1670225 [wpt PR 26064] - [WPT] Migrate most of import-maps resolution tests out of blink internals, a=testonly Automatic update from web-platform-tests [WPT] Migrate most of import-maps resolution tests out of blink internals This CL migrates most of import maps resolution tests by observing the resolution results by intercepting module script requests by a service worker. This CL also introduces `useInternalMethods` flag to clarify the tests still requiring internal methods. Bug: 1026809 Change-Id: I16c2a87bb67b530dc97b1631f6968b2d3bafdac6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2457526 Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by: Domenic Denicola <domenic@chromium.org> Cr-Commit-Position: refs/heads/master@{#818366} -- wpt-commits: e85837b2f4eae3be46065a6ed2f77dd15ee8b628 wpt-pr: 26064
56f43eb35361329b307bb44382d3906c6289f663: Bug 1672031 [wpt PR 26162] - Revert "Reenable scroll-animations/element-based-offset tests", a=testonly
Xianzhu Wang <wangxianzhu@chromium.org> - Sat, 24 Oct 2020 10:37:10 +0000 - rev 554404
Push 37894 by dluca@mozilla.com at Tue, 27 Oct 2020 04:41:26 +0000
Bug 1672031 [wpt PR 26162] - Revert "Reenable scroll-animations/element-based-offset tests", a=testonly Automatic update from web-platform-tests Revert "Reenable scroll-animations/element-based-offset tests" This reverts commit bc2f9ba029056f669cfd0a71fe4b2bad6b58b494. Reason for revert: The test is still flaky. Original change's description: > Reenable scroll-animations/element-based-offset tests > > The underlying source of the test flakes was likely addressed in > recent changes to the handling of play and pause for scroll-linked > animations. > > https://chromium-review.googlesource.com/c/chromium/src/+/2386339 > > This patch also contains a cleanup to remove the unnecessarily > convoluted way of hiding the scrollbar for the clamped offset test. > > Tested with 1000+ retries of the two tests in a virtual threaded > environment. > > Bug: 1080609 > Change-Id: If9097b0a2017a9c87a359b61ba93f35bae56b512 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2475935 > Reviewed-by: Xida Chen <xidachen@chromium.org> > Commit-Queue: Kevin Ellis <kevers@chromium.org> > Cr-Commit-Position: refs/heads/master@{#817568} TBR=kevers@chromium.org,xidachen@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1080609 Change-Id: Ic31eede5561182d78e7bf805cd1f112edfd5379c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2483585 Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#818355} -- wpt-commits: ebdb2fcc605b8d71046207441ac7ef6837c38c8c wpt-pr: 26162
d352ca6a45a4e16212a5fb56572c3238a18dd73c: Bug 1672030 [wpt PR 26152] - Fieldset NG: Fix relayout result of a percent-height fieldset, a=testonly
Kent Tamura <tkent@chromium.org> - Sat, 24 Oct 2020 10:37:07 +0000 - rev 554403
Push 37894 by dluca@mozilla.com at Tue, 27 Oct 2020 04:41:26 +0000
Bug 1672030 [wpt PR 26152] - Fieldset NG: Fix relayout result of a percent-height fieldset, a=testonly Automatic update from web-platform-tests Fieldset NG: Fix relayout result of a percent-height fieldset We should assume a percent-height fieldset is HasDescendantThatDependsOnPercentageBlockSize() because the fieldset content box has a kind of a percent-height if the fieldset has a percent-height. Bug: 1138204 Change-Id: Ic9307c190e5aacb8bc47485059d1bdeefa0fedd4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2479482 Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#818337} -- wpt-commits: e2fc3cb2fad2cf77878a38b5563c2100cd3a14bb wpt-pr: 26152
5ce326e76d6df32266e90d2d72a16dc150be5a69: Bug 1672028 [wpt PR 26109] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 19 Oct 2020 19:52:59 +0000 - rev 554402
Push 37894 by dluca@mozilla.com at Tue, 27 Oct 2020 04:41:26 +0000
Bug 1672028 [wpt PR 26109] - Update wpt metadata, a=testonly wpt-pr: 26109 wpt-type: metadata
fa103e2c973555091c18e0ecab2897a4a804991f: Bug 1672028 [wpt PR 26109] - MSE-in-Workers: Cross-thread function and tests, a=testonly
Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> - Sat, 24 Oct 2020 10:37:00 +0000 - rev 554401
Push 37894 by dluca@mozilla.com at Tue, 27 Oct 2020 04:41:26 +0000
Bug 1672028 [wpt PR 26109] - MSE-in-Workers: Cross-thread function and tests, a=testonly Automatic update from web-platform-tests MSE-in-Workers: Cross-thread function and tests (#26109) Includes implementation of CrossThreadMediaSourceAttachment (CTMSA) and updates to MediaSource and SourceBuffer to use it. CTMSA owns a lock that it takes on most operations. It also provides a utility method (RunExclusively()), which is used by the MSE API to take that same lock during most operations on the API. The same thread attachment provides a basic version of the same, though no lock is used. CTMSA understands whether or not it is attached, has ever started closing, and whether or not either of the attached contexts has ever destructed. It conditions cross-thread operations to safely behave when one or both contexts is being destructed. MediaSource is given its own small lock that it uses to guard its reference to the attachment instance, when attached. This is required because attachment start is synchronous on the main thread, even if the MediaSource is owned by worker context. CTMSA and MediaSource cooperate to ensure mutex and safety of the two-stage attachment start. In MediaSource::ContextDestroyed(), further care is taken to prevent attachment start success when worker context destruction is possibly racing the main thread's attempt to start attachment. `context_already_destroyed_`, protected by MediaSource's lock, is used to prevent that start from succeeding. MediaSource's context destruction can no longer always assume that accessing the demuxer via the WebMediaSource (and WebSourceBuffers) is safe. The worker version of MediaSource context destruction uses the attachment's RunExclusively() to safely know if it can cleanly Close the underlying demuxer, or if instead it must do a simpler shutdown. Future specification work will likely determine some signal to the media element when the worker-owned MediaSource's context is shutdown, yet the element itself is still alive. For now, sane results are returned by the attachment (nothing buffered nor seekable), with no other error provided. Possible app workarounds might include main and worker watchdogs and being careful about when the main thread explicitly terminates the worker. This experimental implementation attempts to retain BackgroundVideoOptimization, even for MSE-in-Workers, but does not support AudioVideoTracks in the worker MediaSource or SourceBuffer. Plumbing of appropriately-identified track metadata parsed from initialization segment in the worker is used to populate (and remove) media element AudioVideoTracks that should agree with the track id's used internally in WebMediaPlayerImpl to accomplish BackgroundVideoOptimization. As a simplification, CTMSA assumes it can be used for at most one attachment. Effectively, this assumes that the currently on-by-default MediaSourceRevokeObjectURLOnAttach feature behavior will be always-on soon. If CTMSA is not unregistered automatically after successful attachment start (e.g., if that feature is disabled) and if the app attempts to re-use the corresponding object URL for a later attachment, that attachment will be rejected by CTMSA. Note that the same-thread attachment would still allow such re-use when that feature is disabled. Updated web-test: mediasource-worker-attach.html changed to ...-play.html and fixed New web-test: mediasource-worker-play-terminate-worker.html Manual test: page refreshing while running mediasource-worker-play*.html BUG=878133 Change-Id: I21f6542b90d51bdc28096500fb1441d202ab4ee8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2459431 Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org> Reviewed-by: Will Cassella <cassew@google.com> Cr-Commit-Position: refs/heads/master@{#818174} Co-authored-by: Matt Wolenetz <wolenetz@chromium.org> -- wpt-commits: 83cff49301dabb7f04195600a65282b1a491ccd0 wpt-pr: 26109
88b0119e17e18ea9de6c033b25f2e7593d6f8eea: Bug 1672027 [wpt PR 26145] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 21 Oct 2020 22:35:32 +0000 - rev 554400
Push 37894 by dluca@mozilla.com at Tue, 27 Oct 2020 04:41:26 +0000
Bug 1672027 [wpt PR 26145] - Update wpt metadata, a=testonly wpt-pr: 26145 wpt-type: metadata
1e3cfe61dbfa34bc1270ab8dd9e01dc6c9081faa: Bug 1672027 [wpt PR 26145] - Fix erronous ref for density-size-correction, a=testonly
Noam Rosenthal <noam@webkit.org> - Sat, 24 Oct 2020 10:36:53 +0000 - rev 554399
Push 37894 by dluca@mozilla.com at Tue, 27 Oct 2020 04:41:26 +0000
Bug 1672027 [wpt PR 26145] - Fix erronous ref for density-size-correction, a=testonly Automatic update from web-platform-tests fix erronous ref for density-size-correction -- wpt-commits: ccec5e33e4884f35e897518591db9ca3c0f1f411 wpt-pr: 26145
eac1361b07b04ebd89c6d2be79dfc1343a2dc8b5: Bug 1672025 [wpt PR 26148] - [AspectRatio] Fix serialization of aspect-ratio, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sat, 24 Oct 2020 10:35:52 +0000 - rev 554398
Push 37894 by dluca@mozilla.com at Tue, 27 Oct 2020 04:41:26 +0000
Bug 1672025 [wpt PR 26148] - [AspectRatio] Fix serialization of aspect-ratio, a=testonly Automatic update from web-platform-tests [AspectRatio] Fix serialization of aspect-ratio Per these conversations: https://github.com/w3c/csswg-drafts/issues/5084 https://github.com/w3c/csswg-drafts/issues/5561 R=futhark@chromium.org, xiaochengh@chromium.org Bug: 1045668 Change-Id: I066809e31e4120b0c179235a101db5c74c3dd146 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2480064 Commit-Queue: Christian Biesinger <cbiesinger@chromium.org> Auto-Submit: Christian Biesinger <cbiesinger@chromium.org> Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org> Cr-Commit-Position: refs/heads/master@{#818250} -- wpt-commits: 8b94afceafbd71defd6e3a1f056321b7788e18c3 wpt-pr: 26148
0c911c4f6c851621f67f56d5af4fec4b0e2edce5: Bug 1672024 [wpt PR 26143] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 21 Oct 2020 22:30:25 +0000 - rev 554397
Push 37894 by dluca@mozilla.com at Tue, 27 Oct 2020 04:41:26 +0000
Bug 1672024 [wpt PR 26143] - Update wpt metadata, a=testonly wpt-pr: 26143 wpt-type: metadata
dae9fee48313f719cc5615ad7ea5648fa6a26733: Bug 1672024 [wpt PR 26143] - [Canvas new API] Add FontKerning to Canvas context 2d, a=testonly
yiyix <yiyix@chromium.org> - Fri, 23 Oct 2020 22:01:37 +0000 - rev 554396
Push 37894 by dluca@mozilla.com at Tue, 27 Oct 2020 04:41:26 +0000
Bug 1672024 [wpt PR 26143] - [Canvas new API] Add FontKerning to Canvas context 2d, a=testonly Automatic update from web-platform-tests [Canvas new API] Add FontKerning to Canvas context 2d Add FontKerning to the new Canvas API, which is currently under the runtime flag, NewCanvas2DAPI. Bug: 1137055 Change-Id: Ic95f74e76eecc2a1fd3aa152d89a4e593a8a8e10 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2470418 Commit-Queue: Yi Xu <yiyix@chromium.org> Reviewed-by: Bo <boliu@chromium.org> Reviewed-by: Fernando Serboncini <fserb@chromium.org> Reviewed-by: Aaron Krajeski <aaronhk@chromium.org> Cr-Commit-Position: refs/heads/master@{#818213} -- wpt-commits: 38bc0248d6de92451d8d1c180056dbae0564606c wpt-pr: 26143
d57e8deefbe92931cc675979fbed4c22b2769f2c: Bug 1670173 [wpt PR 26059] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 22 Oct 2020 09:45:27 +0000 - rev 554395
Push 37894 by dluca@mozilla.com at Tue, 27 Oct 2020 04:41:26 +0000
Bug 1670173 [wpt PR 26059] - Update wpt metadata, a=testonly wpt-pr: 26059 wpt-type: metadata
a9eaa29e3d7591ee6845f625fb5029a349c21d93: Bug 1670173 [wpt PR 26059] - [css-flex] Fix min-height: auto for replaced elements, a=testonly
David Grogan <dgrogan@chromium.org> - Fri, 23 Oct 2020 22:01:29 +0000 - rev 554394
Push 37894 by dluca@mozilla.com at Tue, 27 Oct 2020 04:41:26 +0000
Bug 1670173 [wpt PR 26059] - [css-flex] Fix min-height: auto for replaced elements, a=testonly Automatic update from web-platform-tests [css-flex] Fix min-height: auto for replaced elements min-height: auto had been using the image's natural height as the content size suggestion, ignoring a specified definite inline size, but according to this spec chain, the specified definite inline size should transfer through the aspect ratio and affect the min-content size. https://drafts.csswg.org/css-sizing-3/#min-content -> https://drafts.csswg.org/css-sizing-3/#intrinsic-sizes -> https://www.w3.org/TR/CSS2/visudet.html#float-replaced-width -> https://www.w3.org/TR/CSS2/visudet.html#inline-replaced-width -> """ if 'width' has a computed value of 'auto', 'height' has some other computed value, and the element does have an intrinsic ratio; then the used value of 'width' is: (used height) * (intrinsic ratio) """ This fix also made clear that the regression caused by https://chromium-review.googlesource.com/c/chromium/src/+/2333530 was not so harmless -- the issue wasn't a wrong test in align-items-007, but rather an incorrect block size given to a replaced element with aspect ratio but no size in the content size suggestion. We had been giving such element a 150px intrinsic block size; the correct size is the available inline size passed through the aspect ratio. This is now fixed in this patch. The changed case at the end of flex-aspect-ratio-img-column-011.html was asserting the opposite behavior of flex-minimum-height-flex-items-007.xht (Gerrit or something keeps adding a bogus "fixed" line under Change-Id, in case this CL shows up someplace random) Change-Id: I05cb4b3ca796b3df02dfa5d8e3790d6164213be9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2462574 Commit-Queue: David Grogan <dgrogan@chromium.org> Reviewed-by: Christian Biesinger <cbiesinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#818100} -- wpt-commits: 3782f5a3f63bb94bb0f8422e222e5cf6738bba7c wpt-pr: 26059
3b1ad2471e23ff14cd15ab1e627ac11aed02e9e9: Bug 1672022 [wpt PR 26154] - Fix AtomicStringTable lowercase translator., a=testonly
Jeremy Roman <jbroman@chromium.org> - Fri, 23 Oct 2020 22:01:25 +0000 - rev 554393
Push 37894 by dluca@mozilla.com at Tue, 27 Oct 2020 04:41:26 +0000
Bug 1672022 [wpt PR 26154] - Fix AtomicStringTable lowercase translator., a=testonly Automatic update from web-platform-tests Fix AtomicStringTable lowercase translator. It was erroneously checking if a candidate entry in the atomic string table was an existing lowercase version of the provided string by comparing the two strings for lower-ASCII equality, but this doesn't imply that the string found in the atomic string table is lowercase ASCII. For urgent merging to release branches, this is a minimal fix. A followup CL will land a more efficient version of this. Bug: 1138487 Change-Id: I3af7411879ea831c9210e43cee16bca607b51b30 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2480844 Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Mason Freed <masonfreed@chromium.org> Commit-Queue: Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#818060} -- wpt-commits: 91376d70bde4173790a6b4bd5098e32261975825 wpt-pr: 26154
c859f993040e40cb5065b6a9d5bbc7a459b03e81: Bug 1672021 [wpt PR 26149] - Synchronize classList on SVGElement.className.baseVal updates, a=testonly
Fredrik Söderqvist <fs@opera.com> - Fri, 23 Oct 2020 22:01:22 +0000 - rev 554392
Push 37894 by dluca@mozilla.com at Tue, 27 Oct 2020 04:41:26 +0000
Bug 1672021 [wpt PR 26149] - Synchronize classList on SVGElement.className.baseVal updates, a=testonly Automatic update from web-platform-tests Synchronize classList on SVGElement.className.baseVal updates Element.classList is normally updated by AttributeChanged(). When the underlying attribute is updated via the corresponding SVG animated property AttributeChanged() is not invoked, which makes the list and attribute go out of sync. Refactor baseVal updates on SVGElement so that they go through a single entry point by renaming SvgAttributeBaseValChanged() to BaseValueChanged() and folding it into the other user (SVGElement::AttributeChanged). Fold InvalidateSVGAttributes() into BaseValueChanged() since it's the only caller. BaseValueChanged() is then updated to update the classList when the className base value is updated. Move the classList update into a shared Element::UpdateClassList() function. Fixed: 1137953 Change-Id: I64efff0bfd163b14eb937c635c3d170b4511f4a7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2480023 Commit-Queue: Fredrik Söderquist <fs@opera.com> Reviewed-by: Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/master@{#818035} -- wpt-commits: 51d4134420706b7765ce49ac9b7d0d1912263731 wpt-pr: 26149
748868f2c07d4e5cb7b3e3328bd4c00df116b1d4: Bug 1672020 [wpt PR 26156] - Update interfaces/worklets.idl, a=testonly
autofoolip <auto@foolip.org> - Fri, 23 Oct 2020 22:01:18 +0000 - rev 554391
Push 37894 by dluca@mozilla.com at Tue, 27 Oct 2020 04:41:26 +0000
Bug 1672020 [wpt PR 26156] - Update interfaces/worklets.idl, a=testonly Automatic update from web-platform-tests Update interfaces/worklets.idl (#26156) Source: https://github.com/w3c/webref/blob/b470181/ed/idl/worklets.idl Build: https://travis-ci.org/w3c/webref/builds/736462459 -- wpt-commits: bbe46e5a2e5dfbc4905e8f90b38414cf6c795203 wpt-pr: 26156
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip