Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

slate-dev-environment `HAS_INPUT_EVENTS_LEVEL_2` is bug in chrome@105+ (Slate 0.47)

See original GitHub issue

Description

slate-dev-environment: HAS_INPUT_EVENTS_LEVEL_2 is bug in chrome@105+

Expectation because of : slate-env-bug

Environment

Slate Version: [0.47]
Operating System: [mac m1]
Browser: [Chrome 105.0.5195.52 (x86_64)]

Issue Analytics

State:
Created a year ago
Reactions:6
Comments:6 (1 by maintainers)

Top GitHub Comments

1reaction

gdehmlowcommented, Sep 2, 2022

My team is still in the process of upgrading old slate to new slate (hefty rich text editor), so here’s the super janky fix I’m using temporarily to resolve this issue for our old editor (note that this does cause webpack to complain)

In my package.json:

  "resolutions": {
    "slate-dev-environment": "0.1.4"
  },

Forcing slate-dev-environment to an older version doesn’t export HAS_INPUT_EVENTS_LEVEL_2, which seems to many of the issues related to it. Of course webpack complains with a warning that this isn’t exported.

1reaction

dylanscommented, Sep 2, 2022

Note this does not appear to be an issue with any recent versions of Slate, only with versions released more than 3 years ago. We’ll leave this open so you can sort through it, but Slate won’t be releasing an update to a version this far back.