Open Bug 1586160 Opened 2 years ago Updated 2 months ago

[meta] Support Web Share API and Web Share Target in devtools

Categories

(DevTools :: General, task)

task
Not set
normal

Tracking

(Not tracked)

People

(Reporter: marcosc, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: meta)

As part of prototyping with the Web Share API and Web Share Target, we would like to see if there is anything we could add to Firefox's devtools to make the experience better for developers.

Blocks: 1476515

I'm looking for a bug about Web Share API https://w3c.github.io/web-share/ but this is the only one I can find. Is Web Share API being implemented as well, and should there be a meta bug for it?

I've found bug 1312422 now but it's closed. I can't quite tell if this is on its way to stable or not :)

Thanks for the report Marcos!

  • I am moving this to General component since it isn't clear what panel (or multiple panels) in DevTools will support this feature.
  • I am turning this into meta so we can track the work

Some resources:

Marcos, the feature isn't available in Nightly (at least navigator.share is undefined for me), is there any chance to test it? (e.g. flip a pref?)

Honza

Type: enhancement → task
Component: DOM → General
Keywords: meta
Summary: Support Web Share API and Web Share Target in devtools → [meta] Support Web Share API and Web Share Target in devtools

Looking at bug 1586158, it looks like the Application panel could use that info and show list of share targets.

Honza

Hi Philip!

(In reply to Philip Jägenstedt [:foolip] from comment #2)

I've found bug 1312422 now but it's closed. I can't quite tell if this is on its way to stable or not :)

Not yet, unfortunately - and I'm not sure when we will see it in a product: the DOM implementation only covers the DOM API - but doesn't include OS integration.

Having said that, we do have some OS integration on the way:

  • Android - bug 1402369 - landed, but not shipped yet AFAIK. This will probably be the first platform where we will support it.
  • Windows 10 - bug 1573029 - landed, but requires special Windows 10 API that's still in Windows preview builds.
  • Mac OS, Linux - no work planned yet.

I imagine that eventually and "intent to ship" will be announced on dev-platform when it gets pref'ed on on one of the above platforms.

(In reply to Jan Honza Odvarko [:Honza] (always need-info? me) from comment #3)

Marcos, the feature isn't available in Nightly (at least navigator.share is undefined for me), is there any chance to test it? (e.g. flip a pref?)

In about:config, toggle dom.webshare.enabled ... that will only enable the DOM API, however.

You may be able to play with it on Windows (but may require one of the preview builds), but :saschanaz will need to provide some instructions.

Flags: needinfo?(krosylight)

You may be able to play with it on Windows (but may require one of the preview builds), but :saschanaz will need to provide some instructions.

You need to install Windows Insider build slow/fast ring to get the API enabled, just as how Nightly enables an experimental feature. AFAIK the specific API form we using is stable and simple enough, though.

Flags: needinfo?(krosylight)

Okay, an update: The Windows API is available on build 19041.207 which will be GA in May 2020. I'm currently waiting for documentation update and will turn on the flag by default on Nightly after GA.

(In reply to Kagami :saschanaz from comment #8)

Okay, an update: The Windows API is available on build 19041.207 which will be GA in May 2020. I'm currently waiting for documentation update and will turn on the flag by default on Nightly after GA.

Sounds great. Please be sure to send out and "Intent to Ship" when you do.

The meta keyword is there, the bug doesn't depend on other bugs and there is no activity for 12 months.
:Honza, maybe it's time to close this bug?

Flags: needinfo?(odvarko)

I think this is just reversed?

No longer blocks: 1476515
Depends on: 1476515
Flags: needinfo?(odvarko)
Depends on: 1666203
No longer depends on: 1666203
You need to log in before you can comment on or make changes to this bug.