Not compatible to Chrome 90 or older

[guoyunhe]

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and couldn’t find anything (or linked relevant results below)

Affected packages and versions

9.0.1

Link to runnable example

No response

Steps to reproduce

1. Install Chrome 90 or use https://www.browserstack.com/
2. Visit https://remarkjs.github.io/react-markdown/

Expected behavior

Should render

Actual behavior

Nothing render. Console show errors.

Runtime

Other (please specify in steps to reproduce)

Package manager

npm 8

OS

Windows

Build and bundle tools

Webpack

[JounQin]

Chrome 90 is too old, and https://remarkjs.github.io/react-markdown is only for demo usage, I don't get why should we support Chrome 90.

We require ES2022 at b67d714

[github-actions]

Hi team! Could you describe why this has been marked as wontfix?

Thanks,
— bb

[guoyunhe]

@JounQin the project's README claims:

They work in all modern browsers (essentially: everything not IE 11).

The reason why the package is not compatible to Chrome < 93 is that it uses Object.hasOwn. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/hasOwn#browser_compatibility

[JounQin]

They work in all modern browsers (essentially: everything not IE 11).

That depends on what modern means, we can not support Chrome v1.0 of course.

[guoyunhe]

That depends on what modern means, we can not support Chrome v1.0 of course.

You could add more clear definition in README.

[remcohaszing]

This project is compatible with Node.js 16 and greater. That’s an exact definition. We don’t test across a matrix of different browser versions, so we don’t define the exact meaning of modern browser.

If you need to use modern features in an older browser, you can add a polyfill for missing APIs, or transpile modern syntax using Babel.

[JounQin]

You could add more clear definition in README.

Indeed, unified projects basically require non-legacy node versions, but browsers support it's not well defined.

Or maybe that section should just be removed considering #772 (comment) and #804 (comment)

cc @wooorm and @ChristianMurphy

[wooorm]

Object.hasOwn is intentional. Previous versions did not have it. The latest version does.
10 years ago I had browser matrix tests. Browser tests are error prone and don’t add much. Browsers nowadays are evergreen: they automatically update.
That’s why the text in the readme says: “They work in all modern browsers (essentially: everything not IE 11)”.

I don’t think we need to add a definition of every word in the readme. I think that the current description is sufficient.