Chrome display problem in multi-window.
Reported by
yasutaka...@kyocera.jp,
Jan 18 2017
|
|||
Issue description
Device name: Android One (507SH) Nougat 7.0
Application version: Chrome 55.0.2883.91
Operating system: Android 7.0
URLs (if applicable): None
Steps to reproduce:
<Preparation>
* Install "launchapplication-debug.apk" that launches Chrome.
* Launch some applications supporting multi-window.
<Steps>
(1) Launch Chrome.
(2) Perform a long press on the Overview button.
(3) Select the application supporting multi-window in the Overview screen.
(4) Tap Home button.
(5) Launch "LaunchApplication".
(6) Perform a long press on the Overview button, and select other application.
(7) Tap Home button.
Expected result:
(5) Web content area doesn't become black.
(7) URL bar doesn't remain.
Actual result:
(5) Web content area becomes black.(5_blackscreen.png)
(7) URL bar still remains.(7_URLbar.png)
Note:
We attach the screenshot, two test applications, and bugreport log.
These issues are reproduced by an application that has the following parameters in AndroidManifest.xml.
---------------------------
android:resizeableActivity="false"
android:theme="@android:style/Theme.Translucent.NoTitleBar"
---------------------------
Especially, these problems happen when an application has "@android:style/Theme.Translucent.NoTitleBar", but don't happen when not.
We attach two test applications for reproducing this issue:
* launchapplication-debug.apk
* launchapplication-debug_OK.apk
launchapplication-debug.apk has "@android:style/Theme.Translucent.NoTitleBar", and the problems happen.
launchapplication-debug_OK.apk doesn't have it, and the problems don't.
The following snippet is a part of implementation of "launchapplication-debug.apk".
---------------
* AndroidManifest.xml
<application
android:allowBackup="true"
android:icon="@mipmap/ic_launcher"
android:label="@string/app_name"
android:supportsRtl="true"
android:theme="@style/AppTheme">
<activity android:name=".LaunchApplication"
android:theme="@android:style/Theme.Translucent.NoTitleBar"
android:resizeableActivity="false">
<intent-filter>
<action android:name="android.intent.action.MAIN"/>
<category android:name="android.intent.category.LAUNCHER"/>
</intent-filter>
</activity>
</application>
* LaunchApplication.java
public class LaunchApplication extends AppCompatActivity {
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
Intent intent = new Intent(Intent.ACTION_VIEW, Uri.parse("https://www.google.co.jp/"));
startActivity(intent);
finish();
}
}
---------------
,
Jan 26 2017
Can you please include a video of the issue and repro steps that do not include a custom APK if possible? This sounds like its probably related to issue 668466, which is fixed in newer versions of Android.
,
Jan 27 2017
We attach the video. We're finding repro steps that do not include a custom APK. We think that this issue can be reproduced by apps having a implementation same as custom APK. We can't view 668466. We don't have permission to view the page. If possible, could you provide me the detail of 668466? Is it a bug for chrome app?
,
Jan 27 2017
Thank you for the video. If you're up for a little more work, can you please capture a bugreport? The video looks like a framework issue to me - a bit different than one I mentioned in comment #2 but it's possible they have the same root cause. There are some other things happening in the video that indicate a framework issue. I pulled out some screenshots from the video. You can file an open source Android bug here: https://code.google.com/p/android/issues/entry?template=Developer%20bug%20report or I can help file an internal bug (visibility will be restricted to Google). ----- Issue 668466 was an Android bug that presented in the Chrome app: Steps to reproduce: 1. Launch chrome and put it in multi-window mode docked to the top of the screen 2. Search anything in omnibox 3. Move the tab to other window from Menu> Observe Observed behavior: Tab appears black Expected behavior: Tab should not be black and seen as normal searched result page
,
Jan 27 2017
A bugreport is included in attached files.7z. We captured it at step (7). Could you please help file an internal bug? If you could find out about it, could you let me know it on this report? We also investigate the frameworks.
,
Jan 27 2017
I filed an internal bug. I'll let you know when I hear back. Thank you for the thorough report!
,
Nov 7 2017
yasutaka.kaneda.nf@kyocera.jp@ - do you still see this on the O release?
,
Nov 24 2017
Thank you for your reply. I don't see this on the O release.
,
Nov 27 2017
Thanks for checking! I'm going to close this as it no longer reproduces. |
|||
►
Sign in to add a comment |
|||
Comment 1 by rsgav...@chromium.org
, Jan 26 2017Owner: twelling...@chromium.org
Status: Assigned (was: Unconfirmed)