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

Browser incompatibility for dev setup #1645

Closed
ericjanto opened this issue Jun 19, 2024 · 4 comments
Closed

Browser incompatibility for dev setup #1645

ericjanto opened this issue Jun 19, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@ericjanto
Copy link
Contributor

Describe the bug

There is an issue with Firefox when wanting to develop the front-end with hotreloading. The fe localhost is live but does not display anything.

Environment

Using Firefox 127.0 (64-bit) on an Intel Mac.

Code to reproduce

  1. Run pnpm dev in the fe folder.
  2. Run marimo edit --headless --no-token notebook.py from another terminal tab.
  3. Open http://localhost:3000/ in Firefox. There is a blank page for me.
@ericjanto ericjanto added the bug Something isn't working label Jun 19, 2024
@dmadisetti
Copy link
Contributor

I use FF as my main browser without much issue.

One thing I do that isn't in the readme is set up dev URLs.
So opposed to localhost:3000, I have 3000.port.dev that points to localhost:3000, and then I can do:

marimo -l d edit --headless --proxy=3000.port.dev

(which also allows for token sessions, but you can still disable it)

When you pop the console what do you get for an error?

@ericjanto
Copy link
Contributor Author

So opposed to localhost:3000, I have 3000.port.dev that points to localhost:3000

How do you set up the dev URL? So I can try it too.

This is the console output in FF:

image

@dmadisetti
Copy link
Contributor

It's not totally trivial: You can do it with iptables and editing your hosts file: https://serverfault.com/a/54371

I run nginx and dnsmasq because I have a couple services running.

But I don't think I've seen that error before. A quick Google shows that interfering plugins can produce the scope response. Did you try with no plugins?

@ericjanto
Copy link
Contributor Author

Sorry for the delay in getting back to you. You had the right hunch with the plugins–I disabled my adblocker and now it's working as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants