Skip to content
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

sprites.png is queried from blockly-demo.appspot.com instead of from JupyterLab server/a common CDN #102

Open
Phoenix616 opened this issue Sep 19, 2024 · 1 comment

Comments

@Phoenix616
Copy link

Phoenix616 commented Sep 19, 2024

Right now the sprite which includes the buttons and the trash can seems to be queried from the blockly demo server as seen in the dev console:

image

This seems strange as a) it's a file from the blockly demo setup and not some CDN meant to be used like that, and b) leaks (potentially personally identifiable) user data to a third party in a way that most wont realise. (not even admins which would be required to mention this in their privacy statements or even allow that domain in their firewall)

I've even seen the trashcan icon break completely in certain privacy-minded browser setups that block requests to resources on third party domains.

I'm unsure if this is something one can adjust in the setup or if it needs to be changed/can be changed in the jupyterlab-blockly code or even needs to be done in blockly itself but sinceI noticed this being an issue in a Jupyterlab setup I thought the best start to bring up the issue would be here.

@DenisaCG
Copy link
Member

Thanks for opening this issue, @Phoenix616. Sorry for the delayed response.

Hm, this is a weird behaviour. We are not importing or loading any buttons or trashcan individually. In this extension, we are initializing the workspace and the trashcan automatically gets added to it. These would be the relevant pieces of code:

this._workspace = Blockly.inject(this._host.node, {
toolbox: this._manager.toolbox,
theme: THEME
});

Blockly.serialization.workspaces.load(data, this._workspace);

This behaviour seems to not come from the extension itself, unless the setup for the workspace has changed and we need to update it.

Just to clarify, on top of the trashcan, what other blockly buttons are you referring to? Also, from your debugging, was this something coming from the extension?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants