Replies: 1 comment
-
If you have a reproducible case for your issue, then you should post it to the specific layout's issue tracker so the people who work on that layout can take a look at it: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We are using the cytoscape.js and cytoscape-cise npm package on our project and have encountered a problem with Google authentication that this package causes. The following error appears in the console when the Google authentication popup appears, the popup is empty, and authentication is blocked:
Desired behavior:
Authentication through Google is working; the popup contains functionality for authorization.
The code:
The code works fine apart from this authorization block. We tried to use authorization both in the popup and in a separate window - in both cases the same error appears in the console.
We also tried to connect the cytoscape and cytoscape-cise libraries via import - authorization blocking occurs in all cases.
Authorization is blocked on any page if the user has previously visited the page where the component with cytoscape was loaded. It seems that cytoscape-cise reacts to a new window created during authorization.
How to restrict the library cytoscape to the component in which it should run and prevent running during authentication?
Beta Was this translation helpful? Give feedback.
All reactions