User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.115 Safari/537.36 Steps to reproduce: 1. Set dom.webcomponents.enabled to true 2. Go to https://www.polymer-project.org/components/paper-elements/demo.html#core-toolbar Actual results: This crashed Firefox 36. We have some custom elements using webcomponentsjs (github.com/webcomponents/webcomponentsjs) and it also crashes in FF 36. Expected results: Should not crash Firefox. This works fine with FF 35 with dom.webcomponents.enabled = true. Recent Firefox 35 Crash Report IDs: * 10B6BFC7-3B52-42CC-9071-381FC1F24056 2/03/2015 13:35 * bp-5b2d7c27-9b84-405e-8d31-4a8492150302 2/03/2015 13:32
Thanks for the report! The URL seems to have changed to https://www.polymer-project.org/0.5/components/paper-elements/demo.html#core-toolbar I can't reproduce using the nightly build, nor with 36.0.3, and the crash report ID you posted doesn't seem to appear in recent crash stats. Can you still reproduce? (Note that only the second crash ID (bp-*) you posted was sent to mozilla; you need to click on the link for it to get sent.)
Severity: normal → critical
Crash Signature: [@ mozilla::dom::ImportManager::GetNearestPredecessor(nsINode*)]
Component: Untriaged → DOM
Product: Firefox → Core
Summary: Sites using WebComponents (e.g. polymer) crashes Firefox when dom.webcomponents.enabled is true → [WebComponents] polymer demo crashes Firefox 36 [@ mozilla::dom::ImportManager::GetNearestPredecessor(nsINode*)]
I've moved on to FF 37 (beta channel) and although going to https://www.polymer-project.org/0.5/docs/elements/paper-button.html doesn't crash the browser anymore, it's also not rendering the page properly (as compared to setting dom.webcomponents.enabled = false).
(In reply to Jan Alonzo from comment #2) > I've moved on to FF 37 (beta channel) and although going to Sorry, FF 37 (which is now stable). > https://www.polymer-project.org/0.5/docs/elements/paper-button.html doesn't > crash the browser anymore, it's also not rendering the page properly (as > compared to setting dom.webcomponents.enabled = false). Same rendering issues. The icons are really big compared to when dom.webcomponents.enabled = false.
Polymer is not compatible with our web components implementation, and in its current state probably never will be. It basically assumes things that are specific to Chrome's implementation (e.g. assumes a certain set of things are all implemented together, though we don't plan to implement some of them and some of them may not end up being standardized at all). This is a known issue in Polymer that we have reported to them... Obviously it should not crash, but the incorrect rendering is very much expected, though unfortunate.
Bug 1107662 is the Polymer compatibility issue.
OK. So if 37 and newer is not crashing, this is probably worksforme.
Crash Signature: [@ mozilla::dom::ImportManager::GetNearestPredecessor(nsINode*)] → [@ mozilla::dom::ImportManager::GetNearestPredecessor(nsINode*)] [@ mozilla::dom::ImportManager::GetNearestPredecessor]
You need to log in before you can comment on or make changes to this bug.