Closed
Bug 1254477
Opened 8 years ago
Closed 8 years ago
[Presentation WebAPI] receiver should always return null for the defaultRequest
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
People
(Reporter: schien, Assigned: kershaw)
References
()
Details
(Whiteboard: btpp-backlog [ETA 5/26] [ft:conndevices])
Attachments
(1 file, 1 obsolete file)
2.84 KB,
patch
|
kershaw
:
review+
jocheng
:
approval-mozilla-b2g48+
|
Details | Diff | Splinter Review |
According to the latest spec: A user agent that is a receiving user agent but not a controlling user agent MUST always return null for the defaultRequest attribute. It MUST treat setting the defaultRequest attribute as a no-op.
Reporter | ||
Comment 1•8 years ago
|
||
We can either check the 'mReceiver' in Presentation object or use the role introduced in bug 1234492.
Updated•8 years ago
|
Whiteboard: btpp-backlog
Reporter | ||
Updated•8 years ago
|
blocking-b2g: --- → 2.6?
Reporter | ||
Updated•8 years ago
|
Whiteboard: btpp-backlog → btpp-backlog [ETA 5/26]
Assignee | ||
Comment 2•8 years ago
|
||
Assignee: nobody → kechang
Attachment #8756718 -
Flags: review?(bugs)
Comment 3•8 years ago
|
||
Comment on attachment 8756718 [details] [diff] [review] Return null for defaultRequest I think the spec should be clearer about what happens when the attribute is set on receiving side. Like mention that the operation is no-op.
Attachment #8756718 -
Flags: review?(bugs) → review+
Assignee | ||
Comment 4•8 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=ea4f9ace31b5
Assignee | ||
Comment 5•8 years ago
|
||
(In reply to Olli Pettay [:smaug] from comment #3) > Comment on attachment 8756718 [details] [diff] [review] > Return null for defaultRequest > > I think the spec should be clearer about what happens when the attribute is > set on receiving side. Like mention that the operation is no-op. Thanks for reviewing. As comment #0 said, the spec do mention this.
Assignee | ||
Comment 6•8 years ago
|
||
Attachment #8756718 -
Attachment is obsolete: true
Attachment #8756894 -
Flags: review+
Assignee | ||
Updated•8 years ago
|
Keywords: checkin-needed
Comment 8•8 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/d4a5ef2ca595
Status: NEW → RESOLVED
Closed: 8 years ago
status-firefox49:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla49
Assignee | ||
Updated•8 years ago
|
Attachment #8756894 -
Flags: approval-mozilla-b2g48?
Assignee | ||
Comment 9•8 years ago
|
||
Josh, please help to approve. Thanks. NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings. [Approval Request Comment] Bug caused by (feature/regressing bug #): Presentation API User impact if declined: The behavior of presentation defaultRequest cannot be aligned with spec. Testing completed: with automation test Risk to taking this patch (and alternatives if risky): low String or UUID changes made by this patch: n/a
Flags: needinfo?(jocheng)
Assignee | ||
Updated•8 years ago
|
Whiteboard: btpp-backlog [ETA 5/26] → btpp-backlog [ETA 5/26] [ft:conndevices]
Comment 10•8 years ago
|
||
Comment on attachment 8756894 [details] [diff] [review] Return null for defaultRequest, r=smaug Approve for TV 2.6
Flags: needinfo?(jocheng)
Attachment #8756894 -
Flags: approval-mozilla-b2g48? → approval-mozilla-b2g48+
Updated•8 years ago
|
status-b2g-v2.6:
--- → affected
Comment 11•8 years ago
|
||
https://github.com/mozilla-b2g/gecko-b2g/commit/cbfb889346d87b01c43cece070c13c2064bc40bb
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•