Fixed
Status Update
Comments
dy...@google.com <dy...@google.com> #2
These changes would be really nice! Being able to change the text colour is really important as it now doesn't match the rest of our app either.
Stack overflow posting -http://stackoverflow.com/questions/32533069/how-to-change-a-title-color-in-chrome-custom-tabs
Stack overflow posting -
wi...@gmail.com <wi...@gmail.com> #3
Changing text color and the overflow icon color is important to us too! Awesome work on the feature though.
ar...@google.com <ar...@google.com>
bo...@google.com <bo...@google.com>
bo...@google.com <bo...@google.com> #4
The ability of customize the status bar color is very important!
bo...@google.com <bo...@google.com>
ca...@google.com <ca...@google.com> #5
It is in the essence of a "custom" UI component to have a custom color. Please add this feature!
de...@google.com <de...@google.com> #6
I have noted that the status bar automatically generated from the toolbar color is a bit darker than needed. The status bar color of the chrome activity is different to the one of the rest of my app. It doesn't strictly follow Material guidelines.
Description
The bug is showed in the video. This happens only in the android emulator window.
Please Read:
Android Studio Version: Unknown
Emulator Version (Emulator--> Extended Controls--> Emulator Version): 32.1.11-9536276
HAXM / KVM Version: HVF 13.2.0
Android SDK Tools: 26.1.1
Host Operating System: macOS 13.2.1
CPU Manufacturer: Other CPU:
64-bit CPU
RAM: 16384 MB
GPU:
Build Fingerprint:
AVD Details: Name: A22_API_31
CPU/ABI: arm64
Path: /Users/projecthouse/.android/avd/A22_API_31.avd
Target: google_apis_playstore [Google Play] (API level 31)
Skin: 720x1510
SD Card: 512M
AvdId: A22_API_31
PlayStore.enabled: true
avd.ini.displayname: A22 API 31
avd.ini.encoding: UTF-8
disk.dataPartition.size: 6442450944
fastboot.chosenSnapshotFile:
fastboot.forceChosenSnapshotBoot: no
fastboot.forceColdBoot: yes
fastboot.forceFastBoot: no
hw.accelerometer: yes
hw.arc: false
hw.audioInput: yes
hw.battery: yes
hw.camera.back: virtualscene
hw.camera.front: emulated
hw.cpu.ncore: 4
hw.dPad: no
hw.device.hash2: MD5:9847239f65ec7ef3089a6320357fa7a4
hw.device.manufacturer: User
hw.gps: yes
hw.gpu.enabled: yes
hw.gpu.mode: auto
hw.initialOrientation: Portrait
hw.keyboard: yes
hw.lcd.density: 240
hw.lcd.height: 1510
hw.lcd.width: 720
hw.mainKeys: no
hw.ramSize: 6144
hw.sdCard: yes
hw.sensors.orientation: yes
hw.sensors.proximity: yes
hw.trackBall: no
image.sysdir.1: system-images/android-31/google_apis_playstore/arm64-v8a/
runtime.network.latency: none
runtime.network.speed: lte
showDeviceFrame: yes
skin.dynamic: yes
tag.display: Google Play
vm.heapSize: 80
Steps to Reproduce Bug:
The bug is showed in the video. This happens only in the android emulator window.
Expected Behavior:
Observed Behavior: