Closed Bug 390778 Opened 18 years ago Closed 18 years ago

Bookmarks no longer shown in Bookmarks Toolbar with TabMixPlus 0.3.6.0.070714 extension installed

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: stevee, Unassigned)

References

Details

(Keywords: regression)

1. New profile, start firefox 2. Install TMP 0.3.6.0.070714 from http://tmp.garyr.net/tab_mix_plus-dev-build.xpi 3. Restart firefox Expected: Bookmarks in Bookmarks Toolbar Actual: No Bookmarks in Bookmarks Toolbar, browser consumes 99% CPU time. Works: 20070802_2342_firefox-3.0a7pre.en-US.win32 Broken: 20070802_2359_firefox-3.0a7pre.en-US.win32 Checkins to module PhoenixTinderbox between 2007-08-02 23:42 and 2007-08-02 23:58 : http://bonsai.mozilla.org/cvsquery.cgi?module=PhoenixTinderbox&date=explicit&mindate=1186123320&maxdate=1186124339 Due to bug 378866, but since this is an extension problem I guess it's TMP's responsibility to work?
Actually, scratch the bit about 99% CPU usage, that's wrong. But add this in the error console: Error: uncaught exception: [Exception... "Operation is not supported" code: "9" nsresult: "0x80530009 (NS_ERROR_DOM_NOT_SUPPORTED_ERR)" location: "chrome://tabmixplus/content/tabmix.js Line: 204"]
IMO, we should keep the patch for bug 378866 and if some extensions break, they are doing evil things. Would be great to have minimal testcase of what TMP does.
er, maybe not. Have to test something...
doh, I thought there was a case bug 378866 didn't handle properly, but it should be ok after all.
But I found still one other case bug 378866 doesn't handle (not related to this bug), so I'll have to back it out.
(In reply to comment #5) > But I found still one other case bug 378866 doesn't handle (not related > to this bug), so I'll have to back it out. > Or I may have to back it out.
Backed out bug 378866.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.