Commit 0205e76d authored by Matthias Körber's avatar Matthias Körber Committed by Chromium LUCI CQ

[Autofill] Remove unintended application of subtoken merge strategy

It is currently not the intention to run the subtoken merge strategy
but due to an additional or statement, this strategy is executed
although it is the intent to only run a token merge strategy when
the back of tokens are equivalent.

This change removes the wrong application.

Bug: 1158810
Change-Id: I08d68818fac1b6a7552f6aa744caca8eed512902
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627315Reviewed-by: default avatarChristoph Schwering <schwering@google.com>
Commit-Queue: Matthias Körber <koerber@google.com>
Auto-Submit: Matthias Körber <koerber@google.com>
Cr-Commit-Position: refs/heads/master@{#842977}
parent 10999591
...@@ -67,8 +67,7 @@ enum MergeMode { ...@@ -67,8 +67,7 @@ enum MergeMode {
kUseNewerIfDifferent = 1 << 5, kUseNewerIfDifferent = 1 << 5,
// If the newer component contains one token more, apply a recursive strategy // If the newer component contains one token more, apply a recursive strategy
// to merge the tokens. // to merge the tokens.
kRecursivelyMergeSingleTokenSubset = kRecursivelyMergeSingleTokenSubset = 1 << 6,
1 << 6 | kRecursivelyMergeTokenEquivalentValues,
// If one is a substring use the most recent one. // If one is a substring use the most recent one.
kUseMostRecentSubstring = 1 << 7, kUseMostRecentSubstring = 1 << 7,
// Merge the child nodes and reformat the node from its children after merge. // Merge the child nodes and reformat the node from its children after merge.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment