This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 29066 - Should "If mode is local" be "If mode is remote" ?
Summary: Should "If mode is local" be "If mode is remote" ?
Status: RESOLVED MOVED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: https://html.spec.whatwg.org/#loading...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-19 18:12 UTC by contributor
Modified: 2016-02-01 02:26 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2015-08-19 18:12:03 UTC 
Specification: https://html.spec.whatwg.org/
Multipage: https://html.spec.whatwg.org/multipage/#loading-the-media-resource
Complete: https://html.spec.whatwg.org/#loading-the-media-resource
Referrer: https://codereview.chromium.org/1297983002/

Comment:
Should "If mode is local" be "If mode is remote" ?

Posted from: 106.51.232.244
User agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.155 Safari/537.36
Comment 1 Srirama Chandra Sekhar Mogali 2015-08-20 07:35:27 UTC 
This is raised by me. Here is more info about the issue.

1. If the algorithm was invoked with a URL, then let mode be remote, otherwise let mode be local.

2. If mode is local, then let the current media resource be the resource given by the absolute URL passed to this algorithm; otherwise, let the current media resource be the resource given by the media provider object. Either way, the current media resource is now the element's media resource.

In step1 it is mentioned that mode will be remote if URL is passed.
But in step2 media resource is set using URL if the mode is local, shouldn't this be opposite?
Comment 2 Philip Jägenstedt 2016-02-01 02:25:48 UTC 
This was fixed in https://github.com/whatwg/html/issues/316, sorry for missing this bug! (New issues are now handled on GitHub, but that change was after you filed this bug.)