PR #19108 caused some Suspense-related DevTools regressions (more info available on #19368) which we did not catch because of the fact that DevTools tests are only run against the version of React in master.

We should follow the precedent of the regression fixtures tests and have CI run DevTools tests against multiple

This is a good first PR!

We should add some tests to cover #7036. They should cover both JavaScript and TypeScript support.

They can probably be added to test/fixtures.

• I have searched the issues of this repository and believe that this is not a duplicate.

Reproduction link

Steps to reproduce

Project Too Large to isolate

What is exp

I am unable to click the scrollbar on the virtualized autocomplete.

• The issue is present in the latest release.
• I have searched the issues of this repository and believe that this is not a duplicate.

Curre

Feature request

Is your feature request related to a problem? Please describe.

The examples/with-emotion example is using Emotion 10.

According to the Emotion SSR docs, the _document.js file is no longer required:

![Screen Shot 2020-10-05 at 15 04 17](https://user-images.githubusercontent.com/1935696/95082974-28356a00-071c-11eb-9793-29bc2b

Describe the bug
With multiple pure-documentation MDX docs, the scroll position of the preview window does not reset when switching between docs.

To Reproduce
Steps to reproduce the behavior:

1. Create at least two MDX docs without stories, with content long enough to result in a scroll bar.
2. Select the first doc in the sidebar.
3. Scroll down the first document.
4. Select the

Description

I have a onPreRouteUpdate and a onRouteUpdate in gatsby-browser, both log to the console. I also have a layout component that logs on render and wrapped via gatsby-browsers wrapPageElement.

On initial render, the logging order is: onPreRouteUpdate > layout > onRouteUpdate
On subsequent navigations, the logging order is: layout > onPreRouteUpdate > onRouteUpdate

This

any plans for a Linux ARM build? if nobody else is on it or has attempted it, i can give it a try.

Is your feature request related to a problem? Please describe.
I have a lot of trouble distinguishing between the shades of green signifying a running vs successful query in sqllab.

Describe the solution you'd like
Ideally these would be two different colors for running vs successful. Maybe yellow and green respectively?

Describe alternatives you've considered
If there isn't

🚀 Feature request

Current Behavior

The type ErrorMessage doesn't have an id property.

Desired Behavior

It'd be nice id?: string would be added to the type ErrorMessage and set on the outermost component that serves as error message.

Suggested Solution

Add id={this.props.id} to the outer component in ErrorMessage.

Who does this impact? Who is this

I want to know if there is any implementation of the demo https://sheetjs.com/demo/modify.html in react. I am new to React and want to implement the similar functionality.