-
Notifications
You must be signed in to change notification settings - Fork 975
Fixed drag & drop for images and files broken (causes screen to go white) #7266
Comments
File uploading here on GitHub is working fine for me with Brave 0.13.4 on macOS 10.12.x. Have you tried disabling shields? Click the lion icon in the top right and switch Shields to Down. |
I restarted the browser, without change. Tried it one more time and it did. I'm not sure what the reason was. |
This continues to happen for me, terminating the Brave task does the trick, but this is definitely new. |
While this was not observed in prior builds for me, I have noticed it with a local run of e259d61. |
I can't repro using master and it works great with 0.13.4... We can retest once a new preview build is cut. It does fail with 0.13.5 preview 1. Sites which I tried drag and drop using master:
|
Closing- this appears to work great with 0.13.5 preview 3. Let's re-open if it happens again I'll keep the milestone just so we can confirm that it works during testing (if it's already in our test plan, we can remove milestone) |
Re-opening after seeing the issue again in 0.13.5 preview 3 I experienced the problem here on GitHub and I believe I have better repro steps:
|
@bsclifton I tried these steps, but I couldn't reproduce this error. I experience this kind of error already on 0.13.4, but for now I don't have reproduction steps, it happened 3 or 4 times till now. |
Ok I managed to crash it again (0.13.4). I managed to crash it only after brave was running for a long time, the whole day. |
I spent about 90 minutes trying to make this happen (in which I ran into issues caused by the Amazon S3 services being down). Regardless of those, I could not get an error to happen. Everything always worked OK. I looked at crash reports on stats.brave.com and didn't see any reports which I believe were mine OR which had information which could be helpful. Since the steps to repro aren't nailed down, I'm going to push this to 0.13.6. We should definitely keep eyes out for it |
Here's how it happens for me sometimes. I have Google Hangouts in a pinned tab. I open Brave (new session after completely exiting). This doesn't always work, and sometimes it just happens after having Brave open for some time. |
screenshot courtesy of @echosa: |
Reproduces: 0.13.3 (also 0.13.4, 0.13.5, 0.14.0) Does not reproduce: 0.13.2 Conclusive steps to reproduce:
|
Removing all drag and drop handlers completely from our front end still reproduces. So seems like something from the chromium upgrade. |
Verified this does not reproduce on Linux and Windows, it is macOS only. |
This is the commit that introduces the bug: In particular isValidDragTarget returns false but only after having dragged a bookmark or tab or some other UI element from the window. I think maybe something like the RenderWidget host gets set to the parent window and not the webview. Still investigating . Update: After dragging the bookmark, when dragging an image onto the webcontents, evaluates this to false (which makes isValidDragTarget return false): I suspect maybe dragStartViewID_ is not getting rest properly. |
...and sometimes leads to a crash. Auditors: @bridiver Fix brave/browser-laptop#7266 Browser process's content class WebContentsView has a different implementation on macOS vs Linux and Windows. When dragging starts, a start view ID gets set on both implementations, but it wasn't getting cleared on the macOS implementation. So dragging a bookmark, tab or other chrome element in our UI would then cause future drags in a webview from an external source to stop working and to sometimes crash (whitescreen the whole window). Seems like a chromium bug to me but I think they aren't affected by it.
fixed here: |
Awesome, thanks!
…On Fri, Mar 17, 2017 at 1:54 PM, Brian R. Bondy ***@***.***> wrote:
Closed #7266 <#7266>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#7266 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AY9LGZeaKbV4zh4aAvoedHVaijeOysxFks5rmsjlgaJpZM4MCDOQ>
.
|
Awesome job, @bbondy! 😄 |
...and sometimes leads to a crash. Auditors: @bridiver Fix brave/browser-laptop#7266 Browser process's content class WebContentsView has a different implementation on macOS vs Linux and Windows. When dragging starts, a start view ID gets set on both implementations, but it wasn't getting cleared on the macOS implementation. So dragging a bookmark, tab or other chrome element in our UI would then cause future drags in a webview from an external source to stop working and to sometimes crash (whitescreen the whole window). Seems like a chromium bug to me but I think they aren't affected by it.
Test plan
Conclusive steps to reproduce:
Original issue description
Did you search for similar issues before submitting this one?
Yes.
Describe the issue you encountered:
I am unable to drag any images or files into the browser for websites designed to accept this feature (ie. Hangouts; Google Drive)
Platform (Win7, 8, 10? macOS? Linux distro?):
Mac OS X El Capitan
Brave Version (revision SHA):
0.13.3 b4cb1f5
Steps to reproduce:
Actual result:
Nothing.
Expected result:
File would begin uploading to, for example, Google Drive
Will the steps above reproduce in a fresh profile? If not what other info can be added?
untested
Is this an issue in the currently released version?
Yes, just updated
Can this issue be consistently reproduced?
Yes
Extra QA steps:
1.
2.
3.
Screenshot if needed:
Any related issues:
The text was updated successfully, but these errors were encountered: