FlashGot install has increased spacing between context items

[Landis]

'bug-report'...
Hello,
after the successful installation of FG, all my context menus (blank area of page, on item, on image etc), the spacing between menu items has doubled (approximately). The FG option to show FG context menu and the other to put in sub-menu to save space have no affect on menu items. FG menu puts a FG sub-folder, but all the items remain in the main context menu as separate items and the FG sub-folder is empty.

I can live with deselecting the FG items, leaving only the media option in the main context menu, and disabling the FG folder, but I can NOT live with the extra spacing between menu items.... I worked hard to shrink that padding.

Any ideas please?
Landis.
p.s., disabling FlashGot in the Add-Ons page has no affect now that it's been installed.
p.p.s., mozilla Nightly-central 29.0a1 on openSuSE Linux running KDE 4.11.4

[therube]

Do you know if it is specific to Nightly?

[Landis]

No, i don't..
I can and will start the same profile with Firefox, Aurora and UX then let you know what I find.

Landis.

[Landis]

OK, I ran my main profile, the one with FlashGot installed.
It dawned on me that the reduced padding in context menus is an edit to the chrome i made.
Nightly, UX and Aurora all treat it the same.
Running Firefox (the system maintained installation) proved nothing as I would Not want it touching my profile.


Here's what dawned on me; I reduced the padding in the menus and it seems that whatever FG is doing to the context menu, 'un-does' that padding (css) edit. That is, FG is Not making it 'bigger' (increasing the padding), it's Removing my narrower (small) padding between context menu items.

Menu bar and bookmarks toolbar (personal-bookmars (personal-bar)) are Not affected.

Code: Select all

#personal-bookmarks {
	max-height:20px !important;
	padding-top:1px !important;
	padding-bottom:0px !important;
	margin:-4px 0px !important;
	border:0px solid yellow;
}

So, does anyone know the #ID of the context menu so that I can specifically reduce it (force it back to 0.4 em for example)

Thanks,
Landis.