mac only. this is a regression since hadn't happened before. over to jj --he's away...um, who could fix this in the interim? nominating for beta3, in hopes that it can get fixed by then.
Assignee: cls → jj
Keywords: nsbeta3, pp, regression
!? i wouldn't think that this would be a commercial-only feature. the js console would be quite a useful tool...
we have the js console, just not an icon to launch it. It can be launched from mozilla Tasks|Tools menu item.
Sairuh, This is very strange. Neither the mozilla nor the commercial packages-mac manifests reflect this file. In fact, I just installed the 3pm commercial build and can find no such file. Are you sure someone didn't create this on your machine explicitly?
samir: that is odd. nope, it was definitely part of the 2000.08.29.08 opt commercial build (i used the macbinary sea, not the installer). in fact, the js console icon has been part of the build since i wrote the test plan for such components, back in mid-july. i only recently noticed that the filetype has differed. should this icon not exist, then?
BTW, when I said "we have no control over..." I was referring to the installer folks. I'm assuming we will not be distributing the .sea.bin archive for public consumption.
we push the mac mozilla non-installer blob (ftp://ftp.mozilla.org/pub/mozilla/nightly/2000-08-30-08-M18/mozilla-mac-M18.sea.bin) to mozilla.org along with the mac mozilla installer blob. for netscape 6, we put the non-installer blob up on ftp.netscape.com for PR1 and PR2 since the installer was not available, and broken, respectively. Last I heard, we had fixed the mac installer for PR2 and had pushed out the installer and removed the links to the non-installer PR2 blob. The plan that build release is working from is that we will only be shipping installer bits come RTM.
Thanks for the clarification Jon! So we need to worry about this for Mozilla but not for Netscape 6.
well, I wouldn't say we need to worry about it for mozilla either. basically, we only need to worry about it if someone says this icon should be in the installer builds. If it's supposed to be in the installer builds and it isn't that's a problem. If it's just a handy thing someone put into :viewer:bin that's getting picked up in the blob, then we can resolve this invalid.
Status: NEW → ASSIGNED
Keywords: nsbeta3, pp, regression → rtm
Whiteboard: [rtm need info] which package needs this file?
This bug isn't really a pull it off the wire buts. If we don't get this bug moving so it's rtm+ by the end of the day it's not going to make rtm++.
no activity in a week. rtm-
Whiteboard: [rtm need info] which package needs this file? → [rtm-] which package needs this file?
No, there is no `decode' app on these computers, and the shortcuts do fire up Mozilla as expected. But Mac OS still refers to a Mozilla shortcut as a `decode document'. Is no-one else seeing this? Should I file a separate bug?
Looking at any of the mozilla shortcuts in the install directory (Mozilla Profile Migration, Mozilla Preferences, MozillaEditor, any of them) command I displays Info that says "Kind: decode document". Also strange that the Install Log is classified as decode document and Mozilla Preferences shortcut doesn't have the "-URL (mozilla icon)" icon.
When we AppleSingle decode during installation we create a temporary file named "decode" (or "decode-1", "decode-2", etc. if "decode" already exists). Somehow this is being left around. We /do/ set the finder info so I'm not sure why the original temp file name is being associated as the document "type". Simon, any insight?
Most of these shortcuts have been removed now, so this is moot. But I don't know why things are showing up as 'decode' documents, unless the installer creates a temporary file called 'decode', with type 'APPL' and creator 'MOSS' or 'MOZZ'. Is this the case, samir?
type = '????' creator = 'MOZZ' http://lxr.mozilla.org/seamonkey/source/xpinstall/src/nsAppleSingleDecoder.cpp#114 Should we change the creator to '????' too?
Marking fixed since this file is no longer part of the Netscape build. If not done yet, a new bug should opened about the file type/creator assigned by the installer as well as the "leftover" "decode" document. (samir?)
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
Bug 59217 filed regarding the creator for the temp doc during AppleSingle decoding.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.