26105 2014-06-16 11:27:54 +0000 Consider making .crossOrigin nullable 2014-08-28 22:00:38 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#cors-settings-attribute P3 normal Unsorted 1 contributor ian ian jonas mike w3c zcorpan contributor oldest_to_newest 107853 0 contributor 2014-06-16 11:27:54 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/fetching-resources.html Multipage: http://www.whatwg.org/C#cors-settings-attribute Complete: http://www.whatwg.org/c#cors-settings-attribute Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/edits.html Comment: Consider making .crossOrigin nullable so that elm.crossOrigin = elm.crossOrigin doesn't change state from No CORS to Anonymous, and so that you don't have to use removeAttribute to switch to the No CORS state. IDL would change `DOMString` to `DOMString?`. On getting, if the state is No CORS, return null. On setting, if the value is null, remove the content attribute. Also see https://www.w3.org/Bugs/Public/show_bug.cgi?id=24958#c1 Posted from: 90.230.218.37 by simonp@opera.com User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.114 Safari/537.36 OPR/22.0.1471.40 (Edition Next) 108030 1 ian 2014-06-18 21:24:21 +0000 Interesting idea. Any vendor interest? 108047 2 jonas 2014-06-19 02:06:04 +0000 Sounds good to me 110735 3 contributor 2014-08-28 22:00:38 +0000 Checked in as WHATWG revision r8727. Check-in comment: Make .crossOrigin = null remove the content attribute. http://html5.org/tools/web-apps-tracker?from=8726&to=8727