- Suppress "Switch to Tab" button exclusively in @tabs site search context by removing the phone-only `!is_desktop()` restriction.Can we create a new CL for this if this is orthogonal to the crash fix?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +1 |
- Suppress "Switch to Tab" button exclusively in @tabs site search context by removing the phone-only `!is_desktop()` restriction.Can we create a new CL for this if this is orthogonal to the crash fix?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
if (!match.from_keyword ||
match.type != AutocompleteMatchType::OPEN_TAB) {It looks a little weird to me because the condition for this `if` is the same as the condition for the `else if` below. Why should it be structured like so?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +1 |
if (!match.from_keyword ||
match.type != AutocompleteMatchType::OPEN_TAB) {It looks a little weird to me because the condition for this `if` is the same as the condition for the `else if` below. Why should it be structured like so?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
if constexpr (is_android) {
#if BUILDFLAG(IS_ANDROID)Do we need both the if constexpr(is_android) and the BUILDFLAG check? Can we put the
```
if (!match.from_keyword ||
match.type != AutocompleteMatchType::OPEN_TAB) {
```
as part of the if constexpr (is_android) to reduce nesting/make this easier to follow?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +1 |
if constexpr (is_android) {
#if BUILDFLAG(IS_ANDROID)Do we need both the if constexpr(is_android) and the BUILDFLAG check? Can we put the
```
if (!match.from_keyword ||
match.type != AutocompleteMatchType::OPEN_TAB) {
```as part of the if constexpr (is_android) to reduce nesting/make this easier to follow?
thanks! the `BUILDFLAG(IS_ANDROID)` is redundant. Regarding putting the keyword/type check inside if constexpr : The @tabs keyword mode suppression of the action button is needed for both Android and Desktop (so that we don't show the redundant "Switch to Tab" button on either platform in keyword mode).
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +1 |
if constexpr (is_android) {
#if BUILDFLAG(IS_ANDROID)ben chinDo we need both the if constexpr(is_android) and the BUILDFLAG check? Can we put the
```
if (!match.from_keyword ||
match.type != AutocompleteMatchType::OPEN_TAB) {
```as part of the if constexpr (is_android) to reduce nesting/make this easier to follow?
thanks! the `BUILDFLAG(IS_ANDROID)` is redundant. Regarding putting the keyword/type check inside if constexpr : The @tabs keyword mode suppression of the action button is needed for both Android and Desktop (so that we don't show the redundant "Switch to Tab" button on either platform in keyword mode).
Ah ... looks like even though if constexpr (is_android) discards the execution branch on desktop, the compiler still type-checks the discarded branch on non-Android platforms so we still need it
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |