sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: create-react-app
Issue: Provide option to set transpile target ES version
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

<!--
  Provide a clear and concise description of what the problem is.
  For example, "I'm always frustrated when..."
-->

Currently CRA transpiles to ES5, but ES2017 has almost 95% browser support now. So shipping a ES2017 Module with `<script type="module">` will result in reduced bundle size and faster performance

### Describe the solution you'd like

<!--
  Provide a clear and concise description of what you want to happen.
-->

Provide option to set target ES version

### Describe alternatives you've considered

<!--
  Let us know about other solutions you've tried or researched.
-->

Other option seems to be ejecting.

### Additional context

<!--
  Is there anything else you can add about the proposal?
  You might want to link to related issues here, if you haven't already.
-->

-
Repository: PowerToys
Issue: Re-enable win-app-driver 
Labels: Area-Build

It's being disabled from a default build configuration due to https://github.com/microsoft/PowerToys/pull/8412#issuecomment-742416712. We need to re-enable it once the build farm is fixed.
Repository: ant-design
Issue: Descriptions.Item中span属性目前支持包含列的数量，是否能支持包含行的数量？
Labels: Inactive

- [ ] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### What problem does this feature solve?
增强易用性，解决多行合并显示

### What does the proposed API look like?
span={row:1,col:1}


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: vscode
Issue: can't connect to extensions marketplace
Labels: bug,proxy

Issue Type: <b>Bug</b>

extensions tab rep message "We cannot connect to the Extensions marketplace at this time, please try again later."

VS Code version: Code 1.51.1 (e5a624b788d92b8d34d1392e4c4d9789406efe8f, 2020-11-10T23:34:32.027Z)
OS version: Windows_NT x64 10.0.19041

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx   (8 x 2096)|
|GPU Status|2d_canvas: enabled<br>flash_3d: enabled<br>flash_stage3d: enabled<br>flash_stage3d_baseline: enabled<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>oop_rasterization: disabled_off<br>opengl: enabled_on<br>protected_video_decode: unavailable_off<br>rasterization: enabled<br>skia_renderer: disabled_off_ok<br>video_decode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|13.94GB (9.26GB free)|
|Process Argv|--crash-reporter-id 716a2efd-7c70-46b1-bf12-42ee7008247e|
|Screen Reader|no|
|VM|0%|
</details>Extensions: none
<!-- generated by issue reporter -->
Repository: pytorch
Issue: Torch abs op crashes on -128 int8 tensor with ASAN
Labels: module: error checking,triaged

## 🐛 Bug

Torch abs op if applied on a int8 tensor with min type value (i.e. -128) leads to a crash with message
```
/var/lib/jenkins/workspace/aten/src/ATen/native/Math.h:1108:10: runtime error: 128 is outside the range of representable values of type 'signed char'
```

## To Reproduce

```python
import torch
print(torch.__version__)
> 1.8.0a0+c60a7ad
x = torch.tensor([-128, ], dtype=torch.int8)
print(x, torch.abs(x))
```

## Expected behavior

Gives output as 
```
print(x, torch.abs(x))
tensor([-128], dtype=torch.int8) tensor([-128], dtype=torch.int8) 
```

## Environment

 - PyTorch Version (e.g., 1.0): 1.8.0a0+c60a7ad
 - OS (e.g., Linux): Linux
 - How you installed PyTorch (`conda`, `pip`, source): source + ASAN
 - Build command you used (if compiling from source): like docker image "pytorch_linux_xenial_py3_clang5_asan_test1"
 - Python version: 3.6
 - CUDA/cuDNN version:
 - GPU models and configuration:
 - Any other relevant information:

## Additional context

https://github.com/pytorch/pytorch/pull/49158
Repository: pytorch
Issue: Looking for a more convenient way to getter value of the upper/lower triangular matrix into 1D
Labels: module: bc-breaking,triaged,module: numpy,needs design,topic: bc breaking

## 🚀 Feature
Looking for a new function like `torch.triu_values` / `torch.tril_values` to gatter the value of the upper/lower triangular matrix into 1D shape more convenient.

## Motivation

When we need gatter the value of an upper/lower triangular matrix into 1D shape, in NumPy way, we can easily use `triu_indices`/`tril_indices` to do it, such:
```
>>> a=np.arange(0,9).reshape(3,3)
>>> a
array([[0, 1, 2],
       [3, 4, 5],
       [6, 7, 8]])
>>> a[np.triu_indices(3)]
array([0, 1, 2, 4, 5, 8])
```
But in PyTorch, It's seem that we can’t get the results by previous way:
```
>>> t=torch.arange(0,9).reshape([3,3])
>>> t
tensor([[0, 1, 2],
        [3, 4, 5],
        [6, 7, 8]])
>>> t[torch.triu_indices(3,3)]
tensor([[[0, 1, 2],
         [0, 1, 2],
         [0, 1, 2],
         [3, 4, 5],
         [3, 4, 5],
         [6, 7, 8]],
        [[0, 1, 2],
         [3, 4, 5],
         [6, 7, 8],
         [3, 4, 5],
         [6, 7, 8],
         [6, 7, 8]]])
```
While I can think of other ways to achieve the purpose, but it's not convenient enough.
```
>>> t[torch.triu_indices(3,3)[0], torch.triu_indices(3,3)[1]]
tensor([0, 1, 2, 4, 5, 8])
```

## Pitch

I was wondering if there was an easier way to do it, or if we could implement a new function like `torch.triu_values` / `torch.tril_values` to get the value of the upper/lower triangular matrix more convenient, Just like:
```
>>> t=torch.arange(0,9).reshape([3,3])
>>> t
tensor([[0, 1, 2],
        [3, 4, 5],
        [6, 7, 8]])
>>> torch.triu_values(t)
tensor([0, 1, 2, 4, 5, 8])
>>> torch.tril_values(t)
tensor([0, 3, 4, 6, 7, 8])
```

## Alternatives
I'd like to work on it if this feature sounds feasible 😄 

cc: @useFinger

cc @ezyang @gchanan @mruberry @rgommers @heitorschueroff
Repository: terminal
Issue: Golden Ratio mode
Labels: Issue-Feature,Area-UserInterface,Product-Terminal

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement

Is there anything akin to the [golden ratio mode](https://github.com/roman/golden-ratio.el) of emacs?  If you have multiple panes open when you move focus to one it will auto resize everything to give it more room. This is particularly nice when working with many panes on a small screen so I don't have to resize them manually when switching around.
<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->
Repository: material-ui
Issue: [Transition] Reveal component, transitions when components scroll into view
Labels: new feature,waiting for 👍,component: transitions

A `Reveal` component that tracks the "visiblity" of an element and triggers a specific transition.

- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.

## Summary 💡

Common use case is to implement a "reveal"-effect when certain elements scroll into view. Since I love working with `@material-ui` and it comes with it's own set of transitions wouldn't it be great to have a `Reveal` components that triggers a certain transition when the element scrolls into view and is compatible with `material-ui/core` Transitions (and react transition group)?

## Examples 🌈

I imagine a `Reveal` component with the following API:

```es6
<Reveal TransitionComponent={Slide} TransitionProps={{direction: "left", timeout: 1000}}>
  <div>Hello World</div>
</Reveal>
```

Of course the `Reveal` component would track elements position via `IntersectionObserver`.

## Motivation 🔦

I know that there are libraries that do this similarly but e.g. `react-reveal` is [not maintained anymore](https://github.com/rnosov/react-reveal/issues/106) or `react-awesome-reveal` comes with its [own solution on building custom transitions](https://github.com/dennismorello/react-awesome-reveal#custom-animations). 

I could contribute a solution by myself if this is interesting at all!
Repository: transformers
Issue: overflow_to_sample_mapping missing in in documentation
Labels: WIP

In the [documentation ]( https://huggingface.co/transformers/master/main_classes/tokenizer.html#transformers.PreTrainedTokenizerFast.__call__)of the fast tokenizer, the `overflow_to_sample_mapping` field is missing.
Instead the `overflowing_tokens`  is listed there, which is only part of  the base tokenizer.
Repository: transformers
Issue: CharacterBERT
Labels: New model

# 🌟 New model addition

## Model description
**CharacterBERT** is a **variant of BERT** that uses a CharacterCNN module **instead of** WordPieces. As a result, the model:
1. Does not require/rely on a WordPiece vocabulary
2. Produces a single embedding for any (reasonable) input token
3. Is more robust to misspellings

Paper: https://www.aclweb.org/anthology/2020.coling-main.609/

<!-- Important information -->

## Open source status

* [x] the model implementation is available: https://github.com/helboukkouri/character-bert
* [x] the model weights are available: https://github.com/helboukkouri/character-bert/blob/main/download.py#L16
* [x] who are the authors: @helboukkouri @osf9018 @Jekub @hiroshinoji @PierreZweigenbaum and Junichi Tsujii

I am willing to work on a PR but I will probably need some guidance 😊
Repository: go
Issue: cmd/go: support `@latest-prerelease` tag
Labels: NeedsInvestigation,FeatureRequest,GoCommand,modules

From https://github.com/golang/go/issues/42545#issuecomment-726264795

**Use case**
We have a group of VSCode plugin users who opted in to use prerelease versions of tools. For the users, this will be convenient. Currently the plugin has its own logic to retrieve the list, parse versions, and choose the highest tagged version (including prerelease), but it would be better if this can be done with `go` command.
Repository: terminal
Issue: Add configurable Pane border _hover_ color
Labels: Area-UserInterface,Product-Terminal,Issue-Task

This month on _"Stealing ideas from the [VsCode release notes](https://code.visualstudio.com/updates/v1_52#_sash-hover-border-color)"_:

![image](https://code.visualstudio.com/assets/updates/1_52/sash.gif)

We don't yet support resizing panes with the mouse (that's #992). We also don't support configuring the pane border color (that's #3061 / #3327). 

BUT WHEN WE DO, it would be cool to have a configurable color for the hover on the pane borders. So you would know when you've got a pane border hovered, and that it's actionable. 

Also neat would be if it had that Fluent "glow"? though I suppose "reveal focus" is "xbox only", so maybe not that.
Repository: angular
Issue: Support children outlet in wildcard route
Labels: area: router,router: config matching/activation/validation,P4

I'm trying to make the following route config work:

```javascript
{
  path: '**',
  component: PageComponent,
  children: [
    {
      path: ':slug',
      outlet: 'section',
      component: SectionComponent
    }
  ]
},
```
And this in the `PageComponent`:

```html
<a [routerLink]="[{ outlets: { section: 'one' } }]">Section One</a>
<router-outlet name="section"></router-outlet>
```

As of Angular 11, the outlet doesn't work under a wildcard. Using `routerLink` in `PageComponent` generates the proper link, but it doesn't navigate anywhere when clicked, meaning the URL doesn't change, and the router-outlet doesn't get populated.

The idea is to have a route with unlimited dynamic nested pages where each page can have a section outlet, like:

`/:page/[:page]/(section:[:slug])`

Could this be supported? Is there any workaround I can use?
Repository: TypeScript
Issue: Incorrect error message when referencing non-existent type
Labels: Bug

**TypeScript Version:** 4.0.5

**Search Terms:** "no exported member"

**Code**

foo.d.ts
```ts
namespace foo.bar {
	export interface I {
		x: string
	}
}
```
foo.js
```js
//@ts-check

/** @type { foo.bar.I } */
var i;

/** @type { foo.bar.X } */
var x;

/** @type { foo.bar.I.y } */
var y;

/** @param { foo.bar.I.x } p */
function f(p) {}
```

jsconfig.json
```json
{
	"exclude": [
	]
}
```
**Expected behavior:**
Should give errors like:
foo.bar doesn't have an exported type X
foo.bar.I is not a namespace
foo.bar.I is not a namespace

**Actual behavior:**
```
foo.js:6:21 - error TS2694: Namespace 'foo.bar' has no exported member 'X'.

6 /** @type { foo.bar.X } */
                      ~

foo.js:9:21 - error TS2694: Namespace 'foo.bar' has no exported member 'I'.

9 /** @type { foo.bar.I.y } */
                      ~

foo.js:12:22 - error TS2694: Namespace 'foo.bar' has no exported member 'I'.

12 /** @param { foo.bar.I.x } p */                  ~
```
**Playground Link:** Wasn't able to figure out how to create a new playground; I did examine the one for issue #27630 which resembles this one ([link](https://www.typescriptlang.org/play?#code/MYewdgzgLgBAbjAvDALAJgNwFgBQUCeADgKYyzJgCuAtgEbEBO2OYAhtcRIa8KWDAG8AvrlCRYccqky4CJeFKp1GzMdHj9k6Zmw5cepOP2GyipKJphL6TXLs7deZYyJx32DgzACygmLhhAmGIAD0IQBlg1CSRpZiDgsIjYOXNY6xUAoNDwyKsPfScXLMCc5JhohVjtEsTclLMqihobeOykvMqjapkcBLK8+0LDYr72+rJGi3SWzLHSjtghx3MXBNxXXAB6LZgAQWAoSlYAGxgASwgYAHkAaQAuGAByKCeYcBP8GAZiADNGK5QEAwViTEgAGhgtEosEuUOI5zAAHMYJQIMQACYgq6guCnSikAAWjGIADpROB1HAAIyxKDMHb7Q7HE6PAAKDBAJEiXxebwxIE4VhAsFCl1g4DBpBeZhAvx8T3JOEZHK5IHRGMefPeYE+3z+ALIwNBqUh0NhV3oiJRaMx2JB8HxRJJSq6aFi3lJ9O2uwOR1OFyud0eAGFWGAwCLUej8noVs8wG9WDjHScCa7KRIAMzpBm+5mndmc7kEBP8wVXSOikLinVS56pOUKpUq4vqzGh8NV6N8Arxp6J+24p0Z8TwFAe0lgPNM-2smBhiNR22xzxOF6D5MOvFpsk+mCq8IarUWN4fL4-f4MQHG+vhrGg5YGM0wwPw609h8pncEmDEn6jlSACsdLTvufoskWXKMKWG7lkK3ZiuokqpA2sryt4ir7oe7aag2g7nvqV43g6qH3g6T68C+Frvsin5Dqmv7-nuOBdAAbJOFjMOBBbzou3a-IiWL2M8cBYcquw4ceolnrqF4GteRrbk61FvladG2l+pGNMxSqoVAtLIHAM4QYWMAAHJ9l4TyYX+W6RnUyR2hwygMDJLaSW20lPGJOp6pehpAspu6qXC6k2hqDGobppjyFA7rIJ6xk8XOb7BguXbLjGlHSpuKapHpUw5hQJm8Y8llxtZtmEvZwIDFAznEK5ZYeQeXkdhlS6wCuOVllFZiFXFE6JVOpVzp2XU9quwyiXl2kkK1UkdT5BFyURgW3j+pDkY+VlUVCr5hQiGmRVuJo6S6sXmCBRlgRJs6QRZe3StVtWOZEjXNSt4mtmq3lGLJ-kKSRw67iCYAPtNKyhZax0RXaZ31jFeBTBxI1GNx92mXxmWwIJENQ9ZYmLe1eE+YD8nEUpoMEjDtHw1pu2VU4yOoWABmxHApIgFyEBjY9FVri9bw1ZWdWLJ9NjudhpNar5hEBYpQU08QdPhfRiO9azjTswlPiklzPOEHzKUsmlDwNhT61K7epoHTR6uaQxWuXSj8js8VZDc7z-NmYLM02SLb31ZLjCWyTf3La8fmUxt82q-balwxrKYuwBV1WFAw361A3vG7784+dHCvA9TUpq8nTua89f6u79R7LZIVuKyDjHbQT50QonR0flXqc19r7tQDdCh5ybWNlU9zPC3ZYvvQ1WIuVLRc-Z5kdk03MfW63W3g5Ddvmknvenf30+1+nbt8FAaP65IY8YEAA))

**Related Issues:** Possibly issue #27630 as mentioned above
Repository: pytorch
Issue: Differentiate between objects with a true `Tensor` type and objects with a default `Tensor` type
Labels: oncall: jit

## 🐛 Bug

We currently set `Tensor` as the default type for untyped variables, but this can be overly restrictive. Perhaps we should allow unannotated `List`s and `Dict`s to be typed based on their first added item. In doing this, we should make sure that we don't inadvertently allow reassignment for `List`s and `Dict`s that have truly been annotated as containing `Tensor` objects.

Suggestion: Use the Tensor `isInferred` flag to check type correctness when an `aten::_set_item` is emitted

## Example

```python
@torch.jit.script
def fn():
    d = {}
    d["foo"] = 1    # throws an error since `d` is `Dict[Tensor, Tensor]`
    return d
```

cc @gmagogsfm
Repository: storybook
Issue: Adding Storybook to my TypeScript React component library makes apps that use the published library crash on webpack compilation due to TS errors
Labels: question / support,react,typescript

I maintain an in-house TypeScript React component library, which is published to a private package repository and used within my company's front-end apps. 

The new features in storybook 6 are amazing and I want to use them in my documentation.

I added storybook to my library, and found that it was pretty easy to set up. 

However, I found that if I `yarn build && yarn link` my library, then `yarn link my-library` into one of my company's frontend apps locally, that frontend app will fail to compile. Unexpected TypeScript errors (i.e., errors that do not come up on a tslint or on tsc) cause webpack to crash. 

They're all something along the lines of 

```
ERROR in VisitsSection.tsx
[tsl] ERROR in VisitsSection.tsx(147,10)
      TS2741: Property 'css' is missing in type '{ children: Element; }' but required in type 'Pick<TableFooterProps, "slot" | "style" | "title" | "children" | "onError" | "classes" | "innerRef" | "testID" | "key" | "color" | "component" | "onBlur" | "onFocus" | ... 246 more ... | "css">'.
```

This error comes up for every single component used from my library in a target app run locally, and it *only* comes up in that app if I my library was built with storybook and its dependencies installed. The same exact library code, before I installed storybook, did not cause this.

I realize this seems quite difficult to reproduce, but does anyone have any hard-won wisdom about issues pertaining to

* using storybook in a react codebase that is not, itself, already a web app (just a published library?)
* conflicts with different `@types/react` versions that could be caused by storybook?
* just in general any gotchas or pro-tips about implementing storybook in a pre-existing TypeScript React codebase?

**Update**

I did a little bit of investigating in my build results, and it seems that the triple-slash type reference for react is missing in my `*.d.ts` files when I have storybook installed. A comparison:

```ts
// ValueContainer.d.ts build result file before installing storybook

/// <reference types="react" />
import { ValueContainerProps } from './ValueContainer.model';
declare function ValueContainer(props: ValueContainerProps): JSX.Element;
export default ValueContainer;
```

```ts
// ValueContainer.d.ts build result file after installing storybook

import { ValueContainerProps } from './ValueContainer.model';
declare function ValueContainer(props: ValueContainerProps): JSX.Element;
export default ValueContainer;
```

Still not sure what could have been changed about my build process by storybook to cause the triple-slash refs not to be inserted.
Repository: flutter
Issue: Proposal to add text outline / stroke effect to TextField and TextFormField widget
Labels: c: new feature,framework,engine,a: typography,c: proposal,P3,team-engine,triaged-engine

Apart from the fact the actual text outline is missing but was "fixed" by telling people to place two text widgets into a stack widget, there's no text outline option for TextField and TextFormField widgets.
Repository: rust
Issue: Constantly receiving `Undefined symbols for architecture x86_64`
Labels: A-linkage,O-wasm,C-bug

I'm constantly receiving `Undefined symbols for architecture x86_64` when running `cargo build/test/check/run`. It happens in projects with a variety of targets (wasm/arm/x86/musl). I can make it temporarily go away when switching my default from stable to nightly, but the issues will resume and I'll have to switch back.

The stack traces I'm receiving are especially nasty:

```
  = note: Undefined symbols for architecture x86_64:
            "syn::punctuated::Pair$LT$T$C$P$GT$::into_tuple::h7650409a1648a723", referenced from:
                syn::gen::visit::visit_angle_bracketed_generic_arguments::h17c66b0edf1406c7 in libwasm_bindgen_macro_support-62eb06893cdd5d5c.rlib(wasm_bindgen_macro_support-62eb06893cdd5d5c.wasm_bindgen_macro_support.6s2lo5z5-cgu.0.rcgu.o)
            "syn::punctuated::Pair$LT$T$C$P$GT$::into_tuple::h9e3a72cf01e3775d", referenced from:
                syn::gen::visit::visit_lifetime_def::h12b1c6ddc1818ba7 in libwasm_bindgen_macro_support-62eb06893cdd5d5c.rlib(wasm_bindgen_macro_support-62eb06893cdd5d5c.wasm_bindgen_macro_support.6s2lo5z5-cgu.0.rcgu.o)
                syn::gen::visit::visit_predicate_lifetime::h90dd0a0408d5ad94 in libwasm_bindgen_macro_support-62eb06893cdd5d5c.rlib(wasm_bindgen_macro_support-62eb06893cdd5d5c.wasm_bindgen_macro_support.6s2lo5z5-cgu.0.rcgu.o)
....
....
"_$LT$alloc..raw_vec..RawVec$LT$T$C$A$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::hdf6534d4c8747194", referenced from:
                core::ptr::drop_in_place::h3e5e73dbe7eaf673 in libwasm_bindgen_macro_support-62eb06893cdd5d5c.rlib(wasm_bindgen_macro_support-62eb06893cdd5d5c.wasm_bindgen_macro_support.6s2lo5z5-cgu.6.rcgu.o)
          ld: symbol(s) not found for architecture x86_64
          clang: error: linker command failed with exit code 1 (use -v to see invocation)
         
```

Unfortunately, `cargo clean` doesn't help, nor does switching from debug to release.
Repository: pytorch
Issue: [TorchScipt] Custom Objects C++ API
Labels: oncall: jit

## 🐛 Bug: Creating TorchScript Objects in C++

@samster25  pointed out in a presentation that there is no public  API for creating a User-defined Class (class defined in python) or named tuple in the C++ API. 

More generally, the C++ API is hard to use. In the past, we have considered having a separate set of user-exposed IValue bindings. We could also consider having a tutorial for doing common things in JIT documentation. 

cc @gmagogsfm @SplitInfinity who has been working on improving custom classes support
Repository: pytorch
Issue: [FX] Update `placeholder` docs to better reflect the role of `node` and `target`
Labels: triaged,module: fx

https://github.com/pytorch/pytorch/blob/15200e385a764721000f1dfadbcaf42c328bafdd/torch/fx/node.py#L34

`node` and `target` actually have different behavior. `target` is the stable, user-visible name (and may contain `*` or `**` as in `*args` or `**kwargs`), whereas name is a garden-variety SSA unique name. We should update the docs to indicate so

cc @ezyang
Repository: flutter
Issue: GBoard's contact suggest feature does not show up for Flutter text input
Labels: a: text input,framework,engine,customer: money (g3),P2,team-engine,triaged-engine

Internal: b/348443241

GBoard allows users to enable contact suggestions which take effect when someone is entering a name or a phone number. It seems this works for Web and Android native fields but not for Flutter. From customer:

> We already tried `TextField` with keyboardType: TextInputType.phone, number, email, etc but still cannot see the suggestion chip.
Repository: flutter
Issue: GBoard's suggestion strip messes up the window display metrics
Labels: framework,customer: money (g3),P2,team-framework,triaged-framework

See b/174549158

Related to #72172.

When the suggestion strip shows on GBoard, the app header is pushed into the safe area. Since Flutter's own text field does not allow us to use this feature, there's no simple repro. It can be reproduced by adding a Webview in Scaffold `body` then going to a webpage that allows you to enter contacts with the contact suggest feature enabled.