Closed Bug 495914 Opened 16 years ago Closed 16 years ago

Advanced search drawer appears on homepage load, then disappears

Categories

(addons.mozilla.org Graveyard :: Public Pages, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: osunick, Assigned: rdoherty)

References

Details

Attachments

(1 file)

The advanced search drawer displays for at least half a second and then disappears. It's pretty distracting, any way we can keep this from happening?
Ryan suggested a solution which is based on what we do for AMO today. Always hide this drawer, but for JS disabled, have the tab link to the homepage with a param like advancedsearch=true that reloads the page with it open.
Assignee: nobody → rdoherty
Attached patch v1Splinter Review
quick and dirty method
Attachment #381191 - Flags: review?(lorchard)
Comment on attachment 381191 [details] [diff] [review] v1 Works well, MINUS the line: ->>>>>>> bug 495386: reskin category landing pages:site/app/webroot/css/amo2009/main-mozilla.css I hope that was just hanging around in your working dir, not in the tree.
Attachment #381191 - Flags: review?(lorchard) → review+
That was my bad - I fixed it in r26944 One thing I was going to ask about this patch (which works), is why you used a beforeFilter in lots of controllers instead of maybe an if(!empty($_GET['advanced'])) in just the search element?
Summary: Advanced search drawer appears on homepage load than disappears → Advanced search drawer appears on homepage load, then disappears
(In reply to comment #4) > That was my bad - I fixed it in r26944 > > One thing I was going to ask about this patch (which works), is why you used a > beforeFilter in lots of controllers instead of maybe an > if(!empty($_GET['advanced'])) in just the search element? I toyed with this idea, but it felt kinda 'dirty', ie, the search element behavior is explicitly tied to $_GET parameters, instead of the controller telling it when to show/hide. Maybe I was being too strict. I had to add the function to all the beforeFilters in the controllers because there is no way to globally add it to all them. Most controllers override just about everything app_controller.php sets up.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
(In reply to comment #5) > I had to add the function to all the beforeFilters in the controllers because > there is no way to globally add it to all them. Most controllers override just > about everything app_controller.php sets up. That's certainly out of scope here, but I think every controller that overrides beforeFilter() should also call its parent's beforeFilter(). I think it does make sense to have a place where we can put global stuff like this, and app_controller seems to be the right one.
Blocks: 496133
(In reply to comment #7) > That's certainly out of scope here... Bug 496133.
Verified FIXED -- tested JS disabled, too.
Status: RESOLVED → VERIFIED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: