899586 - Consecutive whitespaces in field values are ignored in <select> elements

Status: RESOLVED FIXED

(Bugzilla :: Query/Bug List, defect)

Description

[Edam]

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:22.0) Gecko/20100101 Firefox/22.0 (Beta/Release)
Build ID: 20130618035212

Steps to reproduce:

1. In Administration -> Field Values -> Severity, add a new value, "A  (blocker)" (NOTE: there is a double-space between the 'A' and the open-bracket).
2. Change a bug to have this new severity value (or create a new bug with it)
3. Perform a search for all bugs of the new severity value


Actual results:

Zarro bugs found


Expected results:

The bug should have been returned

Comment 1

[Frédéric Buclin]

I can reproduce the issue. In query.cgi, the severity drop-down correctly has double spaces, but they are concatenated once passed to buglist.cgi. But if you type |sev:"A  (blocker)"| in the QuickSearch field, then it works correctly.

Comment 2

[Frédéric Buclin]

I just tested with a simple HTML page, and whitespaces are always concatenated before being passed to the script, so this is not exactly a Bugzilla bug but rather how all browsers behave (I tested with Firefox, Opera, Google Chrome and Konqueror). In text fields, consecutive spaces are not concatenated, and so things work correctly using the Custom Search section.

Comment 3

[Frédéric Buclin]

Actually, this is a regression due to bug 636416, which means 4.2 and older are not affected.

Comment 4

[Frédéric Buclin]

Attachment: patch, v1

Consecutive whitespaces in value="..." are correctly taken into account, so let's set it in all cases (this is how it worked in 4.2 and older).

Comment 5

[Frédéric Buclin]

Committing to: bzr+ssh://[e-mail]/bugzilla/trunk/
modified template/en/default/search/field.html.tmpl
Committed revision 8695.

Committing to: bzr+ssh://[e-mail]/bugzilla/4.4/
modified template/en/default/search/field.html.tmpl
Committed revision 8591.