You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have successfully implemented the datafeeds for the TradingView Advanced Charts and verified the accuracy of the provided data. However, we are encountering an issue specifically within the watchlist panel regarding the sorting of symbols. Notably, while the last price, change, and change percentage are sorting correctly, we are experiencing a problem with the sorting of symbols.
Expected Behavior:
Clicking on the word "Symbol" should trigger the watchlist to sort in either ascending or descending order, just like when you click on "Last," "Change," and "Change Percentage."
Charting Library Version: 26.002
Please let us know if any additional information or clarification is required. We appreciate your assistance in resolving this matter.
The text was updated successfully, but these errors were encountered:
First of all try to use the latest available version, currently it is v.27. I was unable to replicate this behavior on our demo page and for the version from the repository. If the behavior happens again, I need more information: full debug log, console errors if any.
We have successfully implemented the datafeeds for the TradingView Advanced Charts and verified the accuracy of the provided data. However, we are encountering an issue specifically within the watchlist panel regarding the sorting of symbols. Notably, while the last price, change, and change percentage are sorting correctly, we are experiencing a problem with the sorting of symbols.
Expected Behavior:
Clicking on the word "Symbol" should trigger the watchlist to sort in either ascending or descending order, just like when you click on "Last," "Change," and "Change Percentage."
Charting Library Version: 26.002
Please let us know if any additional information or clarification is required. We appreciate your assistance in resolving this matter.
The text was updated successfully, but these errors were encountered: