Permission denied to access property "nodeType" on Alt Text (image) editing

[idiazroncero]

Describe the bug
Error when uploading an image using the WYSIWG editor (widget:markdown, body field).
The error happens when you click on the ALT field of the image, (the image uploads correctly).
The error happens using both a gitlab and github backend.
The error is: Error: Permission denied to access property "nodeType""

To Reproduce

• Install a template based on a GitLab / GitHub back-end (I tried both) I used this:
  https://templates.netlify.com/template/eleventy-netlify-boilerplate/
• Login to the admin and edit/create a new post.
• Add an image to the markdown field. Upload a new image and select it.
• Click on the Alt field
• The error happens. Blank screen and message:

"Sorry!
There's been an error - please report it!
Error: Permission denied to access property "nodeType""

Expected behavior
Error doesn't happen.

Applicable Versions:

• Netlify CMS version: 2.0.11
• Git provider: Tried github and gitlab
• OS: macOS Hight Sierra
• Browser version: Firefox 61.0.2
• Node.JS version: 8.11.4

CMS configuration

backend:
  name: git-gateway
  branch: master # Branch to update (optional; defaults to master)
  media_folder: 'static/img' # Media files will be stored in the repo under images/uploads

collections:
  - name: 'blog'
    label: 'Post'
    folder: 'posts'
    create: true
    slug: '{{slug}}'
    fields: 
      - { label: 'Title', name: 'title', widget: 'string' }
      - { label: 'Publish Date', name: 'date', widget: 'datetime' }
      - { label: 'Summary', name: 'summary', widget: 'text' }
      - { label: 'Tags', name: 'tags', widget: 'list', default: ['post'] }
      - { label: 'Body', name: 'body', widget: 'markdown' }
  - name: 'pages'
    label: 'Page'
    folder: 'pages'
    create: false
    slug: '{{slug}}'
    fields:
      - { label: 'Title', name: 'title', widget: 'string' }
      - { label: 'Publish Date', name: 'date', widget: 'datetime' }
      - { label: 'Permalink', name: 'permalink', widget: 'string' }
      - { label: 'Navigation Title', name: 'navtitle', widget: 'string' }
      - { label: 'Tags', name: 'tags', widget: 'hidden', default: 'nav' }
      - { label: 'Body', name: 'body', widget: 'markdown' }

It's the original from the repo

[tech4him1]

I can reproduce this on the CMS demo site in Firefox.

[tomrutgers]

Possibly related to a bug with e.originalTarget in firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=208427

[erquhart]

Looks like:

1. This functionality broke in 2.0.10 (repro), originally giving error: TypeError: i is not a function.
2. Something changed in 2.0.11 (repro) so that the error message reported above shows.

The errors are originating from Slate. I'm betting the original break occurred due to the Slate dependency update that was released in 2.0.10. An issue on their repo shows other users experiencing this in recent months, and one of the commenters opened a Firefox bug report.

It seems this needs to be address within Firefox, but we won't know until someone responds to the bug report.

Update: A reproduction directly in Slate (try changing the Youtube video url by clicking it and then clicking the input that appears): https://www.slatejs.org/#/embeds

[erquhart]

If someone is up for forking the Slate repo and figuring it which commit broke things, that would probably help their team on investigating a fix. I'm guessing it's the slate-react package, as I believe all DOM things happen there, but not certain.

[ghost]

Windows 10 x64, FF 62.00 reporting in. Same issue.

[geonnave]

This issue also happens on Ubuntu 18.04 64-bit, Firefox 63.0 64-bit.

[anderskitson]

Same issue windows 10, firefox

[tech4him1]

See ianstormtaylor/slate#2178.

[GitToby]

same issue with win10 firefox, also with the title edit section too

[danoc]

Seems like the downstream fix has not yet made it into Netlify CMS. Any chance we can get slate-react upgraded? Happy to help if needed.

[erquhart]

This will be fixed with #2828.

[erezrokah]

Closing as fixed (didn't reproduce with Firefox/Chrome). Please comment/re-open if issue persists