Closed Bug 127533 Opened 23 years ago Closed 23 years ago

Cached .XUL files no longer handeled internally..

Categories

(Core :: XUL, defect)

x86
Windows ME
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 127322

People

(Reporter: oysteimo, Assigned: hyatt)

References

Details

When the sidebar is launched first time, the bookmarks and history loads normally, but when you try to swap between the tabs, Mozilla starts to ask for which application should handle it (save file/open with dialog). This happens when trying to open cached .xul files. Reinstall of mozilla did not resolve the problem, even with changed locations, so it's profile related. XUL-tests work normally.
MIME type suggested by Mozilla: mozilla.application/cached-xul Files: history-panel.xul bm-panel.xul
Bug does not exist in build 2002020406, but when I installed latest build (2002022308) it started to show up again.
so then its just a profile problem using more than one build on the same profile, delete the old profile. There are several other profile related bugs in bugzilla, but many have to be fixed.. so even if backwards compatability is an issue for some users of netscape 6.x profiles, we will have to create new profiles when there is another release anyway for other significant bugs in here, so I'm saying this is a non-issue, because it works fine with a new fresh profile.
This is almost certainly a duplicate of blocker bug 127322 (which happens with a fresh profile as all smoketest blockers must). So the old profile explanation is bogus.
Depends on: 127322
A new, fresh profile don't do the trick (I tried that..). You can create a fresh one, but as soon as you go up to one of the newer builds you get problems..
Confirmed with build 2002022203 win32 installer trunk should this bug and bug 127322 go to networking: cache?
Status: UNCONFIRMED → NEW
Ever confirmed: true
sending to XUL
Assignee: sgehani → hyatt
Component: Sidebar → XP Toolkit/Widgets: XUL
QA Contact: sujay → jrgm
ok, I guess that should have fixed it. Kinda like starting from scratch, it should work. I see another bug 127044, maybe caused by something related here.
*** Bug 127709 has been marked as a duplicate of this bug. ***
on bug 127322 it was found that this does not happen with the classic or modern theme but does on other themes. Maybe something about the design of the classic and modern theme is preventing this from happening? Or something missing or wrong with the other themes as they might not match the current builds as well since they were designed for mozilla0.9.8 ? Either way, even if the theme has issues, it shouldn't work this way.
It seems the problem might be theme-related. When using modern or classic, I don't get any problems, but when using Lo-Fi it kicks in immediately... Pity.. nice theme..:(
*** Bug 128781 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 127322 ***
Status: NEW → RESOLVED
Closed: 23 years ago
No longer depends on: 127322
Resolution: --- → DUPLICATE
Depends on: 127322
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.