Bug 787206

Summary:	Chromium/Chrome don't show full Component list
Product:	[Community] Bugzilla	Reporter:	Kamil Páral <kparal>
Component:	Creating/Changing Bugs	Assignee:	PnT DevOps Devs <hss-ied-bugs>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.6	CC:	dmalcolm, kbaker, kevin, sgreen
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-05-01 00:33:14 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Kamil Páral 2012-02-03 14:35:02 UTC

Description of problem:
In Firefox if you click Edit Component, you see a long list of all the available components (e.g. in Fedora). If you do the same in Chrome/Chromium, it starts with 0xFFFF and ends with python-isprelink, and then there is one more option zzuf. Everything between python-isprelink and zzuf is missing.

This is a no-go for every package maintainer/bugzapper in bugzilla.

I believe this is highly related to bug 553189.

Version-Release number of selected component (if applicable):
bugzilla 3.6.8027

How reproducible:
always

Steps to Reproduce:
1. open Chromium on some Fedora bug
2. click Component -> Edit
3. inspect the list

Comment 1 Dave Malcolm 2012-04-30 20:54:40 UTC

I ran into this problem whilst trying to edit the "Component" of bug 817072 with chromium-17.0.963.46-3.fc15.x86_64.  The components listed in the combobox are:
["0xFFFF", "389-admin", ....alphabetical list ending with "presence" ,then "zzuf"].

I was able to successfully see the full list and edit the component with firefox-10.0.1-1.fc15.x86_64.

Comment 2 Simon Green 2012-05-01 00:33:14 UTC


*** This bug has been marked as a duplicate of bug 553189 ***

Comment 3 Jason McDonald 2014-10-27 21:59:34 UTC

*** Bug 1157849 has been marked as a duplicate of this bug. ***