[wp-trac] [WordPress Trac] #62297: SCF creates a weird dropzone blackhole for metaboxes

[WordPress Trac]

#62297: SCF creates a weird dropzone blackhole for metaboxes
----------------------------+-----------------------------
 Reporter:  namith.jawahar  |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Editor          |    Version:  6.6.2
 Severity:  major           |   Keywords:
  Focuses:  ui              |
----------------------------+-----------------------------
 SCF creates a weird dropzone blackhole for metaboxes when the classic
 editor is in use or on a custom post type with rest api disabled.

 Anything accidently going into that dropzone wont be recoverable if we
 switch to gutenberg.  The meta box even disappears from the Preferences
 menu.

 Not sure if this should be categorized as a classic editor bug or a
 gutenberg bug or an SCF bug.


 To recreate the bug

 1) Step 1 - With SCF active visit any custom post type with a metabox with
 the classic editor (rest turned off for the post type).  You can also use
 classic editor plugin to reproduce this instead of turning the rest api
 on/off
 2) Step 2 - Drag any metabox and you will see a new drop area above the
 editor beneath the title.
 3) Step 3 - Drop the metabox there.

 Now if you switch to gutenberg (using classic editor or turning on rest
 for the CPT) that metabox will be irrecoverable.  It wont even appear in
 the prefernces menu to turn back on.  Only way to get the metabox is via
 any methos turn off gutnberg, reload the page, visit screen options and
 turn if back on, and then activate gutenberg.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/62297>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform