Bug: selectableItemBackground shown upon clicking, while selectableItemBackgroundBorderless isn't [111819099]

Obsolete

Bug

[AOSP] assigned

Status Update

No update yet.

Description

lb...@gmail.com

created issue #1

Jul 26, 2018 08:09AM

ConstraintLayout version:
implementation 'androidx.appcompat:appcompat:1.0.0-beta01'
implementation 'androidx.constraintlayout:constraintlayout:1.1.2'

This is a very strange, specific case. Suppose you have multiple views in the ConstraintLayout :
- One with a solid background is below 2 ImageViews
- One of the ImageViews is clickable with selectableItemBackground as background, and the other with selectableItemBackgroundBorderless.

In this case, the one with selectableItemBackgroundBorderless doesn't show its clicking effect, while the other does show.

If you remove the view behind, or set its background to be semi-transparent, you can see the clicking effect.

Attached sample project, and a video.

Tested on Pixel 2 with Android P DP 5.

deleted

Restricted

0 B

deleted

Restricted

0 B

Comments

lb...@gmail.com <lb...@gmail.com> #2Jul 26, 2018 08:13AM

As far as I can tell, the "Show Kotlin Bytecode" action is an internal debugging tool which in my opinion should never have been exposed to end users.

The code is not integrated with the build output - or build system for that matter - and always compiles a single file with default compiler options (except for the language version). For dependencies, the code seems to be using the IDE view of the file, which should be fine if that is configured correctly.

For a more robust "Show Kotlin Bytecode" action we could probably just show the latest build output and notify the user if their build is out of date. However, I'm not sure if this should be an Android Studio issue, since the code is in the Kotlin plugin.

lb...@gmail.com <lb...@gmail.com> #3Jul 26, 2018 08:41AM

I suspected that might be the case. Should I file an upstream bug on the IntelliJ Kotlin plugin?

by...@gmail.com <by...@gmail.com> #4Oct 1, 2018 11:38PM

Yes, please file a bug for the IntelliJ Kotlin plugin.

di...@google.com <di...@google.com> Oct 2, 2018 10:15AM

Reassigned to ho...@google.com.

lb...@gmail.com <lb...@gmail.com> #5Oct 4, 2018 02:48PM

Filed upstream issue KTIJ-23396.

[Deleted User] <[Deleted User]> #6Dec 10, 2018 11:51AM

A fix would be handy!

ho...@google.com <ho...@google.com> Jan 14, 2019 03:58PM

Reassigned to ni...@google.com.

ni...@google.com <ni...@google.com> #7Jun 5, 2019 02:10PM

Status: New

This doesn't seem to be related to ConstraintLayout -- it looks like an issue with the ripple effect / optimization with transparency

lb...@gmail.com <lb...@gmail.com> #8Jun 5, 2019 02:12PM

@7 Can you please fix it though?
And tell about workaround, if it exists?

ku...@google.com <ku...@google.com> Jun 6, 2019 03:48AM

Assigned to ku...@google.com.

ku...@google.com <ku...@google.com> #9Jun 6, 2019 07:41AM

Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

ad...@google.com <ad...@google.com> Oct 10, 2019 08:24AM

Reassigned to ve...@google.com.

ke...@gmail.com <ke...@gmail.com> #10Oct 18, 2019 02:02PM

android:foreground does not work

lb...@gmail.com <lb...@gmail.com> #11Oct 18, 2019 02:46PM

@10 it works only for some views

ma...@gmail.com <ma...@gmail.com> #12Oct 28, 2019 08:40AM

wrap your parent layout, set the desired background to this layout (grandparent layout) and remove the background from the parent layout

ad...@google.com <ad...@google.com> Nov 28, 2019 06:45AM

Reassigned to te...@google.com.

vi...@google.com <vi...@google.com> Dec 9, 2019 09:03AM

Reassigned to cc...@google.com.

cc...@google.com <cc...@google.com> #13Apr 26, 2020 07:04PM

Status: Won't Fix (Obsolete)

Thank you for your feedback. We assure you that we are doing our best to address the issue reported, however our product team has shifted work priority that doesn't include this issue. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with the bug report here

https://goo.gl/TbMiIO.

lb...@gmail.com <lb...@gmail.com> #14Apr 27, 2020 05:53AM

https://issuetracker.google.com/issues/155009790

sa...@gmail.com <sa...@gmail.com> #15May 30, 2023 07:34AM

this issue is not fixed yet? since 2018 serious?