#1704 closed defect (fixed)
FF3: Follow up with Mozilla about trac 1640
Reported by: | James Burke | Owned by: | James Burke |
---|---|---|---|
Priority: | high | Milestone: | 1.1 |
Component: | Loader | Version: | 0.3 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
We have a workaround for the Firefox hang in trac #1640, but we should investigate more and engage Mozilla to find the core issue.
Change History (12)
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
Owner: | changed from alex to Adam Peller |
---|
Adam or Koranteng will handle this.
comment:3 Changed 14 years ago by
Filed bug with Mozilla: https://bugzilla.mozilla.org/show_bug.cgi?id=358387 Will follow up with Mozilla team
comment:4 Changed 14 years ago by
Ok, so we have our initial answer from Mozilla. The code is completely broken and is fixed in the trunk. I verified this. What does this mean? We won't see the fix in a release until mid-2007 at best (Firefox 3.0) Can we deal with the workaround until then?
The ThreadManager? is not something they will retrofit into 2.0. Apparently, it's too complex and probably too risky.
I'm thinking this will end up as a "won't fix" on our end, with us settling on one of our workarounds until FF3.0.
comment:5 Changed 14 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
looks like we wait for this one
comment:7 Changed 13 years ago by
Milestone: | → 1.1 |
---|---|
Resolution: | wontfix |
Status: | closed → reopened |
comment:8 Changed 13 years ago by
Owner: | changed from Adam Peller to James Burke |
---|---|
Status: | reopened → new |
Summary: | Follow up with Mozilla about trac 1640 → Firefox 3: Follow up with Mozilla about trac 1640 |
This may be fixed in Firefox 3. In that case, revisit the logic for enableMozDomContentLoaded.
comment:9 Changed 13 years ago by
Summary: | Firefox 3: Follow up with Mozilla about trac 1640 → FF3: Follow up with Mozilla about trac 1640 |
---|
comment:10 Changed 13 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:11 Changed 13 years ago by
I also added a note to the bugzilla bug mentioning that the issue seems to be fixed.
comment:12 Changed 12 years ago by
I had a chat with key people at Mozilla today regarding https://bugzilla.mozilla.org/show_bug.cgi?id=444322 ... a strong patch was reviewed today. They're going to do everything possible to get this into 3.0.5... no guarantees, but that's what they want to do for us.
A possible (and partial) workaround for #1640 is to :
Details :
Tried it with the current dojo HEAD and it works all right. dojo will still hang if you have really large (>64k) images included from css.
Sorry if this is not the right track to post the workaround.