New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 616846 link

Starred by 1 user
Status: WontFix
Owner:
mea...@chromium.org
Closed: Aug 2016
Cc:
creis@chromium.org
█ nasko@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Allow navigations to some schemes (e.g. view-source) via "Open in new tab/window" menus

Project Member Reported by mea...@chromium.org, Jun 2 2016 
After blocking content initiated navigations to view-source URLs ( bug 606619 ), the only way to open such URLs is to copy and paste the URL. This will be a bit more of a pain when we block other URLs such as data: and blob:.

I'm wondering if it's worth allowing "Open in new tab/window" context menu items to open a subset of URLs to which we block page initiated navigations. So the user will be able to right click and open view-source, data and blob URLs in a new tab, but not chrome: or chrome-devtools: URLs.

creis: What do you think? Would adding a new class of URLs that are displayed/blocked but still navigable add a lot of complexity to the navigation code? There also seems to be some marginal security implications (e.g. a page could now trick the user to ctrl+click).

Comment 1 by creis@chromium.org, Jun 2 2016

Cc: nasko@chromium.org
Components: UI>Browser>Navigation
Yeah, I'm hesitant to introduce a concept of links that only work if you choose "Open in new tab/window."  That could create a lot of corner cases where we think navigations to a class of URLs are blocked when they're not.  I do see your point about it being similar to copying the URL and pasting it into the address bar (and it is considered a browser-initiated navigation), but most people probably don't view the context menu as any different from a link click.

Important note: the "Open in new tab/window" context menu is different from ctrl+click.  The context menu is treated like a browser-initiated navigation, and ctrl+click is a renderer-initiated navigation (and thus would not allow the navigation, even in this proposal).

Comment 2 by mea...@chromium.org, Aug 11 2016

Status: WontFix (was: Untriaged)
Thanks Charlie. I agree the additional complexity doesn't justify the benefit, so closing.
►

Sign in to add a comment