Closed emilianionascu closed 11 months ago
@emilianionascu is this related to any of our documentation? This repo is only for docs work. If you've found a bug in Chrome it should be filed at crbug.com
@robdodson I'm not sure. It could be that the API changed and we're supposed to use setExpression differently. That is a documentation issue. It could be that the API itself has a bug and then it's not a documentation issue.
I believe I've hit this too with my extension: https://chrome.google.com/webstore/detail/sb-angular-inspector/lapcbklolihkkijaemmlbkpibgghhioh?hl=en
I thought it might be related to manifest 3, so I upgraded.
Still seem to be having an issue with setExpression.
OK, tentatively assigning to @awfuchs to take a look
Thanks for raising this. We’re moving to a new platform and so we’ll address this over there. I’ve moved the issue to our new tracker and you can see it at: https://issuetracker.google.com/issues/312784415
Describe the bug When using extensions that use sidebar panels with content set with
sidebarPane.setExpression
an error is thrown.To Reproduce Steps to reproduce the behavior:
Ctrl + Shift + I
Ctrl + Shift + I
Expected behavior Extensions should still work even after the v92 upgrade. It worked until v91.
Screenshots
Desktop (please complete the following information):
Additional context Add any other context about the problem here.