chore: Move draggable regions implementation from NativeBrowserView into InspectableWebContentsView#35007
Conversation
zcbenz
left a comment
There was a problem hiding this comment.
Can you fix the lint error?
$ node ./script/lint.js && npm run lint:docs
shell/browser/ui/inspectable_web_contents_view.h:76: (cpplint) Add #include <vector> for vector<> [build/include_what_you_use] [4]
shell/browser/ui/inspectable_web_contents_view_mac.h:36: (cpplint) Add #include <vector> for vector<> [build/include_what_you_use] [4]
590e8e8 to
6047cb7
Compare
|
There is still one more lint warning, not sure why it was not showing in the first time. |
6047cb7 to
1a345e2
Compare
|
Sorry, I have troubles to launch lint.js locally on my machine |
|
@daniel-koc can you rebase your PR on the latest from main? Also, can you log out of CircleCI before pushing the commit? Those two things should resolve the CI failures. |
Yes, off course. What do you mean by "log out of CircleCI "? |
…to InspectableWebContentsView The draggable regions implementation is related to WebView, so InspectableWebContentsView is a more appropriate place to put it there. Also, this refactoring will allow the subsequent extension of the WebContentsView API, which will eventually replace BrowserView API.
1a345e2 to
61e679a
Compare
|
Windows CI and Linux CI seem to fail on the goma/setup steps, but it seems like there's a legitimate error in the macOS build: cc @daniel-koc |
|
@erickzhao I'll push the fixup today. The implementation on main changed - so the refactor requires adjustment |
|
Can we close this in favor of #35603? |
|
This PR was originally part of BrowserView refactoring - moving the implementation to WebContentsView. Do we plan to support draggable regions for all WebContentsView in the hierarchy of window's contentView? |
|
@daniel-koc I think the refactoring in this PR is good to have, if you are willing to rebase this PR after merging #35603, then I am good to merge this one. |
|
No Release Notes |
|
Congrats on merging your first pull request! 🎉🎉🎉 |
|
I don't think this was ready to land, it includes an incorrect implementation of UpdateDraggableRegions on Mac. It was not properly updated after #35603 landed. |
|
@daniel-koc for one, this included code for manipulating the child hit testing NSViews on macOS, which is a technique that was obviated by #35603. |
|
I've opened #36230 to address it. |
|
OK, it makes sense. |
…nto InspectableWebContentsView (electron#35007) * hore: Move draggable regions implementation from NativeBrowserView into InspectableWebContentsView The draggable regions implementation is related to WebView, so InspectableWebContentsView is a more appropriate place to put it there. Also, this refactoring will allow the subsequent extension of the WebContentsView API, which will eventually replace BrowserView API. * fix: Lint error * fix: Adjusted owner-window
Description of Change
The draggable regions implementation is related to WebView, so
InspectableWebContentsView is a more appropriate place to put it there.
Also, this refactoring will allow the subsequent extension of the
WebContentsView API, which will eventually replace BrowserView API.
Checklist
npm testpassesRelease Notes
Notes: none