Closed (won't fix)
Project:
Views (for Drupal 7)
Version:
6.x-3.x-dev
Component:
User interface
Priority:
Minor
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Anonymous (not verified)
Created:
18 Dec 2008 at 05:33 UTC
Updated:
16 May 2024 at 00:49 UTC
Jump to comment: Most recent
Comments
Comment #1
Anonymous (not verified) commentedAny update on this?
Comment #2
merlinofchaos commentedSorry, have so much to do that this one has remained on the back burner. Still keeping it open in the vain hope someone else will take a look at it for me. I'll get to it someday =)
Comment #3
dagmarYes this is a interesting feature. Moving to views 3.
Comment #4
esmerel commentedComment #5
esmerel commenteddid this get done as part of the expose filters/forms stuff in 3.x?
Comment #6
dagmarNot really, is more a views UI feature request than a view option.
Comment #7
esmerel commentedComment #8
Anonymous (not verified) commentedOk, so I've been looking through the code and have found the issue on lines 1710-1719 of views/includes/admin.inc:
Currently, clicking 'Expose' has the same effect as clicking 'Update' - the stack is reduced by one element; however, as the filter in question hasn't changed, there is now a difference between the current filter and the 'identifier' which, as a result, discards the stack altogether.
I couldn't work out how to prevent the 'Expose' button from shifting the current filter off the stack, but hopefully this information helps someone else work it out.
Comment #9
Letharion commentedComment #10
mustanggb commented