Closed Bug 188874 Opened 22 years ago Closed 20 years ago

windows NT/XP and future integration and schedule of conditions track bug

Categories

(Core Graveyard :: Tracking, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED
Future

People

(Reporter: le.iota, Assigned: le.iota)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b; MultiZilla v1.1.33 (b)) Gecko/20030111 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b; MultiZilla v1.1.33 (b)) Gecko/20030111 tracking all issues and claims that should be reported or claimed to micro$oft and those which need a dodgy and actual Mozilla bugs on these platform: windows XP service packs scheduled versions of window$ including open source project (2004-2005?) Reproducible: Always Steps to Reproduce: 1. install window$ 2. try and install mozilla 3. track installation and integration problems Actual Results: Examples: news client cannot be assigned to Mozilla Calendar cannot be assigned to Mozilla Adress book cannot be assigned to Mozilla Mozilla is shown as only one task in TM royalties aren't reversed to Mozilla by Micro$oft Expected Results: news client is assigned to Mozilla during installation and can be reassigned to another newsclient Calendar is assigned to Mozilla and can be reassigned to any "agenda" Adress book idem Each Mozilla component is shown as a task in TM and in case of a problem with a 3rd party program as acrobat reader or JVM, Mozilla is not frosen by window$ Microsoft reverse royalties to Mozilla project :-D
Depends on: MS, 186170
Whiteboard: DUPEME
Actually depends on bug 114158 if it is duplicate of a bug this bug depends on bug 114158 too or is bug 114158
no bug 114158 is onyl TECH EVANG (problems with MS sites) This bug is about OS integration. Bug 186170 is about a bugzilla feature. this here : news client cannot be assigned to Mozilla Calendar cannot be assigned to Mozilla Adress book cannot be assigned to Mozilla Mozilla is shown as only one task in TM this is only XP APPS and it's invalid as general bug (since many of this is already in other bugs and they all belong to different components. But you can of course have your own tracking bug -> tracking and to reporter
Assignee: asa → le.iota
Component: Browser-General → Tracking
Whiteboard: DUPEME
please accept, reassign or invalidate
Assignee: le.iota → chofmann
QA Contact: asa → chofmann
Target Milestone: --- → Future
unwanted reassignment. this is mine.
QA Contact: chofmann → asa
Assignee: chofmann → le.iota
QA Contact: asa → le.iota
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.