use_gtk3 should be removed
Reported by
pdk...@gmail.com,
Jul 15 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.68 Safari/537.36 Steps to reproduce the problem: Now that GTK3 is default, any GTK3-only code does not appear to be put in #if anymore, with the consequence that disabling the flag causes Chrome to not compile. So the flag is pointless, as is GTK2-only code I think. An example CL. https://chromium.googlesource.com/chromium/src/+/b50cab37a165f1f11d9a046d7f3367e4a563a73f What is the expected behavior? What went wrong? ^ Did this work before? Yes Chrome version: 60.0.3112.68 Channel: beta OS Version: Ubuntu 14.04 Flash Version:
,
Jul 26 2017
,
Aug 24 2017
,
Sep 20 2017
pdknsk@ Could you please respond to the Comment #1
,
Sep 20 2017
I have received complaints about the GTK2 build being broken (which we have fixed), so there are apparently still folks who build in that configuration. Lets not remove the GTK2 code for a little while longer. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by krajshree@chromium.org
, Jul 18 2017Components: UI>Browser>Themes
Labels: Needs-Feedback