Ubuntu
chromium-browser package

Chrome bookmarks are cropped when Ambiance theme or Radiance theme is selected

Bug #573691 reported by Ashutosh Rishi on 2010-05-02

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	Chromium Browser	Unknown	Unknown	chromium #20495
	chromium-browser (Ubuntu)	Fix Released	Undecided	Unassigned

Bug Description

Ubuntu version: Ubuntu 10.04 LTS
Chrome Version (from the about:version page): 5.0.375.23 (Official Build 45554) dev

What steps will reproduce the problem?
1. Install chromium or chrome-dev on ubuntu 10.04

What is the expected result?
Bookmarks added or synced in bookmark bar should be appearing completely.

What happens instead?
I freshly installed chromium on Ubuntu 10.04 and the bookmarks I add in the bookmark bar do not appear fully. They are cut from top and from bottom, only the middle part of the icon and text (height-wise) is seen. I was having this problem when I was using lucid beta too but found no fix or reason. I did a fresh install of lucid now and yet the problems seems to be there. I installed chrome-dev and chrome-beta and the problem's there too. Then I changed the theme to something other than the default Ambiance and Radiance theme and found that the bookbark bar has been fixed. I tried it with other desktop themes and it was appearing properly. Please note that I do not mean the gtk-theme for chrome, I mean the desktop theme. With every chrome theme the bookmarks appear fully as long as the desktop theme is not Radiance or Ambiance.

Also, I am not sure whether its a bug in the theme or chrome. I filed a bug similarly for chrome too.
Screenshot attached.

Tags:

Revision history for this message

Ashutosh Rishi (ashutoshrishi) wrote on 2010-05-02:

Screenshot of the cropped bookmark bar. Edit (6.7 KiB, image/png)

Revision history for this message

John Watson (jwatson) wrote on 2010-05-02:

Confirming that I have exactly the same symptoms after upgrading to 10.04 with Chrome already installed using Ambiance or Radiance. The problem goes away immediately when I switch the desktop theme to Human or Clearlooks (for example).

Gabe Gorelick (gabegorelick) on 2010-05-02

affects:	ubuntu → light-themes (Ubuntu)
Changed in light-themes (Ubuntu):
status:	New → Confirmed

Guillaume Pascal (guigui14100-deactivatedaccount) on 2010-05-02

Changed in chromium-browser (Ubuntu):
status:	New → Invalid

Revision history for this message

Ashutosh Rishi (ashutoshrishi) wrote on 2010-05-04:

This issue was also posted widely in chromium bug page (bug #20495) and they have finally issued a fix for this there.
Please see: http://code.google.com/p/chromium/issues/detail?id=20495#c38 (comment 38 and 39)

Revision history for this message

Gabe Gorelick (gabegorelick) wrote on 2010-05-04:

The upstream bug report seems to say this is an issue with chrome and not individual themes. I don't think chrome is even integrated with the gnome theme settings anyway, so the ambiance theme is probably coming from a chrome extension baked into the Lucid version.

Changed in chromium-browser (Ubuntu):
status:	Invalid → Confirmed
Changed in light-themes (Ubuntu):
status:	Confirmed → Invalid

Revision history for this message

Evan Martin (Chromium) (evan-chromium) wrote on 2010-05-04:

(I am a Chromium developer.)

We can obey GTK themes, to an extent, and it was our bug that our GTK theme support broke with the Ambiance theme. (We also support the Chrome theming system shared with Mac and Windows, but when we're not using those themes we behave more or less like a regular Gnome app.)

In any case, the bug has been fixed.

Revision history for this message

Gabe Gorelick (gabegorelick) wrote on 2010-05-04:

> In any case, the bug has been fixed.
Fixed upstream, or also in Ubuntu? If just upstream, is there a plan to get it into Lucid?

Revision history for this message

Brian Shaw (perturbedpenguin) wrote on 2010-05-11:

Not sure what this means but I was running the Chrome beta and it had the issue so I uninstalled Chrome and installed Chromium after reading here that the issue had apparently been fixed in Chromium. Chromium still had the issue as far as I could tell and after uninstalling it and reinstalling Chrome the issue fixed itself in Chrome. Like I said not certain what that means but thought I'd share.

Revision history for this message

Ashutosh Rishi (ashutoshrishi) wrote on 2010-05-12:

The bug has been fixed and the fix is currently in the chrome's developer version.

Adolfo Jayme Barrientos (fitojb) on 2014-03-02