153498 – x11-themes/gtk-engines-qt "scrollbar fix" breaks Firefox userChrome.css file

Bug 153498 - x11-themes/gtk-engines-qt "scrollbar fix" breaks Firefox userChrome.css file

Summary: x11-themes/gtk-engines-qt "scrollbar fix" breaks Firefox userChrome.css file

Status:	RESOLVED UPSTREAM

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	New packages (show other bugs)
Hardware:	All Linux

Importance:	High minor (vote)
Assignee:	Stefan Schweizer (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2006-10-30 17:21 UTC by Robin Bankhead
Modified:	2006-11-01 18:34 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Robin Bankhead 2006-10-30 17:21:46 UTC

The new feature in the "GTK+ themes and fonts" applet installed by gtk-engines-qt-0.7-r1 to fix scrollbars in Firefox does not work correctly.

Activating the scrollbar fix writes some CSS declarations to the user's Firefox profile, to [profile-dir]/chrome/userChrome.css
The declarations are preceded by a comment like so:

# The following four lines were added by KDE

This comment-style is invalid for a CSS file, and actually b0rks any rules that follow it; the correct syntax would be:

/* The following four lines were added by KDE */

No emerge --info given as this is simply a typo issue.

Comment 1 David Sansome 2006-11-01 07:50:14 UTC

Thanks for bringing this to my attention - I can't believe nobody else has noticed this...

Fixed upstream:
http://gtk-qt.ecs.soton.ac.uk/trac/changeset/21

Comment 2 Stefan Schweizer (RETIRED) gentoo-dev

2006-11-01 08:51:55 UTC

thanks for replying here! This will get fixed with the next version bump then.

Comment 3 Robin Bankhead 2006-11-01 18:34:22 UTC

Cheers ;)

I expect this will already be apparent to the devs, but I just noticed that the fix writes the same content to <profile>/chrome/userContent.css as well, so the same fix is needed there too.