Bug 1663525 - Nested Custom Search results in javascript error
Summary: Nested Custom Search results in javascript error
Keywords:
Status: CLOSED DUPLICATE of bug 1618664
Alias: None
Product: Bugzilla
Classification: Community
Component: User Interface
Version: 5.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-04 17:25 UTC by Bryan Kearney
Modified: 2019-01-13 23:35 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-01-13 23:35:17 UTC
Embargoed:

Attachments (Terms of Use)

Description Bryan Kearney 2019-01-04 17:25:40 UTC 
I am attempting to edit a report using a Custom Search. When I click on the left paren button, nothing happens. Bringing up a javascript console, I see the following:

Uncaught TypeError: Cannot set property 'innerHTML' of null
    at _cs_remove_and_g (custom-search.js:297)
    at custom_search_open_paren (custom-search.js:66)
    at HTMLButtonElement.onclick (query.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=VERIFIED&classification=Red Hat&f1=flagtypes.name&f2=component&o1=substring&o2=notsubstring&product=Red Hat Satellite 6&v1=sat-6.5.0%2B&v2=Doc&x_axis_field=bug_status&y_axis_field=bug_severity&format=report-table:2762)
_cs_remove_and_g @ custom-search.js:297
custom_search_open_paren @ custom-search.js:66
onclick @ query.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=VERIFIED&classification=Red Hat&f1=flagtypes.name&f2=component&o1=substring&o2=notsubstring&product=Red Hat Satellite 6&v1=sat-6.5.0%2B&v2=Doc&x_axis_field=bug_status&y_axis_field=bug_severity&format=report-table:2762


I am running Chrome on Fedora 28.
Comment 1 Jeff Fearn 🐞 2019-01-13 23:35:17 UTC 

*** This bug has been marked as a duplicate of bug 1618664 ***
Note You need to log in before you can comment on or make changes to this bug.