### Preflight Checklist
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

### Issue Details

* **Electron Version:**
  * 12.0.0-beta.7
* **Operating System:**
  * macOS / Window
* **Last Known Working Electron version:**
  * 8

### Expected Behavior
<!-- A clear and concise description of what you expected to happen. -->
1. Add `<input type="color" />` in HTML code
2. Run the app
3. Click on input - color picker is opening
4. Pick color by Eyedropper
5. Input should be updated by selected color

### Actual Behavior
The eyedropper is not started

### To Reproduce
For reproduce you can use electron fiddle and simply add `<input type="color" />`  in HTML code
 
### Screenshots
![5ZqhvTeI95](https://user-images.githubusercontent.com/8972979/101465241-fa4ceb80-393f-11eb-950f-152f736e127e.gif)


shell/browser/api/electron_api_web_contents.cc
if (!inspectable_ontents_)
    return nullptr;
  return inspectable_ontents_->GetWebContents();
}
content::WebConbContents::GetDevToolsWebContents() const {
  if (!inspectable_ontents_)
    return nullptr;
  return inspectable_ontents_->GetDevToolsWebContents();
}
void WebContents::MarkDestroyed() {
  if (GetAllWebContents().Lookup(id_))
    GetAllWebContents().Remove(id_);
  v8::Isolate* isolate = JavascriptEnvironment::GetIsolate();
  v8::HandleScope scope(isolate);
  v8::Lobject> wrapper;
  if (!GetWrapper(isolate).ToLocal(&wrapper))
    return;
  wrapper->SetAlignedPointerInInternalField(0, nullptr);
}
 There are three ways of destroying a webContents:
 1. call webContents.destroy();
 2. garbage collection;
 3. user closes the window of webContents;
 4. the embedder detaches the frame.
 For webview only #4 will happen, for BrowserWindow both #1 and #3 may
 happen. The #2 should never happen for webContents, because webview is
 managed by GuestViewManager, and BrowserWindow's webContents is managed
 by api::BrowserWindow.
 For #1, the destructor will do the cleanup work and we only need to make