{"action":"created","issue":{"url":"https://api.github.com/repos/Polymer/vulcanize/issues/231","repository_url":"https://api.github.com/repos/Polymer/vulcanize","labels_url":"https://api.github.com/repos/Polymer/vulcanize/issues/231/labels{/name}","comments_url":"https://api.github.com/repos/Polymer/vulcanize/issues/231/comments","events_url":"https://api.github.com/repos/Polymer/vulcanize/issues/231/events","html_url":"https://github.com/Polymer/vulcanize/issues/231","id":102167855,"number":231,"title":"Polymer 1.10.0 does not work in Firefox when vulcanized","user":{"login":"makroiss","id":4398091,"avatar_url":"https://avatars.githubusercontent.com/u/4398091?v=3","gravatar_id":"","url":"https://api.github.com/users/makroiss","html_url":"https://github.com/makroiss","followers_url":"https://api.github.com/users/makroiss/followers","following_url":"https://api.github.com/users/makroiss/following{/other_user}","gists_url":"https://api.github.com/users/makroiss/gists{/gist_id}","starred_url":"https://api.github.com/users/makroiss/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/makroiss/subscriptions","organizations_url":"https://api.github.com/users/makroiss/orgs","repos_url":"https://api.github.com/users/makroiss/repos","events_url":"https://api.github.com/users/makroiss/events{/privacy}","received_events_url":"https://api.github.com/users/makroiss/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-08-20T15:36:30Z","updated_at":"2016-02-19T20:12:02Z","closed_at":"2015-08-20T17:27:15Z","body":"Example:\r\n\r\n\t<!doctype html>\r\n\t<html>\r\n\r\n\t<head>\r\n\t\t<script src=\"bower_components/webcomponentsjs/webcomponents-lite.js\"></script>\r\n\t\t<link rel=\"import\" href=\"bower_components/polymer/polymer.html\">\r\n\t</head>\r\n\r\n\t<body>\r\n\t\t<dom-module id=\"app-test\">\r\n\t\t\t<template>\r\n\t\t\t\t<div>TEST</div>\r\n\t\t\t</template>\r\n\t\t</dom-module>\r\n\t\t<script>\r\n\t\t\tPolymer({\r\n\t\t\t\tis: \"app-test\",\r\n\t\t\t\tattached: function () {}\r\n\t\t\t});\r\n\t\t</script>\r\n\t\t<app-test></app-test>\r\n\t</body>\r\n\r\n\t</html>\r\n\r\nShows a blank page in Firefox when vulcanized."},"comment":{"url":"https://api.github.com/repos/Polymer/vulcanize/issues/comments/186384332","html_url":"https://github.com/Polymer/vulcanize/issues/231#issuecomment-186384332","issue_url":"https://api.github.com/repos/Polymer/vulcanize/issues/231","id":186384332,"user":{"login":"samccone","id":883126,"avatar_url":"https://avatars.githubusercontent.com/u/883126?v=3","gravatar_id":"","url":"https://api.github.com/users/samccone","html_url":"https://github.com/samccone","followers_url":"https://api.github.com/users/samccone/followers","following_url":"https://api.github.com/users/samccone/following{/other_user}","gists_url":"https://api.github.com/users/samccone/gists{/gist_id}","starred_url":"https://api.github.com/users/samccone/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/samccone/subscriptions","organizations_url":"https://api.github.com/users/samccone/orgs","repos_url":"https://api.github.com/users/samccone/repos","events_url":"https://api.github.com/users/samccone/events{/privacy}","received_events_url":"https://api.github.com/users/samccone/received_events","type":"User","site_admin":false},"created_at":"2016-02-19T20:12:02Z","updated_at":"2016-02-19T20:12:02Z","body":"Ok did some more thinking on this one and the issue is pretty interesting...\r\n\r\nFor the normal vulcanize case the script tag is at the bottom of the elements import... thus this is never an issue, however if you want to force the browser to cache bust the elements.js file on deploy to a production facing site you will end up using the no script option inside of crisper... which give you the responsibility for including elements.js somewhere in your page\r\n\r\n\r\nNow since the script tag could be outside of the sync DL and process path that the default approach takes ... (script tag at the bottom of the file) you can hit this issue!\r\n\r\nWhy this is an issue only in firefox.. is still a bit of a mystery to me, I am guessing there are some implementation wrinkles between firefox parse order and chrome parse order, perhaps @azakus has some insights on this :)\r\n\r\nAnyway... I think this is a pretty interesting \"common\" path case for people -- and something worth figuring out "}}