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

add support for chrome 99+ #70

Closed
wants to merge 1 commit into from
Closed

add support for chrome 99+ #70

wants to merge 1 commit into from

Conversation

vvenv
Copy link

@vvenv vvenv commented Mar 17, 2022

fix: #69

`port.sender.url` contains `//devtools`
@vvenv vvenv changed the title Master add support for chrome 99 Mar 17, 2022
@vvenv vvenv marked this pull request as ready for review March 17, 2022 11:06
@brandonbloom
Copy link

Just wanted to confirm: I build/installed this change locally and it does indeed fix the issue. Thanks!

@HoffmannP
Copy link

Works for me two, please merge

@Little-Star-Star
Copy link

It works good for me in v99 of chrome.

@c19
Copy link

c19 commented Apr 5, 2022

the pr version works for me in v100.0.4896.60 of chrome, macos

@jefflafay
Copy link

This works on my macos with chrome 100.0.4896.88 (x86_64). The production chrome plugin is still broken without this PR.

@vvenv vvenv changed the title add support for chrome 99 add support for chrome 99+ Apr 20, 2022
@ianyxtan
Copy link

ianyxtan commented Apr 26, 2022

This fix didn't work for me on ubuntu 22.04. Used firefox at the mean time.

@kaipaysen
Copy link

kaipaysen commented May 10, 2022

Works for me on Mac/Chrome 100, but not on Ubuntu 22/Chrome 100.

@GM-David
Copy link

Nice 👍

@mgrubinger
Copy link

Are there any plans to merge this PR?

@bershanskiy
Copy link
Contributor

Are there any plans to merge this PR?

Not that I know of. This repository appears to be abandoned (last commit in June 2021). If you like to, you can build extension locally or even just open the ChromeData folder and patch it manually.

Copy link

@rocketinventor rocketinventor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixes the issue! Awesome!

@bershanskiy
Copy link
Contributor

@@ -1,7 +1,7 @@
const toolsPorts = new Map()

chrome.runtime.onConnect.addListener(port => {
if (port.sender.url == chrome.runtime.getURL('/devtools/panel.html')) {
if (port.sender.url.replace('//devtools', '/devtools') == chrome.runtime.getURL('/devtools/panel.html')) {
Copy link

@Saibamen Saibamen Sep 22, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

More universal solution:

Suggested change
if (port.sender.url.replace('//devtools', '/devtools') == chrome.runtime.getURL('/devtools/panel.html')) {
if (port.sender.url.replaceAll('//', '/') == chrome.runtime.getURL('/devtools/panel.html')) {

And what do you think about adding toLowerCase()?

@bershanskiy
Copy link
Contributor

The Chromium DevTools bug (linked above) was fixed and fix was already rolled into Chromium. I tested on Chromium Version 108.0.5358.0 (Developer Build) (64-bit) and sender.url was fine. Most likely, Chromium Canary was already fixed too. We can expect Chromium 108 to release with Svelte DevTools working again.

@bershanskiy
Copy link
Contributor

I just checked on Google Chrome Beta 108 and Svelte Devtools worked fine. If you still would like to use this extension, you can just install Chrome Beta or wait until November 29 for Chrome 108 to be released officially.

Test details:

  • Svelte Devtools 1.3.0 installed from CWS
  • Google Chrome Beta 108.0.5359.22
  • macOS Montrey 12.6 on MacBook Pro (Retina, 13-inch, Early 2015)

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 this pull request may close these issues.

Can't get working svelte devtools in Chrome with svelte new version 3.46.4