Problem/Motivation

Commit 710a536 (Use a safer way of finding the exposed form) Added a nicer way to find the exposed form element. However, because this uses more general selection, the use of children() restricts what custom view templates can do.

Proposed resolution

Make the selector more forgiving by using find() instead of children(). As children() only get direct descendants.

Remaining tasks

Use find() to get the actual form too?

CommentFileSizeAuthor
#2 views-2320661-1.patch516 bytesdamiankloip
#1 views-2320661.patch514 bytesdamiankloip

Comments

damiankloip’s picture

damiankloip commented
Status: Active » Needs review
StatusFileSize
new views-2320661.patch514 bytes
damiankloip’s picture

damiankloip commented
StatusFileSize
new views-2320661-1.patch516 bytes

Maybe this instead.

jkingsnorth’s picture

jkingsnorth commented
Status: Needs review » Closed (duplicate)

Hi damiankloip. There's been a lot of discussion about this issue here: #2425099: Exposed form in block with ajax no longer works

I think these issues pretty much refer to the same thing. Unfortunately the patch in #2 does not fix the problems described in the other issue. If it's OK I think we should close this issue, even though it predates the other, and focus efforts there to get this fixed up.