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

Ember application not detected with Firefox 120.0 #2516

Open
rgaiacs opened this issue Nov 22, 2023 · 8 comments · Fixed by #2517 · May be fixed by #2569
Open

Ember application not detected with Firefox 120.0 #2516

rgaiacs opened this issue Nov 22, 2023 · 8 comments · Fixed by #2517 · May be fixed by #2569
Labels

Comments

@rgaiacs
Copy link

rgaiacs commented Nov 22, 2023

Ember Inspector displays

Ember application not detected!

Here are some common reasons this happens:

  • This is not an Ember application.
  • You are using an old version of Ember (< rc5).

with Firefox 120.0.

To Reproduce

Steps to reproduce the behavior:

  1. Create a new Ember project by running ember new super-rentals --lang en
  2. Start the developer server by running cd super-rentals/ && ember server
  3. Open http://localhost:4200/ using Firefox
  4. Open Ember Inspector

Expected behavior

Ember Inspector working.

Environment

ember-cli: 5.4.1

node : 20.5.1

os: linux x64

Firefox: 120.0

Additional context

Ember Inspector works as expected in Chrome.

@rgaiacs rgaiacs added the bug label Nov 22, 2023
@RobbieTheWagner
Copy link
Member

@rgaiacs any errors?

@happydude
Copy link

Not for me, but the console does have Ember Inspector Active

@patricklx
Copy link
Collaborator

looks like there are some missing permissions for firefox now. I had the enable it per website now...
Screenshot 2023-11-23 at 09 51 45

@patricklx
Copy link
Collaborator

or go to manage extensions and enable it for all sites.
Screenshot 2023-11-23 at 09 56 37

@rgaiacs
Copy link
Author

rgaiacs commented Nov 23, 2023

Thanks @patricklx.

Now that you mentioned, Firefox Extension displays a notification alert:

Screenshot 2023-11-23 142436

Set the corrections permission solved the issue.

@Windvis
Copy link
Contributor

Windvis commented Apr 23, 2024

I just set up a new device and still had to configure the permissions in the extension settings. I'm not sure if the issue wasn't resolved by #2517 or if newer versions of Firefox broke it again 🤔.

@patricklx
Copy link
Collaborator

patricklx commented Apr 25, 2024

i confirmed this on Firefox 125.0.2

@patricklx patricklx reopened this Apr 25, 2024
@patricklx
Copy link
Collaborator

looks like Firefox takes this as optional now.
We need to request it manually

@patricklx patricklx linked a pull request May 6, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
5 participants