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 23967 - how to include an insecure js in chrome?
Summary: how to include an insecure js in chrome?
Status: RESOLVED NEEDSINFO
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: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-03 10:52 UTC by contributor
Modified: 2013-12-05 18:35 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2013-12-03 10:52:19 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/fetching-resources.html
Multipage: http://www.whatwg.org/C#potentially-cors-enabled-fetch
Complete: http://www.whatwg.org/c#potentially-cors-enabled-fetch
Referrer: http://stackoverflow.com/questions/5913978/cryptic-script-error-reported-in-javascript-in-chrome-and-firefox

Comment:
how to include an insecure js in chrome?

Posted from: 148.107.1.20
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.57 Safari/537.36
Comment 1 Ian 'Hixie' Hickson 2013-12-05 18:35:10 UTC 
What do you mean by "insecure JS"? Do you mean cross-site? If so, the stackoverflow question cited above actually gives some techniques for doing this.