Bug 844517
| Summary: | Changing entries in the searchbar can create JS errors | ||
|---|---|---|---|
| Product: | [Retired] Beaker | Reporter: | Raymond Mancy <rmancy> |
| Component: | web UI | Assignee: | Raymond Mancy <rmancy> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 0.9 | CC: | bpeck, dcallagh, ebaak, rmancy, stl |
| 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-09-06 04:39:53 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Just to be clear, this error does not cause any problems in functionality. Beaker 0.9.3 has been released. |
Under some circumstances, changing the search table in the search bar can create the following error: elem is undefined: elem.setAttribute(k, v); This only happens when you switch between values which both use a select field in their values column.