Add support for Physical Web scanning in Chromium
Reported by
tval...@gmail.com,
May 18 2017
|
||||||
Issue descriptionExample URL: chrome://physical-web Steps to reproduce the problem: 1. Built chromium for Android 2. Open chrome://physical-web 3. There is no result What is the expected behavior? Should display URL from my beacon. What went wrong? I built Chromium for Android from open source and tried to see my beacon on chrome://physical-web but there are no results. At the same time on the same device in Chrome from Google play store it works good. Does it occur on multiple sites: No Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? N/A Chrome version: 60.0.3102.0 Channel: dev OS Version: Flash Version:
,
May 19 2017
PW Scanning only works on official builds of Chrome. We may be able to get a version working in Chromium some day (only a few pieces need swapping out), but this is not available today.
,
May 19 2017
,
May 19 2017
Thanks for your response. How to know when it will be ready?
,
May 19 2017
I changed this bug title to make it a feature request. You can track progress here if you are interested. I do not expect this will be available for a few months. Also, while we may make scanning available to Chromium, the Physical Web server is not available outside of official builds, which means that results will be unfiltered. I still think that will be useful for development/testing.
,
May 19 2017
,
May 19 2017
Thanks a lot. Yes it's interesting for me.
,
May 19 2017
No problem -- could you explain your use case, to help me understand and prioritize?
,
May 19 2017
Oh nothing special, some simple education experiments. And also I interesting about open source contributions to this component :).
,
Jun 7 2017
Issue 699586 has been merged into this issue.
,
Jun 8 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 8 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by candr...@chromium.org
, May 18 2017