Bug 424691
Summary: | query screen slow down due to ajax | ||||||
---|---|---|---|---|---|---|---|
Product: | [Community] Bugzilla | Reporter: | Kevin Baker <kbaker> | ||||
Component: | Query/Bug List | Assignee: | PnT DevOps Devs <hss-ied-bugs> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | |||||
Severity: | low | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 3.2 | CC: | dkl, ineilsen | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2008-11-25 22:22:42 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: | |||||||
Attachments: |
|
Description
Kevin Baker
2007-12-14 07:38:52 UTC
Currently this done at first load so that if any form values are passed in they will be automatically selected such as product/component/version and that the lists will look correct. This is critical for things like editing stored queries, etc. A fix would be to define a javascript variable that is true/false depending on whether any form data was passed to the cgi. Then also had another var called firstrun that is set to 1 when the page first loads and then set to 0 once the products have been updated once. Then in the jscript code do check: if ( formdata == 1 && firstrun == 0 ) { update select lists set formdate = 0 set firstrun = 0 } else { do nothing } ooops should be: if ( formdata == 1 || firstrun == 0 ) { update select lists set formdata = 0 set firstrun = 0 } else { do nothing } Created attachment 289311 [details]
Patch to disable use of ajax on first page load if no form data present
Red Hat Bugzilla is now using version 3.2 of the Bugzilla codebase and therefore this bug will need to be re-verified against the new release. With the updated code this bug may no longer be relevant or may have been fixed in the new code. Updating bug version to 3.2. This is still issue even with the new revised ajax code. *** This bug has been marked as a duplicate of bug 457843 *** |