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

Issue 769887 link

Starred by 1 user
Status: WontFix
Owner:
█ dskiba@chromium.org
Last visit 15 days ago
Closed: May 2018
Cc:
twelling...@chromium.org
tedc...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Take intent action into account in ChromeLauncherActivity

Project Member Reported by dskiba@chromium.org, Sep 28 2017 
ChromeLauncherActivity (target for .Main activity alias) doesn't check intent action before dispatching it. So for example you can use MAIN intent to open a URL.

We need to properly act upon intent action and reject all invalid cases.

Comment 1 by dskiba@chromium.org, Oct 2 2017 

I would like to do some work here for M63 - any suggestions? Should we go full-nuclear and simply restrict to what MAIN intents can do? Or should we add UMAs first, to see how widespread the problem is?

Comment 2 by dtrainor@chromium.org, Feb 8 2018

Components: UI>Browser>Mobile Mobile>Intents

Comment 3 by tedc...@chromium.org, Feb 8 2018

Owner: dskiba@chromium.org
Status: Assigned (was: Untriaged)
Do you still think this is a problem?  I think if we get a MAIN intent w/ a URL, we can start route that to ChromeTabbedActivity.  But I'd like to get away from CTA spawning different activities if at all possible.

Comment 4 by dskiba@chromium.org, May 22 2018 

This is probably not a problem. Let's reopen if we have more evidence that it is.

Comment 5 by dskiba@chromium.org, May 22 2018

Status: WontFix (was: Assigned)
►

Sign in to add a comment