We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
After I did the scenario (that below) a couple of time, I see the JS heap size and count of DOM Nodes grow dramatically
To reproduce the scenario in your example (https://opensource.adobe.com/coral-spectrum/examples/#tabview) and switch between component table page and tab list page(for example) .
Chrome Version 89.0.4389.114 (Official Build) (64-bit) Windows
https://opensource.adobe.com/coral-spectrum/examples/#table
The text was updated successfully, but these errors were encountered:
fyi @Pareesh
Sorry, something went wrong.
No branches or pull requests
Actual Behavior
After I did the scenario (that below) a couple of time, I see the JS heap size and count of DOM Nodes grow dramatically
Reproduce Scenario (including but not limited to)
To reproduce the scenario in your example (https://opensource.adobe.com/coral-spectrum/examples/#tabview) and switch between component table page and tab list page(for example) .
Browser name/version/os (ie Chrome Version 62.0.3202.94 (Official Build) (64-bit) MacOS)
Chrome Version 89.0.4389.114 (Official Build) (64-bit) Windows
Coral Spectrum version
https://opensource.adobe.com/coral-spectrum/examples/#table
Screenshots (if applicable)
The text was updated successfully, but these errors were encountered: