Closed
Bug 301283
Opened 19 years ago
Closed 19 years ago
Toolbar customize gives js error after removing searchbar
Categories
(Firefox :: Toolbars and Customization, defect, P2)
Firefox
Toolbars and Customization
Tracking
()
RESOLVED
FIXED
Firefox1.5
People
(Reporter: martijn.martijn, Assigned: Gavin)
References
Details
(Keywords: fixed1.8, regression)
Attachments
(1 file)
1.20 KB,
patch
|
mconnor
:
review+
asa
:
approval1.8b4+
|
Details | Diff | Splinter Review |
See also discussion here:
http://forums.mozillazine.org/viewtopic.php?t=293935&start=15&sid=aa28ca0442836f7726db03ef1ccbc994#1614988
To reproduce:
- Open the customize window
- Drag the searchbar into this window
- Click on Done -> error appears:
Error: uncaught exception: [Exception... "Component returned failure code:
0x80004005 (NS_ERROR_FAILURE) [nsIControllers.removeController]" nsresult:
"0x80004005 (NS_ERROR_FAILURE)" location: "JS frame ::
chrome://browser/content/search.xml :: :: line 74" data: no]
Now, every time you open the customize window again and click on 'Done', you get
the same error again.
This doesn't happen in 20050707 build, but it happens in 20050708 build.
Assignee | ||
Updated•19 years ago
|
Assignee: nobody → gavin.sharp
Assignee | ||
Updated•19 years ago
|
Status: NEW → ASSIGNED
OS: Windows 2000 → All
Priority: -- → P2
Hardware: PC → All
Target Milestone: --- → Firefox1.1
Version: unspecified → Trunk
Comment 1•19 years ago
|
||
Is the controller just not there anymore after the first time?
More interestingly, if you customize toolbars to have and then not have the
searchbar, does the searchbar work?
Flags: blocking-aviary1.1?
Comment 2•19 years ago
|
||
Does anything actually break here?
Assignee | ||
Comment 3•19 years ago
|
||
No, nothing breaks, but it may be the cause of memory leaks, and it clutters the
console. This whole situation kind of sucks, but it doesn't really suck any more
than it has on the branch, so this probably shouldn't be considered a blocker.
I'll attach a patch to get rid of the warning.
Assignee | ||
Comment 4•19 years ago
|
||
Assignee | ||
Updated•19 years ago
|
Attachment #190307 -
Flags: review?(mconnor)
(In reply to comment #2)
> Does anything actually break here?
well something breaks, the paste and go extension stops working after that error
msg in the js console until the browser is restarted.
for stops working i mean the paste & go line disappears in ff right click
context menu
Updated•19 years ago
|
Flags: blocking-aviary1.5? → blocking1.8b4+
Assignee | ||
Updated•19 years ago
|
Whiteboard: [patch-r?]
Updated•19 years ago
|
Whiteboard: [patch-r?] → [patch-r?][needs review mconnor]
Updated•19 years ago
|
Attachment #190307 -
Flags: review?(mconnor) → review+
Assignee | ||
Updated•19 years ago
|
Whiteboard: [patch-r?][needs review mconnor]
Assignee | ||
Updated•19 years ago
|
Attachment #190307 -
Flags: approval1.8b4?
Comment 6•19 years ago
|
||
please land this on the trunk and when it's verified there we'll revevaluate for
branch. thanks.
Assignee | ||
Comment 7•19 years ago
|
||
Checked in on trunk. This patch is trivial, it just masks the exception, so the
risk that it effects anything but the JS Console error is close to zero.
Checking in search.xml;
/cvsroot/mozilla/browser/base/content/search.xml,v <-- search.xml
new revision: 1.26; previous revision: 1.25
done
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Updated•19 years ago
|
Attachment #190307 -
Flags: approval1.8b4? → approval1.8b4+
Assignee | ||
Comment 8•19 years ago
|
||
Checked in on the 1.8 Branch.
mozilla/browser/base/content/search.xml; new revision: 1.25.2.1;
Keywords: fixed1.8
(In reply to comment #8)
> Checked in on the 1.8 Branch.
> mozilla/browser/base/content/search.xml; new revision: 1.25.2.1;
Sorry for bugspam but it's not really fixed, you just hide the exception but
paste & go extension still breaks :)
Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8b4) Gecko/20050830
Firefox/1.0+ ID:2005083006
Assignee | ||
Comment 10•19 years ago
|
||
(In reply to comment #9)
> Sorry for bugspam but it's not really fixed, you just hide the exception but
> paste & go extension still breaks :)
If you think a bug marked fixed isn't fixed, that's not bugspam :). The reason
that "Paste and Go" is broken doesn't have anything to do with this bug, though,
it's broken because of bug 306358.
You need to log in
before you can comment on or make changes to this bug.
Description
•