prevent js alert spoofing attacks

[diracdeltas]

Test Plan

1. Visit http://jsbin.com/fiyojusahu/edit?html,output
2. In the output area, click the Click me to test an alert button
3. Observe that the alert:

• does not show the Brave logo
• shows the domain it originated from
• is only shown on this tab; you can switch tabs without a problem. There is no question which tab created this alert.

4. Click OK to close alert
5. Open http://jsbin.com/sadunogefu/edit?html,output in a new tab
6. In the output area, click the Click me to test a confirm button
7. Observe that the confirm:

• does not show the Brave logo
• shows the domain it originated from
• is only shown on this tab; you can switch tabs without a problem. There is no question which tab created this confirm.

8. Click cancel to close confirm

original issue text

if you open https://jsfiddle.net/s4oab7yn/ and then switch to another tab, the alert shows looks like it's coming from the currently-active tab instead of the tab it's actually from.

two mitigations:

• the message box should display its origin
• add a button in the message box to switch to the tab that it originated from
• also mentioned in Alert: "Your computer has been blocked" Error #S47452D #4992 - remove the Brave logo from the alert box

[Sh1d0w]

Can we do it like Chrome does it? When an alert or confirm is invoked in another tab, different from the current active one, the tab that triggered the alert becomes the active tab (without any user interaction needed)? I think this is the most clean way to do it, because some users still may get confused.

[bbondy]

I much prefer what @diracdeltas mentioned with a button to switch to the tab. I find it very obnoxious and annoying that Chrome makes itself the active window and loses my current-tab-context.

[diracdeltas]

@bridiver how involved do you think this will be WRT electron? wondering if it will be feasible for 0.12.8

[BrendanEich]

I recall Chrome puts a checkbox in the JS dialogs so users can stop them repeating from a given origin. Is that right? We could do worse!

[bridiver]

I think the current plan is to generate the JS dialogs inside the brave ui instead of using the current OS dialogs and display them per-tab instead of window modal. Similar to Safari, but also adding the checkbox as @BrendanEich mentioned

[bridiver]

fyi - Safari won't even display the window.alert if you run it inside a setTimeout so you'll have to remove that if you want to compare Safari to Brave or Chrome

[cndouglas]

Related issue: #3794

[bsclifton]

Moving to 0.13.4

[srirambv]

Verified on master. Works fine