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

Automatic publicPath is not supported in this browser #395

Closed
maartenbreddels opened this issue Jan 27, 2023 · 6 comments · Fixed by #398
Closed

Automatic publicPath is not supported in this browser #395

maartenbreddels opened this issue Jan 27, 2023 · 6 comments · Fixed by #398

Comments

@maartenbreddels
Copy link
Member

I'm trying to support ipyvolume/pythreejs in solara, but I'm getting: "Automatic publicPath is not supported in this browser"

Any pointers where a change happened in pythreejs where this changed?

@maartenbreddels
Copy link
Member Author

Hmm, also seeing this in the (classic) notebook now. Starting from a new virtual env, pythreejs doesn't seem to work (2.4.1)

@merlinND
Copy link

I am encountering this issue in classic notebooks as well with these versions:

notebook==6.5.2
ipywidgets==8.0.4
jupyterlab_widgets==3.0.5
pythreejs==2.4.1
widgetsnbextension==4.0.5

This particular combination of versions (found in another Issue) works, though I haven't tested the effect of each downgrade individually:

ipywidgets==7.7.2
jupyterlab_widgets==1.1.1
pythreejs==2.3.0
widgetsnbextension==3.6.1

In both cases, testing in Chrome 110.0.5481.77 on Ubuntu 22.04.

@vidartf
Copy link
Member

vidartf commented Feb 17, 2023

I don't think any change was made in pythreejs, but I think a change was recommended? https://ipywidgets.readthedocs.io/en/stable/migration_guides.html#updating-the-webpack-publicpath-configuration Maybe it will work with that?

@maartenbreddels
Copy link
Member Author

Weird, it's with the classic notebook extension. Maybe for some reason, the extension fails, and it will try to fallback to the CDN, which then fails. I'll investigate more.

@vidartf
Copy link
Member

vidartf commented Feb 20, 2023

This should be fixed in 2.4.2 that I just pushed to PyPI. Please try it and see if it resolves the issue.

@maartenbreddels
Copy link
Member Author

Yes, thanks a lot @vidartf !

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

Successfully merging a pull request may close this issue.

3 participants