Preserve Input Search Value

Created on 10 November 2022, almost 2 years ago
Updated 6 August 2024, about 1 month ago

Problem/Motivation

We have a use case to preserve the search input that was used, which provides a better UX for the user in the long run.

Feature request
Status

RTBC

Version

1.0

Component

Code

Created by

🇺🇸United States droath

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇨🇦Canada phjou Vancouver/Paris 🇨🇦 🇪🇺

    Nice feature.
    Should we make this a checkbox in the block configuration to enable or disable this feature? And we would enable this by default.

    - If people want to customize in their theme, it might be best to have an option to not add any javascript.
    - It might be best if the javascript was based on a class that we add ourselves because in a theme the class "form-search" could be missing or used in other spots.

  • Status changed to Needs work over 1 year ago
  • 🇨🇦Canada phjou Vancouver/Paris 🇨🇦 🇪🇺
  • I thought about something like this:

  • Status changed to Needs review 3 months ago
  • 🇮🇳India Vivek Panicker Kolkata

    This patch worked for me!

  • 🇮🇳India Vivek Panicker Kolkata

    Converted patch#7 to MR.

  • Status changed to RTBC about 1 month ago
  • 🇮🇳India atul ghate

    I have reproduced the issue successfully.
    The MR8 is applied cleanly.

    I followed the steps below to reproduce the issue:

    1.Cloned the 1.0.x version of the module.
    2.Installed its dependencies and enabled both modules.
    3.Create a view for content and add exposed filter and configure
    4.add serach api form by configuring it with key and action view url
    5.Reproduced the issue both without MR8 changes and with MR8 applied.
    Changing its status to RTBC.

Production build 0.71.5 2024