Opened 12 years ago

Last modified 11 years ago

#3639 accepted defect

Browse should ask the user about blocked pop-ups

Reported by: manuq Owned by: humitos
Priority: Normal Milestone:
Component: Browse Version: Git as of bugdate
Severity: Unspecified Keywords: screenshot
Cc: humitos, manuq, garycmartin, godiard Distribution/OS: Unspecified
Bug Status: Unconfirmed

Description

Currently Browse prevents pop-up pages, which is nice. But some of them may be desirable. For example using Gmail, if you try to open a link inside an email, a Javascript alert is shown saying that a pop-up blocker is getting in the middle (screenshot attached).

Firefox and Epiphany ask the user what to do the first time this happens, and can remember the decision for the future popups in the same host. We can use a Sugar alert for this.

The current workaround in Browse is to copy the link in the clipboard, open a new tab, and paste it in the URL entry.

Attachments (1)

gmail-link-alert.png (96.1 KB) - added by manuq 12 years ago.

Download all attachments as: .zip

Change History (8)

Changed 12 years ago by manuq

comment:1 in reply to: ↑ description Changed 12 years ago by humitos

  • Keywords screenshot added
  • Priority changed from Unspecified by Maintainer to Normal

Replying to manuq:

Firefox and Epiphany ask the user what to do the first time this happens, and can remember the decision for the future popups in the same host. We can use a Sugar alert for this.

Where should we save this information? Should it be saved globally or per session?

comment:2 Changed 12 years ago by humitos

  • Owner changed from erikos to humitos
  • Status changed from new to accepted

comment:3 Changed 12 years ago by humitos

  • Cc manuq garycmartin godiard added

We have to use this setting:

How should we manage this? I think it's annoying to click on Allow (or something like that) to allow the pop up to open every time that you click on a Gmail link, for example.

This could be enabled by default.

Epiphany does not ask to me about this behaviour :(

comment:4 Changed 12 years ago by humitos

There is a bug reported about this:

I'm not sure if the version of WebKit that we are using includes this bugfix or not.

comment:5 Changed 12 years ago by humitos

That bugfix was applied here:

comment:6 Changed 12 years ago by humitos

  • Milestone changed from 0.98 to 1.0

comment:7 Changed 11 years ago by dnarvaez

  • Milestone 1.0 deleted

Milestone 1.0 deleted

Note: See TracTickets for help on using tickets.