WordPress / gutenberg

The Block Editor project for WordPress and beyond. Plugin is available from the official repository.
https://wordpress.org/gutenberg/
Other
10.49k stars 4.18k forks source link

IE11 Copy and pasting fails #8359

Closed jrmd closed 4 years ago

jrmd commented 6 years ago

Describe the bug When trying to copy and paste content into the editor nothing happens, in console it shows nothing as the input and nothing as the output

To Reproduce Steps to reproduce the behavior:

  1. Create a post in IE11
  2. Copy some content from a website
  3. Try paste it into the editor

Expected behavior This should paste the desired content into the editor

Screenshots Screen cast of this happening (Droplr link)

Desktop (please complete the following information):

Additional context

Clorith commented 6 years ago

I can confirm this behavior, with debugging enabled I've got a few warnings.

Before pasting:

Warning: Unsafe lifecycle methods were found within a strict-mode tree:
    in Unknown (created by e)
    in e (created by RemountOnPropChange(e))
    in RemountOnPropChange(e)
    in WithSelect(Component)

componentWillReceiveProps: Please update the following components to use static getDerivedStateFromProps instead: t

Learn more about this warning here:
https://fb.me/react-strict-mode-warnings

Not sure if it's related, but loading up the Gutenberg editor also throws a console error in IE11, which looks similar so might be related?

Warning: Unsafe lifecycle methods were found within a strict-mode tree:
    in Unknown (created by e)
    in e (created by RemountOnPropChange(e))
    in RemountOnPropChange(e)
    in WithSelect(Component)

componentWillReceiveProps: Please update the following components to use static getDerivedStateFromProps instead: t

componentWillUpdate: Please update the following components to use componentDidUpdate instead: t

Learn more about this warning here:
https://fb.me/react-strict-mode-warnings
IreneStr commented 5 years ago

This bug is still present (in WP5.0 RC1). I also get an 'Updating failed' and 'Unhandled promise rejection' that might or might not be related. image 6

To clarify:

ellatrix commented 4 years ago

Is this still an issue with Gutenberg 7.1?

Clorith commented 4 years ago

I can't replicate this any more, so I suspect it's been resolved in a preceding commit somewhere :)

pento commented 4 years ago

Closing this, it appears to have been fixed at some point in the past.