Closed Bug 77358 Opened 24 years ago Closed 24 years ago

mozilla unable to read google sidebar

Categories

(SeaMonkey :: Sidebar, defect)

Product:
SeaMonkey
Component:
Sidebar
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED
Milestone:
mozilla0.9.3

People

(Reporter: andreww, Assigned: amitp)

References

Details

steps to replicate: launch mozilla (2001042304) choose Tabs-->Customize My Sidebar under available tabs, go to "sidebar directory" and expand that Choose Google as a sidebar. click ok you will now see the following error message: this file has mime type application/vnd.mozilla.xul+xml and cannot be viewed using Netscape 6. blah blah.... and asks me to download it. Thus rendering the google sidebar inoperative.
From: http://www.google.com/intl/en_extra/mozilla/google-search.html Warning: Mozilla starting with build 2001-03-21 uses different syntax for XUL. This breaks the Google sidebar and most other XUL documents.
When I get a chance, I'll make another sidebar XUL for the newer Mozillas. And I need to hack the webserver to send different MIME types for the older and newer ones. Ew.
*** Bug 79646 has been marked as a duplicate of this bug. ***
*** Bug 80429 has been marked as a duplicate of this bug. ***
Amitp: the server hackery required is minimal - XUL does not require a .xul file extension, so just set up the server to serve e.g. .xulold as text/xul and .xul as the proper MIME type. You could browser sniff on the Gecko date string to direct people to the correct version. Gerv
lets get this in for 0.9.3
Target Milestone: --- → mozilla0.9.3
Do the Netscape-branded products include a Gecko date string for browser sniffing? Unless browser sniffing will work in most cases, since there are already lots of people out there using the *.xul file, I guess I'll make a .xulnew for 0.9 and leave .xul for older Mozillen and Netscape 6.
Is there any change needed on the client side or can this bug be taken care of by Amit on the server side?
I think this needs to be handled on the server side - Amit how this is going?
Assignee: matt → amitp
I'm working on the new XUL file but I'm still a little confused. I saw that <text> becomes <label>. But bug 70745 says that <html> goes away. I'm using <html:script> in the Google.XUL. What should I do with it? I guess the answer to Viswanath's question is -- the server changes are no problem (I got approval for them last week). The problem is that I don't know all the changes I need to make to the XUL file. I'll mess with it for a little while longer; if I don't get anywhere, I'll ask someone here for help.
Status: NEW → ASSIGNED
only <html> the tag, not <html:foo> the namespace. you can include any namespace you want. But XUL now doesnt have a <xul:html> tag for wrapping text. so you could keep the <html:script>
<xul:script> should work just like <html:script> so you should just use <script>.
Thanks -- I've gotten everything working locally. Now I'm awaiting a code review from a fellow Googler. There will be a google.xul2 for the new XUL code and google.xul will still be there for people who won't upgrade. I'll have more news in a day or two.
Okay, there's now a google.xul2 file for the newer Mozilla, and google.xul will remain for older Mozilla. Plus, browser sniffing -- if it looks like a newer Mozilla, Google will serve the right thing when you ask for google.xul.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
verified on 7/11 trunk. Andrew, this should work for you now....
Status: RESOLVED → VERIFIED
server side fix also works now on the branch builds: win32 2001-07-11-16-0.9.2.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.