{"action":"created","issue":{"url":"https://api.github.com/repos/facebook/react/issues/1252","labels_url":"https://api.github.com/repos/facebook/react/issues/1252/labels{/name}","comments_url":"https://api.github.com/repos/facebook/react/issues/1252/comments","events_url":"https://api.github.com/repos/facebook/react/issues/1252/events","html_url":"https://github.com/facebook/react/issues/1252","id":29305014,"number":1252,"title":"noscript contents cause invariant violation","user":{"login":"matthewwithanm","id":126263,"avatar_url":"https://avatars.githubusercontent.com/u/126263?v=3","gravatar_id":"","url":"https://api.github.com/users/matthewwithanm","html_url":"https://github.com/matthewwithanm","followers_url":"https://api.github.com/users/matthewwithanm/followers","following_url":"https://api.github.com/users/matthewwithanm/following{/other_user}","gists_url":"https://api.github.com/users/matthewwithanm/gists{/gist_id}","starred_url":"https://api.github.com/users/matthewwithanm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/matthewwithanm/subscriptions","organizations_url":"https://api.github.com/users/matthewwithanm/orgs","repos_url":"https://api.github.com/users/matthewwithanm/repos","events_url":"https://api.github.com/users/matthewwithanm/events{/privacy}","received_events_url":"https://api.github.com/users/matthewwithanm/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/facebook/react/labels/Component:%20DOM%20(general%20issues)","name":"Component: DOM (general issues)","color":"bfd4f2"},{"url":"https://api.github.com/repos/facebook/react/labels/Type:%20Bug","name":"Type: Bug","color":"fc2929"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2014-03-12T21:33:49Z","updated_at":"2015-02-05T09:29:30Z","closed_at":null,"body":"When using server rendering, putting an `<img>` in a `<noscript>` seems to invariably cause an invariant violation (it can't find the image).\r\n\r\nI believe this is because, to the JS enabled browser, the noscript content looks like CDATA.\r\n\r\nThis can be worked around by using `dangerouslySetInnerHTML` to actually set the contents to an HTML string, however, you can't nest components with this approach."},"comment":{"url":"https://api.github.com/repos/facebook/react/issues/comments/73017611","html_url":"https://github.com/facebook/react/issues/1252#issuecomment-73017611","issue_url":"https://api.github.com/repos/facebook/react/issues/1252","id":73017611,"user":{"login":"syranide","id":1714255,"avatar_url":"https://avatars.githubusercontent.com/u/1714255?v=3","gravatar_id":"","url":"https://api.github.com/users/syranide","html_url":"https://github.com/syranide","followers_url":"https://api.github.com/users/syranide/followers","following_url":"https://api.github.com/users/syranide/following{/other_user}","gists_url":"https://api.github.com/users/syranide/gists{/gist_id}","starred_url":"https://api.github.com/users/syranide/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/syranide/subscriptions","organizations_url":"https://api.github.com/users/syranide/orgs","repos_url":"https://api.github.com/users/syranide/repos","events_url":"https://api.github.com/users/syranide/events{/privacy}","received_events_url":"https://api.github.com/users/syranide/received_events","type":"User","site_admin":false},"created_at":"2015-02-05T09:29:30Z","updated_at":"2015-02-05T09:29:30Z","body":"Related #1905 ... should we even set the content of `<noscript>` client-side? (Or technically even render it when React is able to) It's a perf hit and I can't think of a reason you would ever care about the contents of the `<noscript>` when client-side?"}}