Zero-width buttons in Project Structure [159059846]

Fixed

Bug

Status Update

No update yet.

Description

em...@google.com

created issue #1

Jun 15, 2020 09:52PM

Build: AI-201.7223.91.42.6568795, 202006081754,

AI-201.7223.91.42.6568795, JRE 1.8.0_242-release-1644-b01x64 JetBrains s.r.o, OS Windows 10(amd64) v10.0 , screens 2560x1440, 1536x864

AS: 4.2 Canary 1; Kotlin plugin: 1.3.61-release-Studio4.1-1; Android Gradle Plugin: 4.2.0-alpha01; Gradle: 6.5; NDK: from local.properties: (not specified), latest from SDK: (not found); LLDB: pinned revision 3.1 not found, latest from SDK: (package not found); CMake: from local.properties: (not specified), latest from SDK: 3.10.2, from PATH: (not found)

IMPORTANT: Please read https://developer.android.com/studio/report-bugs.html carefully and supply all required information.

+++

Repro instructions

Create a new app
Open Project Structure
Open Modules or Build Variants

Expected: Small buttons on the right of combobox have a label Actual: Buttons are zero width

Mon Jun 15 2020 14:49:02 GMT-0700 (Pacific Daylight Time).png

32 KB

View

Download

Comments

uc...@google.com <uc...@google.com> Jun 15, 2020 10:45PM

Assigned to an...@google.com.

xa...@google.com <xa...@google.com> Jun 25, 2020 04:30PM

Reassigned to so...@google.com.

so...@google.com <so...@google.com> #2Jul 2, 2020 03:59PM

Reassigned to xa...@google.com.

I am not sure I understand the use case. how can the benchmark be code to real world scenario when it's not possible to do right now ? which scenario is it ?

In any case, since this would be for benchmarking, this would clearly not be available through the public DSL. We should find a semi-private way of doing this (maybe the private variant API object could offer that functionality for instance or a property).

xa...@google.com <xa...@google.com> Jul 3, 2020 06:27AM

Reassigned to da...@google.com.

da...@google.com <da...@google.com> #3Sep 18, 2023 05:16PM

Reassigned to so...@google.com.

We want benchmarks to measure code after Progaurd / R8, but it's not possible to turn that on for androidTests in library modules at the moment (to my knowledge?)

Benchmarks are also a public facing thing, but we have a plugin to help configure gradle builds for our users, so if support for this ends up in a private API, we could try to keep those usages localized to our code perhaps.

Screenshot 2023-09-18 at 10.15.40 AM.png

14 KB

View

Download

so...@google.com <so...@google.com> Sep 18, 2023 05:26PM

Status: New

ga...@google.com <ga...@google.com> #4Sep 29, 2023 11:26AM

Assigned to ml...@google.com.

Hi Jerome,

Any update on the status of this request and when it can be supported?

Thanks,
Amanda

ka...@google.com <ka...@google.com> Aug 30, 2024 01:54PM

Reassigned to ka...@google.com.

ka...@google.com <ka...@google.com> Aug 30, 2024 03:57PM

Marked as fixed.

an...@google.com <an...@google.com> #5Sep 9, 2024 10:44PM

this is not part of our OKR at this point so we are not talking soon. at first glance, we would need to simulate usage patterns to minify against and such, this seems substantial amount of work. there are not a lot of library module that have android tests, most only rely on unit-tests.

how important is this ? we are out of PM right now but I suspect the next step will be to negotiate with J. Eason and xav@ to scale a priority level.