1. 06 Aug, 2019 40 commits
    • Lukasz Anforowicz's avatar
      Do not apply CORB to application/x-www-form-urlencoded. · 782f209d
      Lukasz Anforowicz authored
      Bug: 990853, 802836
      Change-Id: I7aeba7f34ae3257a8c0d7900a4f266f872273304
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1739646
      Commit-Queue: Charlie Reis <creis@chromium.org>
      Auto-Submit: Łukasz Anforowicz <lukasza@chromium.org>
      Reviewed-by: default avatarCharlie Reis <creis@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684464}
      782f209d
    • Harsh Patel's avatar
      Proguard conditional keeps for layouts · 58305bfd
      Harsh Patel authored
      Added flag for aapt2 link to generate proguard conditional keep rules.
      
      Bug: 682786
      Change-Id: I11e7afd5b540bcc6bc0f4bf54a8bd20c750fb0a3
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1723796
      Commit-Queue: Harsh Patel <harshpa@google.com>
      Reviewed-by: default avatarSam Maier <smaier@chromium.org>
      Reviewed-by: default avatarAndrew Grieve <agrieve@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684463}
      58305bfd
    • Nektarios Paisios's avatar
      Added paragraph navigation and whole page caret browsing on Mac · c0fd3c06
      Nektarios Paisios authored
      A few text marker attributes are still missing from our Mac implementation.
      This patch adds the missing attributes for paragraph and caret browsing.
      This patch also declares any missing attributes for text markers in the form of constants,
      instead of using text strings.
      This is the full set of text marker attributes supported by Safari.
      R=aleventhal@chromium.org
      Bug: 990931
      
      Change-Id: I9839f2f1f419c14b7730573ac1f7c1f3306f36c3
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1732692
      Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
      Reviewed-by: default avatarAaron Leventhal <aleventhal@chromium.org>
      Auto-Submit: Nektarios Paisios <nektar@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684462}
      c0fd3c06
    • Sami Kyostila's avatar
      chrome/browser/net: Always specify thread affinity when posting tasks · a46c813c
      Sami Kyostila authored
      *** Note: There is no behavior change from this patch. ***
      
      The PostTask APIs will shortly be changed to require all tasks to explicitly
      specify their thread affinity, i.e., whether the task should run on the thread
      pool or a specific named thread such as a BrowserThread. This patch updates all
      call sites with thread affinity annotation. We also remove the "WithTraits"
      suffix to make the call sites more readable.
      
      Before:
      
          // Thread pool task.
          base::PostTaskWithTraits(FROM_HERE, {...}, ...);
      
          // UI thread task.
          base::PostTaskWithTraits(FROM_HERE, {BrowserThread::UI, ...}, ...);
      
      After:
      
          // Thread pool task.
          base::PostTask(FROM_HERE, {base::ThreadPool(), ...}, ...);
      
          // UI thread task.
          base::PostTask(FROM_HERE, {BrowserThread::UI, ...}, ...);
      
      This patch was semi-automatically prepared with these steps:
      
          1. Patch in https://crrev.com/c/1635827 to make thread affinity a build-time
             requirement.
          2. Run an initial pass with a clang rewriter:
             https://chromium-review.googlesource.com/c/chromium/src/+/1635623
          3. ninja -C out/Debug | grep 'requested here' | cut -d: -f1-3 | sort | \
                 uniq > errors.txt
          4. while read line; do
               f=$(echo $line | cut -d: -f 1)
               r=$(echo $line | cut -d: -f 2)
               c=$(echo $line | cut -d: -f 3)
               sed -i "${r}s/./&base::ThreadPool(),/$c" $f
             done < errors.txt
          5. GOTO 3 until build succeeds.
          6. Remove the "WithTraits" suffix from task API call sites:
      
             $ tools/git/mffr.py -i <(cat <<EOF
             [
               ["PostTaskWithTraits",
                "PostTask"],
               ["PostDelayedTaskWithTraits",
                "PostDelayedTask"],
               ["PostTaskWithTraitsAndReply",
                "PostTaskAndReply"],
               ["CreateTaskRunnerWithTraits",
                "CreateTaskRunner"],
               ["CreateSequencedTaskRunnerWithTraits",
                "CreateSequencedTaskRunner"],
               ["CreateUpdateableSequencedTaskRunnerWithTraits",
                "CreateUpdateableSequencedTaskRunner"],
               ["CreateSingleThreadTaskRunnerWithTraits",
                "CreateSingleThreadTaskRunner"],
               ["CreateCOMSTATaskRunnerWithTraits",
                "CreateCOMSTATaskRunner"]
             ]
             EOF
             )
      
      This CL was uploaded by git cl split.
      
      R=nharper@chromium.org
      
      Bug: 968047
      Change-Id: Ie94b75f8055d40ca1225b1da7154e8f86a4b1350
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1738596
      Auto-Submit: Sami Kyöstilä <skyostil@chromium.org>
      Reviewed-by: default avatarNick Harper <nharper@chromium.org>
      Commit-Queue: Nick Harper <nharper@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684461}
      a46c813c
    • Dave Tapuska's avatar
      Add boolean indicating whether cross browsing instance frame lookup is allowed. · fc457ca8
      Dave Tapuska authored
      WebView and extensions allow frame lookup across browsing instances. We wish
      to enforce Same Agent restrictions in bindings but for these cases we
      cannot. This change adds the ability to mark frames as having
      CrossBrowsingInstanceFrameLookup. A folloup change will add a SECURITY_CHECK
      to the bindings interface for this.
      
      BUG=970360
      
      Change-Id: I76334a82644161f7b44b07a32847514bf20acecf
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1708752Reviewed-by: default avatarDevlin <rdevlin.cronin@chromium.org>
      Reviewed-by: default avatarDaniel Cheng <dcheng@chromium.org>
      Reviewed-by: default avatarAlex Moshchuk <alexmos@chromium.org>
      Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684460}
      fc457ca8
    • Eric Willigers's avatar
      CSS: opacity properties accept percentage · baaab7ff
      Eric Willigers authored
      The following properties accept either a number or a percentage:
      - fill-opacity
      - flood-opacity
      - opacity
      - shape-image-threshold
      - stop-opacity
      - stroke-opacity
      
      Each property serializes as a number.
      
      Spec:
      https://drafts.csswg.org/css-color/#typedef-alpha-value
      
      Intent to Implement and Ship:
      https://groups.google.com/a/chromium.org/d/msg/blink-dev/SdPIaBdhzAQ/f26Mp_3REAAJ
      
      Credit to hanlee.dev@gmail.com for uploading a patch.
      
      Bug: 907787
      Change-Id: Ie297d7225becafde73449c35bcb719c4847c87d2
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1734753
      Commit-Queue: Emil A Eklund <eae@chromium.org>
      Auto-Submit: Eric Willigers <ericwilligers@chromium.org>
      Reviewed-by: default avatarEmil A Eklund <eae@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684459}
      baaab7ff
    • Sami Kyostila's avatar
      chrome/browser/push_messaging: Always specify thread affinity when posting tasks · 0734535c
      Sami Kyostila authored
      *** Note: There is no behavior change from this patch. ***
      
      The PostTask APIs will shortly be changed to require all tasks to explicitly
      specify their thread affinity, i.e., whether the task should run on the thread
      pool or a specific named thread such as a BrowserThread. This patch updates all
      call sites with thread affinity annotation. We also remove the "WithTraits"
      suffix to make the call sites more readable.
      
      Before:
      
          // Thread pool task.
          base::PostTaskWithTraits(FROM_HERE, {...}, ...);
      
          // UI thread task.
          base::PostTaskWithTraits(FROM_HERE, {BrowserThread::UI, ...}, ...);
      
      After:
      
          // Thread pool task.
          base::PostTask(FROM_HERE, {base::ThreadPool(), ...}, ...);
      
          // UI thread task.
          base::PostTask(FROM_HERE, {BrowserThread::UI, ...}, ...);
      
      This patch was semi-automatically prepared with these steps:
      
          1. Patch in https://crrev.com/c/1635827 to make thread affinity a build-time
             requirement.
          2. Run an initial pass with a clang rewriter:
             https://chromium-review.googlesource.com/c/chromium/src/+/1635623
          3. ninja -C out/Debug | grep 'requested here' | cut -d: -f1-3 | sort | \
                 uniq > errors.txt
          4. while read line; do
               f=$(echo $line | cut -d: -f 1)
               r=$(echo $line | cut -d: -f 2)
               c=$(echo $line | cut -d: -f 3)
               sed -i "${r}s/./&base::ThreadPool(),/$c" $f
             done < errors.txt
          5. GOTO 3 until build succeeds.
          6. Remove the "WithTraits" suffix from task API call sites:
      
             $ tools/git/mffr.py -i <(cat <<EOF
             [
               ["PostTaskWithTraits",
                "PostTask"],
               ["PostDelayedTaskWithTraits",
                "PostDelayedTask"],
               ["PostTaskWithTraitsAndReply",
                "PostTaskAndReply"],
               ["CreateTaskRunnerWithTraits",
                "CreateTaskRunner"],
               ["CreateSequencedTaskRunnerWithTraits",
                "CreateSequencedTaskRunner"],
               ["CreateUpdateableSequencedTaskRunnerWithTraits",
                "CreateUpdateableSequencedTaskRunner"],
               ["CreateSingleThreadTaskRunnerWithTraits",
                "CreateSingleThreadTaskRunner"],
               ["CreateCOMSTATaskRunnerWithTraits",
                "CreateCOMSTATaskRunner"]
             ]
             EOF
             )
      
      This CL was uploaded by git cl split.
      
      R=peter@chromium.org
      
      Bug: 968047
      Change-Id: I4e4e63b3ac7944977f2ac01725f153b97d008616
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1739807
      Auto-Submit: Sami Kyöstilä <skyostil@chromium.org>
      Reviewed-by: default avatarPeter Beverloo <peter@chromium.org>
      Commit-Queue: Peter Beverloo <peter@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684458}
      0734535c
    • chromium-autoroll's avatar
      Roll src/third_party/pdfium c9edc556eae1..db9976265161 (3 commits) · edf52eb5
      chromium-autoroll authored
      https://pdfium.googlesource.com/pdfium.git/+log/c9edc556eae1..db9976265161
      
      git log c9edc556eae1..db9976265161 --date=short --no-merges --format='%ad %ae %s'
      2019-08-06 thestig@chromium.org Remove code that checks GetSystemHandler() return value.
      2019-08-06 tsepez@chromium.org Deduplicate pointers to widgets in pwl.
      2019-08-06 thestig@chromium.org Simplify code in CPWL_EditCtrl::SetCursor().
      
      Created with:
        gclient setdep -r src/third_party/pdfium@db9976265161
      
      The AutoRoll server is located here: https://autoroll.skia.org/r/pdfium-autoroll
      
      Documentation for the AutoRoller is here:
      https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
      
      If the roll is causing failures, please contact the current sheriff, who should
      be CC'd on the roll, and stop the roller if necessary.
      
      
      TBR=pdfium-deps-rolls@chromium.org
      
      Bug: None
      Change-Id: Ibb6eff26cfcd25d8de279af96cb540ac271532fd
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1738651Reviewed-by: default avatarchromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
      Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
      Cr-Commit-Position: refs/heads/master@{#684457}
      edf52eb5
    • chromium-autoroll's avatar
      Roll src/third_party/webrtc 7cbee84610a8..63c38e21dae6 (1 commits) · 97e07fa9
      chromium-autoroll authored
      https://webrtc.googlesource.com/src.git/+log/7cbee84610a8..63c38e21dae6
      
      git log 7cbee84610a8..63c38e21dae6 --date=short --no-merges --format='%ad %ae %s'
      2019-08-06 srte@webrtc.org Fix for incorrect transport sequence number config for audio in scenario tests.
      
      Created with:
        gclient setdep -r src/third_party/webrtc@63c38e21dae6
      
      The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-chromium-autoroll
      
      Documentation for the AutoRoller is here:
      https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
      
      If the roll is causing failures, please contact the current sheriff, who should
      be CC'd on the roll, and stop the roller if necessary.
      
      
      TBR=webrtc-chromium-sheriffs-robots@google.com
      
      Bug: None
      Change-Id: I59b8b2b0c4659b657b152e4fa448b7fd09aacdf5
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1738321Reviewed-by: default avatarchromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
      Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
      Cr-Commit-Position: refs/heads/master@{#684456}
      97e07fa9
    • Yue Li's avatar
      Merge Assistant preferences logic into AssistantState · bd9703f6
      Yue Li authored
      Merge the current Assistant prefs controller logic into the
      AssistantStateBase. Will also merge the logic of
      VoiceInteractionController into this controller in the next change.
      
      Bug: b/110211045
      Test: Run existing tests
      Change-Id: I1d3a8388fd66217baad44d7c7043ffd75830e42d
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1727733
      Commit-Queue: Yue Li <updowndota@chromium.org>
      Reviewed-by: default avatarXiyuan Xia <xiyuan@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684455}
      bd9703f6
    • Yue Li's avatar
      Sync Assistant admin policy at startup · c8c12cbb
      Yue Li authored
      Check if Assistant is disabled by admin policy at Service startup.
      
      Bug: b/138589497, 982286
      Change-Id: I3efe448f95bc8cc8059885db23fb004de5b3af89
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1734742
      Commit-Queue: Yue Li <updowndota@chromium.org>
      Reviewed-by: default avatarTao Wu <wutao@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684454}
      c8c12cbb
    • Sami Kyostila's avatar
      chrome/browser/tracing: Always specify thread affinity when posting tasks · d8fa3628
      Sami Kyostila authored
      *** Note: There is no behavior change from this patch. ***
      
      The PostTask APIs will shortly be changed to require all tasks to explicitly
      specify their thread affinity, i.e., whether the task should run on the thread
      pool or a specific named thread such as a BrowserThread. This patch updates all
      call sites with thread affinity annotation. We also remove the "WithTraits"
      suffix to make the call sites more readable.
      
      Before:
      
          // Thread pool task.
          base::PostTaskWithTraits(FROM_HERE, {...}, ...);
      
          // UI thread task.
          base::PostTaskWithTraits(FROM_HERE, {BrowserThread::UI, ...}, ...);
      
      After:
      
          // Thread pool task.
          base::PostTask(FROM_HERE, {base::ThreadPool(), ...}, ...);
      
          // UI thread task.
          base::PostTask(FROM_HERE, {BrowserThread::UI, ...}, ...);
      
      This patch was semi-automatically prepared with these steps:
      
          1. Patch in https://crrev.com/c/1635827 to make thread affinity a build-time
             requirement.
          2. Run an initial pass with a clang rewriter:
             https://chromium-review.googlesource.com/c/chromium/src/+/1635623
          3. ninja -C out/Debug | grep 'requested here' | cut -d: -f1-3 | sort | \
                 uniq > errors.txt
          4. while read line; do
               f=$(echo $line | cut -d: -f 1)
               r=$(echo $line | cut -d: -f 2)
               c=$(echo $line | cut -d: -f 3)
               sed -i "${r}s/./&base::ThreadPool(),/$c" $f
             done < errors.txt
          5. GOTO 3 until build succeeds.
          6. Remove the "WithTraits" suffix from task API call sites:
      
             $ tools/git/mffr.py -i <(cat <<EOF
             [
               ["PostTaskWithTraits",
                "PostTask"],
               ["PostDelayedTaskWithTraits",
                "PostDelayedTask"],
               ["PostTaskWithTraitsAndReply",
                "PostTaskAndReply"],
               ["CreateTaskRunnerWithTraits",
                "CreateTaskRunner"],
               ["CreateSequencedTaskRunnerWithTraits",
                "CreateSequencedTaskRunner"],
               ["CreateUpdateableSequencedTaskRunnerWithTraits",
                "CreateUpdateableSequencedTaskRunner"],
               ["CreateSingleThreadTaskRunnerWithTraits",
                "CreateSingleThreadTaskRunner"],
               ["CreateCOMSTATaskRunnerWithTraits",
                "CreateCOMSTATaskRunner"]
             ]
             EOF
             )
      
      This CL was uploaded by git cl split.
      
      R=oysteine@chromium.org
      
      Bug: 968047
      Change-Id: Ibc31dc65ba9108247d7e6780d5f815827f4a3354
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1739814
      Auto-Submit: Sami Kyöstilä <skyostil@chromium.org>
      Reviewed-by: default avataroysteine <oysteine@chromium.org>
      Commit-Queue: oysteine <oysteine@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684453}
      d8fa3628
    • Matt Menke's avatar
      Make HostStringIsLocalhost() call IPAddress::IsLoopback(). · fbcdfcda
      Matt Menke authored
      Currently, they do the same thing for numeric IPs (modulo a DCHECK
      that the IP is valid in HostStringIsLocalhost()), but I don't think we
      want the two methods to have potentially divergent concept of loopback
      IPs if, for instance, we add IPv6-mapped IPv4 loopback addresses.
      
      Bug: None
      Change-Id: Ia193c2dff08f90bf62847a89fb6b31f130f75fa7
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1739482Reviewed-by: default avatarEric Roman <eroman@chromium.org>
      Commit-Queue: Matt Menke <mmenke@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684452}
      fbcdfcda
    • Josh Nohle's avatar
      [DeviceSync v2] Add authorized entity number for v2 DeviceSync project · 0c9f843f
      Josh Nohle authored
      CryptAuth v2 Enrollment and v2 DeviceSync are separate
      Cloud/Pantheon/Firebase projects that need separate authorization to
      send push notifications to the client. The authorized entity values here
      identify the v2 Enrollment and v2 DeviceSync Cloud/Pantheon/Firebase
      projects.
      
      While the user's Instance ID can be used across multiple CryptAuth
      projects, the Instance ID *tokens* are project specific. The authorized
      entity values are needed to generate Instance ID tokens. These tokens
      are unique and immutable identifiers of the client's authorization of
      the project to send the client push notifications.
      
      Bug: 951969, 990430
      Change-Id: Iad38286357f71054530a9afc05c5dc2382edcbae
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1735472
      Commit-Queue: Josh Nohle <nohle@chromium.org>
      Auto-Submit: Josh Nohle <nohle@chromium.org>
      Reviewed-by: default avatarKyle Horimoto <khorimoto@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684451}
      0c9f843f
    • Adam Ettenberger's avatar
      Adjust AXTree::Unserialize to notify events outside of UpdateNode [3/3] · ff6e9ce5
      Adam Ettenberger authored
      This change adds DCHECKs to AXNode::*Unignored* traversal methods to
      guarantee they are not accessed in the middle of a tree update, which
      can cause subtle bugs if the previously unignored parent becomes
      ignored during the update.
      
      ---
      
      Problem :
        AXTree notifies AXTreeObservers of node and subtree changes in the middle
        of a tree update, which means observers may be seeing a tree state that's
        incomplete. This can lead to subtle bugs when observers access nodes in the
        AXTree other than the node being updated.
        e.g. |GetUnignoredParent| may be invalid during a notification, but
        correct afterwards.
      
      Proposed solution :
        Separate notifications from updates in AXTree::Unserialize.
      
        This requires the following steps :
          1. Record all operations that would be performed on the tree.
          2. Fire all on destroy and OnNodeDataWillChange callbacks.
          3. Apply all update operations.
          4. Fire all created and node data changed callbacks.
      
      
        For additional context, see these comments by Nektarios and Dominic :
        https://chromium-review.googlesource.com/c/chromium/src/+/1650222/20#message-ffe9bf96b616a915bebf2e69d7803bcae6a18b24
        https://chromium-review.googlesource.com/c/chromium/src/+/1535171/69#message-7b62970b193439a1878d7339cdc94d2556d0a416
      
        I  plan to submit approximately 3 CLs to resolve this :
          1. Handle Pre/Post Tree changes (create node / destroy subtree)
          2. Handle Pre/Post Node data changes (attributes will / have changes)
          3. Add DCHECKs to AXNode::*Unignored* accessors, along with any remaining
             work required to do so, to help harden these paths.
      
      Bug: 974444
      Change-Id: I40ce8a29b7faf2f1eeea513c37a19320062783f8
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1710052
      Commit-Queue: Adam Ettenberger <adettenb@microsoft.com>
      Reviewed-by: default avatarNektarios Paisios <nektar@chromium.org>
      Reviewed-by: default avatarKurt Catti-Schmidt <kschmi@microsoft.com>
      Cr-Commit-Position: refs/heads/master@{#684450}
      ff6e9ce5
    • Sami Kyostila's avatar
      chrome/browser/performance_monitor: Always specify thread affinity when posting tasks · 302a8ab7
      Sami Kyostila authored
      *** Note: There is no behavior change from this patch. ***
      
      The PostTask APIs will shortly be changed to require all tasks to explicitly
      specify their thread affinity, i.e., whether the task should run on the thread
      pool or a specific named thread such as a BrowserThread. This patch updates all
      call sites with thread affinity annotation. We also remove the "WithTraits"
      suffix to make the call sites more readable.
      
      Before:
      
          // Thread pool task.
          base::PostTaskWithTraits(FROM_HERE, {...}, ...);
      
          // UI thread task.
          base::PostTaskWithTraits(FROM_HERE, {BrowserThread::UI, ...}, ...);
      
      After:
      
          // Thread pool task.
          base::PostTask(FROM_HERE, {base::ThreadPool(), ...}, ...);
      
          // UI thread task.
          base::PostTask(FROM_HERE, {BrowserThread::UI, ...}, ...);
      
      This patch was semi-automatically prepared with these steps:
      
          1. Patch in https://crrev.com/c/1635827 to make thread affinity a build-time
             requirement.
          2. Run an initial pass with a clang rewriter:
             https://chromium-review.googlesource.com/c/chromium/src/+/1635623
          3. ninja -C out/Debug | grep 'requested here' | cut -d: -f1-3 | sort | \
                 uniq > errors.txt
          4. while read line; do
               f=$(echo $line | cut -d: -f 1)
               r=$(echo $line | cut -d: -f 2)
               c=$(echo $line | cut -d: -f 3)
               sed -i "${r}s/./&base::ThreadPool(),/$c" $f
             done < errors.txt
          5. GOTO 3 until build succeeds.
          6. Remove the "WithTraits" suffix from task API call sites:
      
             $ tools/git/mffr.py -i <(cat <<EOF
             [
               ["PostTaskWithTraits",
                "PostTask"],
               ["PostDelayedTaskWithTraits",
                "PostDelayedTask"],
               ["PostTaskWithTraitsAndReply",
                "PostTaskAndReply"],
               ["CreateTaskRunnerWithTraits",
                "CreateTaskRunner"],
               ["CreateSequencedTaskRunnerWithTraits",
                "CreateSequencedTaskRunner"],
               ["CreateUpdateableSequencedTaskRunnerWithTraits",
                "CreateUpdateableSequencedTaskRunner"],
               ["CreateSingleThreadTaskRunnerWithTraits",
                "CreateSingleThreadTaskRunner"],
               ["CreateCOMSTATaskRunnerWithTraits",
                "CreateCOMSTATaskRunner"]
             ]
             EOF
             )
      
      This CL was uploaded by git cl split.
      
      R=simonhatch@chromium.org
      
      Bug: 968047
      Change-Id: I90e2499257ebe0b5914568b3f496d32c48b4f6e0
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1739806
      Auto-Submit: Sami Kyöstilä <skyostil@chromium.org>
      Reviewed-by: default avatarSimon Hatch <simonhatch@chromium.org>
      Commit-Queue: Simon Hatch <simonhatch@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684449}
      302a8ab7
    • Jacob DeWitt's avatar
      Add jacde to WebXR-related OWNERS files. · b3b1e0ce
      Jacob DeWitt authored
      Change-Id: I158bbc20c0b0eea748d1200b4709d48d1355fe80
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1739667Reviewed-by: default avatarBrandon Jones <bajones@chromium.org>
      Reviewed-by: default avatarKlaus Weidner <klausw@chromium.org>
      Reviewed-by: default avatarAlexander Cooper <alcooper@chromium.org>
      Commit-Queue: Jacob DeWitt <jacde@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684448}
      b3b1e0ce
    • Robert Ma's avatar
      Mark an incoming web-animations test as flaky · ce229a10
      Robert Ma authored
      Currently blocking the importer. Example:
      https://test-results.appspot.com/data/layout_results/linux-rel/159555/not_site_per_process_webkit_layout_tests%20%28with%20patch%29/layout-test-results/results.html
      
      No-Try because the change hasn't landed in Chromium yet.
      
      TBR=flackr
      
      No-Try: True
      Bug: 991295
      Change-Id: I599bd336d45df0ca928711657cb81cb838713990
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1738335Reviewed-by: default avatarRobert Ma <robertma@chromium.org>
      Commit-Queue: Robert Ma <robertma@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684447}
      ce229a10
    • Jacob DeWitt's avatar
      Update WebXR gamepads to latest version of xr-standard mapping · 05d736b3
      Jacob DeWitt authored
      The mapping is defined by the spec at:
      https://immersive-web.github.io/webxr/#xr-standard-gamepad-mapping
      Now, only a primary trigger is required for a controller to claim
      xr-standard mapping, and the order of some of the buttons has changed.
      
      Centralize the logic of how to order buttons + input axes, as well as
      where/when to add placeholder values in the XRStandardGamepadBuilder
      class.
      
      Bug: 979246
      Change-Id: Iefb116ea603c0a7237575d189686fd2daee9de90
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1728345
      Commit-Queue: Jacob DeWitt <jacde@chromium.org>
      Reviewed-by: default avatarAlexander Cooper <alcooper@chromium.org>
      Reviewed-by: default avatarBrian Sheedy <bsheedy@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684446}
      05d736b3
    • Sami Kyostila's avatar
      chrome/browser/prefs: Always specify thread affinity when posting tasks · 1dc0388b
      Sami Kyostila authored
      *** Note: There is no behavior change from this patch. ***
      
      The PostTask APIs will shortly be changed to require all tasks to explicitly
      specify their thread affinity, i.e., whether the task should run on the thread
      pool or a specific named thread such as a BrowserThread. This patch updates all
      call sites with thread affinity annotation. We also remove the "WithTraits"
      suffix to make the call sites more readable.
      
      Before:
      
          // Thread pool task.
          base::PostTaskWithTraits(FROM_HERE, {...}, ...);
      
          // UI thread task.
          base::PostTaskWithTraits(FROM_HERE, {BrowserThread::UI, ...}, ...);
      
      After:
      
          // Thread pool task.
          base::PostTask(FROM_HERE, {base::ThreadPool(), ...}, ...);
      
          // UI thread task.
          base::PostTask(FROM_HERE, {BrowserThread::UI, ...}, ...);
      
      This patch was semi-automatically prepared with these steps:
      
          1. Patch in https://crrev.com/c/1635827 to make thread affinity a build-time
             requirement.
          2. Run an initial pass with a clang rewriter:
             https://chromium-review.googlesource.com/c/chromium/src/+/1635623
          3. ninja -C out/Debug | grep 'requested here' | cut -d: -f1-3 | sort | \
                 uniq > errors.txt
          4. while read line; do
               f=$(echo $line | cut -d: -f 1)
               r=$(echo $line | cut -d: -f 2)
               c=$(echo $line | cut -d: -f 3)
               sed -i "${r}s/./&base::ThreadPool(),/$c" $f
             done < errors.txt
          5. GOTO 3 until build succeeds.
          6. Remove the "WithTraits" suffix from task API call sites:
      
             $ tools/git/mffr.py -i <(cat <<EOF
             [
               ["PostTaskWithTraits",
                "PostTask"],
               ["PostDelayedTaskWithTraits",
                "PostDelayedTask"],
               ["PostTaskWithTraitsAndReply",
                "PostTaskAndReply"],
               ["CreateTaskRunnerWithTraits",
                "CreateTaskRunner"],
               ["CreateSequencedTaskRunnerWithTraits",
                "CreateSequencedTaskRunner"],
               ["CreateUpdateableSequencedTaskRunnerWithTraits",
                "CreateUpdateableSequencedTaskRunner"],
               ["CreateSingleThreadTaskRunnerWithTraits",
                "CreateSingleThreadTaskRunner"],
               ["CreateCOMSTATaskRunnerWithTraits",
                "CreateCOMSTATaskRunner"]
             ]
             EOF
             )
      
      This CL was uploaded by git cl split.
      
      R=battre@chromium.org
      
      Bug: 968047
      Change-Id: I034c246f7d4dbfb87ad12731f35e47e8710ddd16
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1738600
      Auto-Submit: Sami Kyöstilä <skyostil@chromium.org>
      Reviewed-by: default avatarDominic Battré <battre@chromium.org>
      Commit-Queue: Dominic Battré <battre@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684445}
      1dc0388b
    • Mustafa Emre Acer's avatar
      Add meacer@ as a url_formatter owner · 8c1ca43d
      Mustafa Emre Acer authored
      Change-Id: I9a6c3772e33e67cfe99f2d20da97c0f52aaa8fbd
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1739543Reviewed-by: default avatarTommy Li <tommycli@chromium.org>
      Commit-Queue: Mustafa Emre Acer <meacer@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684444}
      8c1ca43d
    • Carlos Caballero's avatar
      Remove references of MessageLoopForIO in /extensions/renderer · d372d6a1
      Carlos Caballero authored
      MessageLoopForIO will go away soon use ScopedTaskEnvironment instead.
      
      ScopedTaskEnvironment will per default start a ThreadPool, which should
      be fine in most of the cases. If you believe your test needs to make sure
      that no ThreadPool runs let me know and I will update the patch.
      
      BUG=891670
      This CL was uploaded by git cl split.
      
      R=rdevlin.cronin@chromium.org
      
      Change-Id: I011ff9c037debc4092850caff94f52f4d7667ea0
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733610Reviewed-by: default avatarDevlin <rdevlin.cronin@chromium.org>
      Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684443}
      d372d6a1
    • Brian Sheedy's avatar
      Increase UHD bot timeouts · f75bb60b
      Brian Sheedy authored
      Increases the swarming expiration and overall builder execution timeout
      for Win10 FYI x64 Release (Intel UHD 630) since only having one device
      is causing shard timeouts on heavily sharded tests and the builder is
      getting dangerously close to its current 6 hour timeout.
      
      Bug: 986939
      Change-Id: I30f01c869b405cea3aae0e11b09f0d81769d62e6
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1739590
      Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
      Commit-Queue: Kenneth Russell <kbr@chromium.org>
      Auto-Submit: Brian Sheedy <bsheedy@chromium.org>
      Reviewed-by: default avatarKenneth Russell <kbr@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684442}
      f75bb60b
    • K Moon's avatar
      Split options from chrome_pdf::DocumentLayout · eb9e000c
      K Moon authored
      Due to the loose, asynchronous coupling between the C++ and JavaScript
      portions of the layout code, we need to pass certain layout "options"
      (such as the default page orientation) back and forth by value.
      
      As a result, it makes sense to have a separate Options class to hold
      these settings, which then can be used to recalculate the layout.
      
      The expected layout lifecycle eventually should look like this:
      1. Update desired layout options one or more times.
      2. Estimate layout size with new layout options.
      3. Send options and estimated size to JavaScript.
      4. Receive updated options from JavaScript.
      5. Apply final options to current layout.
      6. Repaint using updated layout.
      
      As a side effect of this change, I added the desired_layout_options_
      field to PDFiumEngine. This new field holds the mutable state about
      page orientation that was split off into DocumentLayout::Options.
      
      Miscellaneous changes:
      * Revised some of the API comments for DocumentLayout
      * Eliminated need for unsigned math by replacing -1 with +3 (mod 4)
      * DocumentLayout no longer needs to be copyable, so it isn't
      
      Bug: 885110
      Change-Id: I89714c4c2cba6c0ab354c0696ec3943327c979d0
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733795
      Commit-Queue: K Moon <kmoon@chromium.org>
      Reviewed-by: default avatarLei Zhang <thestig@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684441}
      eb9e000c
    • John Abd-El-Malek's avatar
      Remove some dead code in devtools for old loading path. · f2ea3ba5
      John Abd-El-Malek authored
      Bug: 934009
      Change-Id: I859a008b9a68313d3d0479225d20b2b23acf4de4
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1738667
      Commit-Queue: John Abd-El-Malek <jam@chromium.org>
      Auto-Submit: John Abd-El-Malek <jam@chromium.org>
      Reviewed-by: default avatarAndrey Kosyakov <caseq@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684440}
      f2ea3ba5
    • chromium-autoroll's avatar
      Roll src/third_party/perfetto 600679a1c326..4ec51d883391 (1 commits) · 1a0997e0
      chromium-autoroll authored
      https://android.googlesource.com/platform/external/perfetto.git/+log/600679a1c326..4ec51d883391
      
      git log 600679a1c326..4ec51d883391 --date=short --no-merges --format='%ad %ae %s'
      2019-08-06 fmayer@google.com Merge "Add nogncheck to conditional include."
      
      Created with:
        gclient setdep -r src/third_party/perfetto@4ec51d883391
      
      The AutoRoll server is located here: https://autoroll.skia.org/r/perfetto-chromium-autoroll
      
      Documentation for the AutoRoller is here:
      https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
      
      If the roll is causing failures, please contact the current sheriff, who should
      be CC'd on the roll, and stop the roller if necessary.
      
      
      TBR=perfetto-bugs@google.com
      
      Bug: None
      Change-Id: I7eaa4ec19b4d18f4a3dc97c6ee813c9a9953c99d
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1738999Reviewed-by: default avatarchromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
      Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
      Cr-Commit-Position: refs/heads/master@{#684439}
      1a0997e0
    • Sami Kyostila's avatar
      chrome/browser/subresource_filter: Always specify thread affinity when posting tasks · fda131a0
      Sami Kyostila authored
      *** Note: There is no behavior change from this patch. ***
      
      The PostTask APIs will shortly be changed to require all tasks to explicitly
      specify their thread affinity, i.e., whether the task should run on the thread
      pool or a specific named thread such as a BrowserThread. This patch updates all
      call sites with thread affinity annotation. We also remove the "WithTraits"
      suffix to make the call sites more readable.
      
      Before:
      
          // Thread pool task.
          base::PostTaskWithTraits(FROM_HERE, {...}, ...);
      
          // UI thread task.
          base::PostTaskWithTraits(FROM_HERE, {BrowserThread::UI, ...}, ...);
      
      After:
      
          // Thread pool task.
          base::PostTask(FROM_HERE, {base::ThreadPool(), ...}, ...);
      
          // UI thread task.
          base::PostTask(FROM_HERE, {BrowserThread::UI, ...}, ...);
      
      This patch was semi-automatically prepared with these steps:
      
          1. Patch in https://crrev.com/c/1635827 to make thread affinity a build-time
             requirement.
          2. Run an initial pass with a clang rewriter:
             https://chromium-review.googlesource.com/c/chromium/src/+/1635623
          3. ninja -C out/Debug | grep 'requested here' | cut -d: -f1-3 | sort | \
                 uniq > errors.txt
          4. while read line; do
               f=$(echo $line | cut -d: -f 1)
               r=$(echo $line | cut -d: -f 2)
               c=$(echo $line | cut -d: -f 3)
               sed -i "${r}s/./&base::ThreadPool(),/$c" $f
             done < errors.txt
          5. GOTO 3 until build succeeds.
          6. Remove the "WithTraits" suffix from task API call sites:
      
             $ tools/git/mffr.py -i <(cat <<EOF
             [
               ["PostTaskWithTraits",
                "PostTask"],
               ["PostDelayedTaskWithTraits",
                "PostDelayedTask"],
               ["PostTaskWithTraitsAndReply",
                "PostTaskAndReply"],
               ["CreateTaskRunnerWithTraits",
                "CreateTaskRunner"],
               ["CreateSequencedTaskRunnerWithTraits",
                "CreateSequencedTaskRunner"],
               ["CreateUpdateableSequencedTaskRunnerWithTraits",
                "CreateUpdateableSequencedTaskRunner"],
               ["CreateSingleThreadTaskRunnerWithTraits",
                "CreateSingleThreadTaskRunner"],
               ["CreateCOMSTATaskRunnerWithTraits",
                "CreateCOMSTATaskRunner"]
             ]
             EOF
             )
      
      This CL was uploaded by git cl split.
      
      R=battre@chromium.org
      
      Bug: 968047
      Change-Id: Ia14e3392662a15f96dc0675265f93397cf5a22f4
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1739813
      Auto-Submit: Sami Kyöstilä <skyostil@chromium.org>
      Reviewed-by: default avatarDominic Battré <battre@chromium.org>
      Commit-Queue: Dominic Battré <battre@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684438}
      fda131a0
    • Sami Kyostila's avatar
      chrome/browser/service_process: Always specify thread affinity when posting tasks · bccfc838
      Sami Kyostila authored
      *** Note: There is no behavior change from this patch. ***
      
      The PostTask APIs will shortly be changed to require all tasks to explicitly
      specify their thread affinity, i.e., whether the task should run on the thread
      pool or a specific named thread such as a BrowserThread. This patch updates all
      call sites with thread affinity annotation. We also remove the "WithTraits"
      suffix to make the call sites more readable.
      
      Before:
      
          // Thread pool task.
          base::PostTaskWithTraits(FROM_HERE, {...}, ...);
      
          // UI thread task.
          base::PostTaskWithTraits(FROM_HERE, {BrowserThread::UI, ...}, ...);
      
      After:
      
          // Thread pool task.
          base::PostTask(FROM_HERE, {base::ThreadPool(), ...}, ...);
      
          // UI thread task.
          base::PostTask(FROM_HERE, {BrowserThread::UI, ...}, ...);
      
      This patch was semi-automatically prepared with these steps:
      
          1. Patch in https://crrev.com/c/1635827 to make thread affinity a build-time
             requirement.
          2. Run an initial pass with a clang rewriter:
             https://chromium-review.googlesource.com/c/chromium/src/+/1635623
          3. ninja -C out/Debug | grep 'requested here' | cut -d: -f1-3 | sort | \
                 uniq > errors.txt
          4. while read line; do
               f=$(echo $line | cut -d: -f 1)
               r=$(echo $line | cut -d: -f 2)
               c=$(echo $line | cut -d: -f 3)
               sed -i "${r}s/./&base::ThreadPool(),/$c" $f
             done < errors.txt
          5. GOTO 3 until build succeeds.
          6. Remove the "WithTraits" suffix from task API call sites:
      
             $ tools/git/mffr.py -i <(cat <<EOF
             [
               ["PostTaskWithTraits",
                "PostTask"],
               ["PostDelayedTaskWithTraits",
                "PostDelayedTask"],
               ["PostTaskWithTraitsAndReply",
                "PostTaskAndReply"],
               ["CreateTaskRunnerWithTraits",
                "CreateTaskRunner"],
               ["CreateSequencedTaskRunnerWithTraits",
                "CreateSequencedTaskRunner"],
               ["CreateUpdateableSequencedTaskRunnerWithTraits",
                "CreateUpdateableSequencedTaskRunner"],
               ["CreateSingleThreadTaskRunnerWithTraits",
                "CreateSingleThreadTaskRunner"],
               ["CreateCOMSTATaskRunnerWithTraits",
                "CreateCOMSTATaskRunner"]
             ]
             EOF
             )
      
      This CL was uploaded by git cl split.
      
      R=rbpotter@chromium.org
      
      Bug: 968047
      Change-Id: I5ec1af17a9d1408c6dc656abc9c44a5fcd47bb74
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1739866
      Auto-Submit: Sami Kyöstilä <skyostil@chromium.org>
      Reviewed-by: default avatarLei Zhang <thestig@chromium.org>
      Commit-Queue: Lei Zhang <thestig@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684437}
      bccfc838
    • manuk's avatar
      [chrome://omnibox]: Preserve whitespace in table. · b011a4f1
      manuk authored
      Whitespace is important for inline autocomplete, and possibly other fields.
      
      Change-Id: I8dfcb1f2140e20b6d3365f72b9fd832b8eba9303
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1739325Reviewed-by: default avatarTommy Li <tommycli@chromium.org>
      Commit-Queue: manuk hovanesian <manukh@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684436}
      b011a4f1
    • chromium-autoroll's avatar
      Roll src/third_party/angle 99f494e42246..6201d134b3bb (1 commits) · 53929246
      chromium-autoroll authored
      https://chromium.googlesource.com/angle/angle.git/+log/99f494e42246..6201d134b3bb
      
      git log 99f494e42246..6201d134b3bb --date=short --no-merges --format='%ad %ae %s'
      2019-08-06 timvp@google.com Vulkan: Suppress KHR-GLES2 ASTC 3D Texture Tests
      
      Created with:
        gclient setdep -r src/third_party/angle@6201d134b3bb
      
      The AutoRoll server is located here: https://autoroll.skia.org/r/angle-chromium-autoroll
      
      Documentation for the AutoRoller is here:
      https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
      
      If the roll is causing failures, please contact the current sheriff, who should
      be CC'd on the roll, and stop the roller if necessary.
      
      
      CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
      TBR=ynovikov@chromium.org
      
      Bug: None
      Change-Id: I8fb2d5ea7dec802417c8968d3b8f971a6a5a82f7
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1738997Reviewed-by: default avatarchromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
      Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
      Cr-Commit-Position: refs/heads/master@{#684435}
      53929246
    • chromium-internal-autoroll's avatar
      Roll src-internal fc9e4928e7c0..838e9713fa32 (3 commits) · 31e6ae56
      chromium-internal-autoroll authored
      https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/fc9e4928e7c0..838e9713fa32
      
      
      Created with:
        gclient setdep -r src-internal@838e9713fa32
      
      The AutoRoll server is located here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll
      
      Documentation for the AutoRoller is here:
      https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
      
      If the roll is causing failures, please contact the current sheriff, who should
      be CC'd on the roll, and stop the roller if necessary.
      
      
      CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome
      TBR=jbudorick@google.com
      
      Bug: chromium:None,chromium:None,chromium:None
      Change-Id: Ia2e0cb8a2f15aa728c6eb0a28232c634690c7d5f
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1739002Reviewed-by: default avatarchromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
      Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
      Cr-Commit-Position: refs/heads/master@{#684434}
      31e6ae56
    • Sami Kyostila's avatar
      chrome/browser/optimization_guide: Always specify thread affinity when posting tasks · 8623ae8c
      Sami Kyostila authored
      *** Note: There is no behavior change from this patch. ***
      
      The PostTask APIs will shortly be changed to require all tasks to explicitly
      specify their thread affinity, i.e., whether the task should run on the thread
      pool or a specific named thread such as a BrowserThread. This patch updates all
      call sites with thread affinity annotation. We also remove the "WithTraits"
      suffix to make the call sites more readable.
      
      Before:
      
          // Thread pool task.
          base::PostTaskWithTraits(FROM_HERE, {...}, ...);
      
          // UI thread task.
          base::PostTaskWithTraits(FROM_HERE, {BrowserThread::UI, ...}, ...);
      
      After:
      
          // Thread pool task.
          base::PostTask(FROM_HERE, {base::ThreadPool(), ...}, ...);
      
          // UI thread task.
          base::PostTask(FROM_HERE, {BrowserThread::UI, ...}, ...);
      
      This patch was semi-automatically prepared with these steps:
      
          1. Patch in https://crrev.com/c/1635827 to make thread affinity a build-time
             requirement.
          2. Run an initial pass with a clang rewriter:
             https://chromium-review.googlesource.com/c/chromium/src/+/1635623
          3. ninja -C out/Debug | grep 'requested here' | cut -d: -f1-3 | sort | \
                 uniq > errors.txt
          4. while read line; do
               f=$(echo $line | cut -d: -f 1)
               r=$(echo $line | cut -d: -f 2)
               c=$(echo $line | cut -d: -f 3)
               sed -i "${r}s/./&base::ThreadPool(),/$c" $f
             done < errors.txt
          5. GOTO 3 until build succeeds.
          6. Remove the "WithTraits" suffix from task API call sites:
      
             $ tools/git/mffr.py -i <(cat <<EOF
             [
               ["PostTaskWithTraits",
                "PostTask"],
               ["PostDelayedTaskWithTraits",
                "PostDelayedTask"],
               ["PostTaskWithTraitsAndReply",
                "PostTaskAndReply"],
               ["CreateTaskRunnerWithTraits",
                "CreateTaskRunner"],
               ["CreateSequencedTaskRunnerWithTraits",
                "CreateSequencedTaskRunner"],
               ["CreateUpdateableSequencedTaskRunnerWithTraits",
                "CreateUpdateableSequencedTaskRunner"],
               ["CreateSingleThreadTaskRunnerWithTraits",
                "CreateSingleThreadTaskRunner"],
               ["CreateCOMSTATaskRunnerWithTraits",
                "CreateCOMSTATaskRunner"]
             ]
             EOF
             )
      
      This CL was uploaded by git cl split.
      
      R=tbansal@chromium.org
      
      Bug: 968047
      Change-Id: Ib877f88fa151617c51533a56adfa399706db5b0f
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1739708
      Auto-Submit: Sami Kyöstilä <skyostil@chromium.org>
      Reviewed-by: default avatarTarun Bansal <tbansal@chromium.org>
      Commit-Queue: Tarun Bansal <tbansal@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684433}
      8623ae8c
    • redatawfik's avatar
      Checks for credit cards duplication. · 06446923
      redatawfik authored
      1)Checks if there is any saved credit card with the same number.
      2)If there is any, then update saved credit card object with the new data
      update it in DB by PersonalDataManager.
      3)Adds method for updating credit card properties.
      
      Change-Id: Ife5efb47a0bee6439ae05981116bc891b7289f7e
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731839
      Commit-Queue: Reda Tawfik <redatawfik@google.com>
      Reviewed-by: default avatarSergio Collazos <sczs@chromium.org>
      Reviewed-by: default avatarJavier Ernesto Flores Robles <javierrobles@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684432}
      06446923
    • Sami Kyostila's avatar
      chrome/browser/plugins: Always specify thread affinity when posting tasks · ff7dace0
      Sami Kyostila authored
      *** Note: There is no behavior change from this patch. ***
      
      The PostTask APIs will shortly be changed to require all tasks to explicitly
      specify their thread affinity, i.e., whether the task should run on the thread
      pool or a specific named thread such as a BrowserThread. This patch updates all
      call sites with thread affinity annotation. We also remove the "WithTraits"
      suffix to make the call sites more readable.
      
      Before:
      
          // Thread pool task.
          base::PostTaskWithTraits(FROM_HERE, {...}, ...);
      
          // UI thread task.
          base::PostTaskWithTraits(FROM_HERE, {BrowserThread::UI, ...}, ...);
      
      After:
      
          // Thread pool task.
          base::PostTask(FROM_HERE, {base::ThreadPool(), ...}, ...);
      
          // UI thread task.
          base::PostTask(FROM_HERE, {BrowserThread::UI, ...}, ...);
      
      This patch was semi-automatically prepared with these steps:
      
          1. Patch in https://crrev.com/c/1635827 to make thread affinity a build-time
             requirement.
          2. Run an initial pass with a clang rewriter:
             https://chromium-review.googlesource.com/c/chromium/src/+/1635623
          3. ninja -C out/Debug | grep 'requested here' | cut -d: -f1-3 | sort | \
                 uniq > errors.txt
          4. while read line; do
               f=$(echo $line | cut -d: -f 1)
               r=$(echo $line | cut -d: -f 2)
               c=$(echo $line | cut -d: -f 3)
               sed -i "${r}s/./&base::ThreadPool(),/$c" $f
             done < errors.txt
          5. GOTO 3 until build succeeds.
          6. Remove the "WithTraits" suffix from task API call sites:
      
             $ tools/git/mffr.py -i <(cat <<EOF
             [
               ["PostTaskWithTraits",
                "PostTask"],
               ["PostDelayedTaskWithTraits",
                "PostDelayedTask"],
               ["PostTaskWithTraitsAndReply",
                "PostTaskAndReply"],
               ["CreateTaskRunnerWithTraits",
                "CreateTaskRunner"],
               ["CreateSequencedTaskRunnerWithTraits",
                "CreateSequencedTaskRunner"],
               ["CreateUpdateableSequencedTaskRunnerWithTraits",
                "CreateUpdateableSequencedTaskRunner"],
               ["CreateSingleThreadTaskRunnerWithTraits",
                "CreateSingleThreadTaskRunner"],
               ["CreateCOMSTATaskRunnerWithTraits",
                "CreateCOMSTATaskRunner"]
             ]
             EOF
             )
      
      This CL was uploaded by git cl split.
      
      R=tommycli@chromium.org
      
      Bug: 968047
      Change-Id: Id69af8c66a5b886be639f1f22c0dc027a49e7758
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1738702
      Auto-Submit: Sami Kyöstilä <skyostil@chromium.org>
      Reviewed-by: default avatarTommy Li <tommycli@chromium.org>
      Commit-Queue: Sami Kyöstilä <skyostil@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684431}
      ff7dace0
    • John Abd-El-Malek's avatar
      Remove some kNetworkService checks in the code. · 301d265e
      John Abd-El-Malek authored
      Bug: 934009
      Change-Id: If1af2ec4d66ead9c3fa2f7f36ccabfb726bbec7d
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1739110
      Commit-Queue: John Abd-El-Malek <jam@chromium.org>
      Commit-Queue: Clark DuVall <cduvall@chromium.org>
      Auto-Submit: John Abd-El-Malek <jam@chromium.org>
      Reviewed-by: default avatarClark DuVall <cduvall@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684430}
      301d265e
    • Sami Kyostila's avatar
      chrome/browser/spellchecker: Always specify thread affinity when posting tasks · 3cd045bd
      Sami Kyostila authored
      *** Note: There is no behavior change from this patch. ***
      
      The PostTask APIs will shortly be changed to require all tasks to explicitly
      specify their thread affinity, i.e., whether the task should run on the thread
      pool or a specific named thread such as a BrowserThread. This patch updates all
      call sites with thread affinity annotation. We also remove the "WithTraits"
      suffix to make the call sites more readable.
      
      Before:
      
          // Thread pool task.
          base::PostTaskWithTraits(FROM_HERE, {...}, ...);
      
          // UI thread task.
          base::PostTaskWithTraits(FROM_HERE, {BrowserThread::UI, ...}, ...);
      
      After:
      
          // Thread pool task.
          base::PostTask(FROM_HERE, {base::ThreadPool(), ...}, ...);
      
          // UI thread task.
          base::PostTask(FROM_HERE, {BrowserThread::UI, ...}, ...);
      
      This patch was semi-automatically prepared with these steps:
      
          1. Patch in https://crrev.com/c/1635827 to make thread affinity a build-time
             requirement.
          2. Run an initial pass with a clang rewriter:
             https://chromium-review.googlesource.com/c/chromium/src/+/1635623
          3. ninja -C out/Debug | grep 'requested here' | cut -d: -f1-3 | sort | \
                 uniq > errors.txt
          4. while read line; do
               f=$(echo $line | cut -d: -f 1)
               r=$(echo $line | cut -d: -f 2)
               c=$(echo $line | cut -d: -f 3)
               sed -i "${r}s/./&base::ThreadPool(),/$c" $f
             done < errors.txt
          5. GOTO 3 until build succeeds.
          6. Remove the "WithTraits" suffix from task API call sites:
      
             $ tools/git/mffr.py -i <(cat <<EOF
             [
               ["PostTaskWithTraits",
                "PostTask"],
               ["PostDelayedTaskWithTraits",
                "PostDelayedTask"],
               ["PostTaskWithTraitsAndReply",
                "PostTaskAndReply"],
               ["CreateTaskRunnerWithTraits",
                "CreateTaskRunner"],
               ["CreateSequencedTaskRunnerWithTraits",
                "CreateSequencedTaskRunner"],
               ["CreateUpdateableSequencedTaskRunnerWithTraits",
                "CreateUpdateableSequencedTaskRunner"],
               ["CreateSingleThreadTaskRunnerWithTraits",
                "CreateSingleThreadTaskRunner"],
               ["CreateCOMSTATaskRunnerWithTraits",
                "CreateCOMSTATaskRunner"]
             ]
             EOF
             )
      
      This CL was uploaded by git cl split.
      
      R=rouslan@chromium.org
      
      Bug: 968047
      Change-Id: I695547fcd8f3859e16252bf24b8e78d6374ede4c
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1739867
      Auto-Submit: Sami Kyöstilä <skyostil@chromium.org>
      Reviewed-by: default avatarRouslan Solomakhin <rouslan@chromium.org>
      Commit-Queue: Sami Kyöstilä <skyostil@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684429}
      3cd045bd
    • Benjamin Beaudry's avatar
      Changed loop var type from size_t to int · 74a89b88
      Benjamin Beaudry authored
      The problem was here:
      
      for (size_t i = children().size() - 1; i >= 0; --i) {
      
      The loop variable |size_t i| was of an unsigned int type, so |i >= 0|
      was always true.
      
      Repro on Windows by exploring the tree with Inspect on the link provided
      in the crbug description.
      
      Bug: 988153
      Change-Id: I1cae093da68f12ed1630a568ec7529703c73cf89
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1737870
      Commit-Queue: Benjamin Beaudry <benjamin.beaudry@microsoft.com>
      Reviewed-by: default avatarAaron Leventhal <aleventhal@chromium.org>
      Reviewed-by: default avatarNektarios Paisios <nektar@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684428}
      74a89b88
    • Michael Thiessen's avatar
      Fix snav-focusless-fullscreen-video.html on mac · 15b75cab
      Michael Thiessen authored
      This is a speculative fix.
      
      Bug: 979565
      Change-Id: I140d9a3fa2334f7137e1491c40c61d96bcded8b1
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1729922
      Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
      Reviewed-by: default avatarDavid Bokan <bokan@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684427}
      15b75cab
    • Ian Kilpatrick's avatar
      [LayoutNG] Allow clearance as a valid value in the new-fc DCHECK. · 171133bf
      Ian Kilpatrick authored
      Patch:
      https://chromium-review.googlesource.com/c/chromium/src/+/1692627
      
      Made us consider inline-level OOF-positioned nodes as adjoining, as
      their static-position depends on where other floats are placed.
      
      During the first pass the BFC block-offset gets resolved here:
      https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/layout/ng/ng_block_layout_algorithm.cc?l=986&rcl=e6157bb7afb778d5c15bb2bb09a457d9632151da
      
      This aborts as it has an adjoining inline-OOF, and *doesn't* resolve
      the BFC block-offset at |child_bfc_offset_estimate| instead applying
      clearance.
      
      Upon the second pass we now hit the DCHECK as neither of the options
      has clearance applied.
      
      Bug: 987004
      Change-Id: I2634d56726a4664c869b2ecfa1e7a8a13458e78f
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731917
      Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
      Reviewed-by: default avatarMorten Stenshorne <mstensho@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684426}
      171133bf
    • Sami Kyostila's avatar
      chrome/browser/policy: Always specify thread affinity when posting tasks · 03efa572
      Sami Kyostila authored
      *** Note: There is no behavior change from this patch. ***
      
      The PostTask APIs will shortly be changed to require all tasks to explicitly
      specify their thread affinity, i.e., whether the task should run on the thread
      pool or a specific named thread such as a BrowserThread. This patch updates all
      call sites with thread affinity annotation. We also remove the "WithTraits"
      suffix to make the call sites more readable.
      
      Before:
      
          // Thread pool task.
          base::PostTaskWithTraits(FROM_HERE, {...}, ...);
      
          // UI thread task.
          base::PostTaskWithTraits(FROM_HERE, {BrowserThread::UI, ...}, ...);
      
      After:
      
          // Thread pool task.
          base::PostTask(FROM_HERE, {base::ThreadPool(), ...}, ...);
      
          // UI thread task.
          base::PostTask(FROM_HERE, {BrowserThread::UI, ...}, ...);
      
      This patch was semi-automatically prepared with these steps:
      
          1. Patch in https://crrev.com/c/1635827 to make thread affinity a build-time
             requirement.
          2. Run an initial pass with a clang rewriter:
             https://chromium-review.googlesource.com/c/chromium/src/+/1635623
          3. ninja -C out/Debug | grep 'requested here' | cut -d: -f1-3 | sort | \
                 uniq > errors.txt
          4. while read line; do
               f=$(echo $line | cut -d: -f 1)
               r=$(echo $line | cut -d: -f 2)
               c=$(echo $line | cut -d: -f 3)
               sed -i "${r}s/./&base::ThreadPool(),/$c" $f
             done < errors.txt
          5. GOTO 3 until build succeeds.
          6. Remove the "WithTraits" suffix from task API call sites:
      
             $ tools/git/mffr.py -i <(cat <<EOF
             [
               ["PostTaskWithTraits",
                "PostTask"],
               ["PostDelayedTaskWithTraits",
                "PostDelayedTask"],
               ["PostTaskWithTraitsAndReply",
                "PostTaskAndReply"],
               ["CreateTaskRunnerWithTraits",
                "CreateTaskRunner"],
               ["CreateSequencedTaskRunnerWithTraits",
                "CreateSequencedTaskRunner"],
               ["CreateUpdateableSequencedTaskRunnerWithTraits",
                "CreateUpdateableSequencedTaskRunner"],
               ["CreateSingleThreadTaskRunnerWithTraits",
                "CreateSingleThreadTaskRunner"],
               ["CreateCOMSTATaskRunnerWithTraits",
                "CreateCOMSTATaskRunner"]
             ]
             EOF
             )
      
      This CL was uploaded by git cl split.
      
      R=zmin@chromium.org
      
      Bug: 968047
      Change-Id: I5af561f465c55acc9b49898abe8051f475f1f873
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1739826
      Auto-Submit: Sami Kyöstilä <skyostil@chromium.org>
      Reviewed-by: default avatarOwen Min <zmin@chromium.org>
      Commit-Queue: Owen Min <zmin@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#684425}
      03efa572