Closed Bug 1184036 (1-UA_Presentation_API) Opened 7 years ago Closed 9 months ago

[meta] 1-UA support for Presentation API

Categories

(Core :: DOM: Core & HTML, enhancement, P5)

enhancement

Tracking

()

RESOLVED WONTFIX
mozilla52

People

(Reporter: schien, Unassigned)

References

Details

(Keywords: feature, meta, Whiteboard: [ft:conndevices])

This is the meta bug for supporting non-Web-compatible presentation display, e.g.:

1. HDMI
2. Wifi Display
3. ChromeCast/Roku/DIAL-compatible devices
In my understanding Chromecast fits the 2-UA case.

Is it a typo or is it because it would introduce a case where the presentation browsing context does not have the same rendering engine as the controller (gecko vs blink)?

This could be ok but it would also mean that presenting on a Chromecast would not look the same when controlled from Chrome or from Firefox.

I mentioned my concerns about Chromecast and 1-UA vs 2-UA at https://github.com/w3c/presentation-api/issues/164
Depends on: 1208417
Depends on: 1224445
No longer depends on: 1224445
Alias: 1-UA_Presentation_API
Depends on: 1235124
Depends on: 1235123
Depends on: 1262779
Whiteboard: [ft:conndevices]
No longer depends on: 1267122
Keywords: feature
Target Milestone: --- → mozilla52
Depends on: 1311375
Depends on: 1313368
Depends on: 1313404
Depends on: 1304971
Depends on: 1304978
Depends on: 1304976
Depends on: 1314229
Depends on: 1304969
Depends on: 1316584
Depends on: 1316592
Depends on: 1317372
Priority: -- → P2
Component: DOM → DOM: Core & HTML
Type: defect → enhancement
Priority: P2 → P5
See Also: → Chromecast

Bug 1697680 removed Presentation API implementation.

Status: NEW → RESOLVED
Closed: 9 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.