"null" could be interpreted as a relative URL I think. The current handling of relative URLs by plugins is sadly plugin-specific.
On Wed, Jun 19, 2013 at 4:04 PM, Braden Shepherdson <bra...@chromium.org>wrote: > The automated tests for Media frequently call new Media() with no URL, > which sends a null to the "create" action. In the past, this got turned > into the string "null" in Java, which was handled as a file named "null" > that didn't exist, and nothing crashed. > > DataResource is fine with the files not existing, but it's not fine with > "null" as a filename since it neither has a URL scheme nor is it an > absolute path. > > Is there a reason why new Media() should work rather than throwing > IllegalArgumentExceptions for trying to read files with relative paths? > Should I detect and gracefully handle null being given as the media URL in > Javascript? In Java? Should I instead change the mobile-spec tests to use > "file:///dummy" or similar? > > Braden >
