Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Widgets using stored values aren't updated if the stored value is updated in another browser tab #24887

Open
1 task done
ghost opened this issue Jun 27, 2023 · 1 comment
Assignees
Labels
Bug Something isn't working Framework Functions Cases related to internal functions like showAlert(), navigateTo() etc... Javascript Product Issues related to users writing javascript in appsmith Low An issue that is neither critical nor breaks a user flow Production Query & JS Pod Issues related to the query & JS Pod

Comments

@ghost
Copy link

ghost commented Jun 27, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Description

I have two tabs, each showing a different page of the same Appsmith app. When I update a stored value in Tab 2 the change isn't reflected in Tab 1.

I expect the widgets bound to the stored value in Tab 1 to update when I change the value in Tab 2. They are using the same store.

The use case here is having a common form that is used across multiple pages. Several pages of the app contain a form for editing data. One of the form fields is complex and common among pages. This field has been broken out into its own editor page. The data from this complex field has an effect on the other fields from the original form. We need the original form tabs values to react in real-time while editing the complex field in its own page.

Related Discord thread.

Steps To Reproduce

  1. Open the public sample app below.
  2. Click the Populate the Store button.
  3. Observe that the store is populated with some values.
  4. Click the Open Browser Tab 2 button.
  5. Change a value in the JSON Form.
  6. Click Update the Store.
  7. Switch back to the original tab.
  8. Observe that the value has not updated.
  9. Refresh the original tab.
  10. Observe that you can now see the correct and current value of the store.

Public Sample App

https://app.appsmith.com/app/issue-cross-tab-value-updates/example-645c5a6e47cc6a716aa3155e

Environment

Production

Issue video log

No response

Version

Cloud 1.9.24-SNAPSHOT

Front logo Front conversations

@ghost ghost added Bug Something isn't working Needs Triaging Needs attention from maintainers to triage Medium Issues that frustrate users due to poor UX storeValue labels Jun 27, 2023
@github-actions github-actions bot added the Javascript Product Issues related to users writing javascript in appsmith label Jun 27, 2023
@bharath31
Copy link

@arunvjn could you investigate the root cause?

@bharath31 bharath31 added Low An issue that is neither critical nor breaks a user flow and removed Needs Triaging Needs attention from maintainers to triage Medium Issues that frustrate users due to poor UX labels Sep 12, 2023
@Nikhil-Nandagopal Nikhil-Nandagopal added Framework Functions Cases related to internal functions like showAlert(), navigateTo() etc... Production and removed storeValue labels Feb 29, 2024
@Nikhil-Nandagopal Nikhil-Nandagopal added the Query & JS Pod Issues related to the query & JS Pod label Aug 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Framework Functions Cases related to internal functions like showAlert(), navigateTo() etc... Javascript Product Issues related to users writing javascript in appsmith Low An issue that is neither critical nor breaks a user flow Production Query & JS Pod Issues related to the query & JS Pod
Projects
None yet
Development

No branches or pull requests

5 participants