confirming 082308, winME
*** Bug 50196 has been marked as a duplicate of this bug. ***
Browser, not engine. Reassigning to DOM Level 0 for further triage -
Nominating for beta3 and reassigning to the sidebar component owner, I see no problems in the DOM code, the problem seems to be in the sidebar component, I get assertions in RDFServiceImpl::GetDataSource()...
Voted and CC'd myself. This is a major bug and should be fixed asap i have a hunch that this bug is directly releated to the switch to JAR's
I agree, this is a major bug. I believe it occured before the switch to Jars though. And, it's marked as on all platforms, and jars are only enabled in win32 so far.
nav triage team: [nsbeta3+] claudius: Isn't this a dupe? This regressed a couple of weeks ago, maybe it's filed in one of the JS components?
*** Bug 50581 has been marked as a duplicate of this bug. ***
From ICP Marketing: We need the Add Button to work for sidebar evangelism programs which are about to start in DE, FR, JA
Added myself to the CC line.
I checked in a fix today. One side note, it seems like the sidebar.addPanel(...) function requires all three arguments now (title, content_url, customize_url).
(Naive question) This is a new requirement, yes? If the tab does not have a customization URL, how should the third argument be coded? This will affect the Sidebar Dev Guide.
I hope a null value for "customize_url" is OK because most of the partners don't have that url.
A null value or an empty string is fine for the customize url.
Linda, I believe our current documentation has it like this: window.sidebar.addPanel (document.title, "http://....", ""); so we are probably OK as far as the documentation is concerned.
verified this is fixed on win/mac/linux builds 2000090508m18.