-
Notifications
You must be signed in to change notification settings - Fork 168
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
Resolving GeoGebra Notes Integration Issue: Camera Access in iFrames #12121
Comments
Thank you chatGPT! Maybe it would be even better to use a parameter instead of allowing camera everywhere. But that depends on how much work that would be. |
@kobergj to make this configurable, it would make most sense to have it configurable in oCIS and then Web would only read and use the config accordingly. Reason for that: the external apps are loaded via API call into oCIS, not a Web config. So it would be simply about keeping the information together. And e.g. However, since that would increase the effort, should we do that or simply go with "allow always" solution? |
Yes let's go with the simple solution for now. Probably no one will ever complain about it 👍 |
Reopened. Unfortunately it still does not work. Same behaviour as before. Happy to make a screen sharing session. |
@dj4oC I would need to see whether there is any error output in the browser console. |
Background:
We are integrating GeoGebra Notes as an external app into ownCloud Infinite Scale. During testing, it was identified that the camera functionality does not work as expected. The issue stems from the missing allow="camera" attribute in the <iframe> where GeoGebra Notes is loaded.
Technical Context:
The relevant code can be found here:
App.vue Line 2-8
To enable camera functionality in GeoGebra Notes, we need to modify the allow attribute of the <iframe> tag to include camera. This change ensures that the browser grants the required permission to GeoGebra Notes for accessing the camera.
Action Plan:
Add allow="camera" to the iframe in the App.vue file of the web-app-external package.
The text was updated successfully, but these errors were encountered: