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

IPFS badge should open native protocol scheme when local node is used #21306

Closed
lidel opened this issue Feb 24, 2022 · 6 comments
Closed

IPFS badge should open native protocol scheme when local node is used #21306

lidel opened this issue Feb 24, 2022 · 6 comments

Comments

@lidel
Copy link

lidel commented Feb 24, 2022

Problem

When IPFS resolution is set to "Brave local node", opening https://en.wikipedia-on-ipfs.org/wiki/Wikipedia/ show "IPFS" badge in address bar:

2022-02-24_20-48

but clicking on it does not open ipns://en.wikipedia-on-ipfs.org/wiki/Wikipedia/
it opens http://ipns://en.wikipedia-on-ipfs.org.ipns.localhost:48080/wiki/Wikipedia/

2022-02-24_20-48_1

Expected bahavior

Brave should open native ipfs:// or ipns://

In this specific case, it should open ipns://en.wikipedia-on-ipfs.org/wiki/Wikipedia/

Other notes

Sounds like we tested "gateway" scenario, but did not check "local node" one when testing fix for #20567

@BigLep
Copy link

BigLep commented Mar 1, 2022

Good catch @lidel . Did you manually find this? I realize this is a question for Brave, but is there a way to have an automated test for this or manual test in a Brave release checklist?

@lidel
Copy link
Author

lidel commented Mar 3, 2022

QA does manual verification before release (e.g. #21462)

afaik there is no way to automate addressbar checks like this one, right @stephendonner?

@stephendonner
Copy link

QA does manual verification before release (e.g. #21462)

afaik there is no way to automate addressbar checks like this one, right @stephendonner?

Not at present; especially since it involves going to chrome:///brave:// schemes, which things like Selenium can't get at.

@spylogsster would this be able to be succinctly covered by browsertests?

@stephendonner
Copy link

stephendonner commented Mar 3, 2022

An additional case, from #21462

Steps:

  1. install 1.38.21
  2. launch Brave
  3. load ipns://ipfs.io
  4. click on Use a Brave local IPFS node
  5. wait for installation to complete
  6. load https://blog.ipfs.io/24-uncensorable-wikipedia
  7. click on the IPFS button/badge in the URL bar

Actual:
Land on http://blog.ipfs.io.ipns.localhost:48081/24-uncensorable-wikipedia/

Expected:
According to our test plan, it should be ipns://blog.ipfs.io/24-uncensorable-wikipedia

@srirambv
Copy link
Contributor

srirambv commented Dec 5, 2022

@lidel this seems to be fixed (mostly) for the original steps with Kubo 0.17.0. Loading https://en.wikipedia-on-ipfs.org/wiki/Wikipedia/ and clicking on the IPFS button loads ipns://en.wikipedia-on-ipfs.org/wiki/Wikipedia/, however #21306 (comment) also seems to work but fails to resolve both ipfs:// or ipns://. Are we good to close this issue as fixed with Kubo update?

21306.mov

@lidel
Copy link
Author

lidel commented Dec 6, 2022

ipfs://{domain-name} is invalid (DNSLink works only with ipns://), so that last error is nothing weird.

Ok to close.

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

No branches or pull requests

4 participants