Open
Bug 451647
Opened 16 years ago
Updated 3 years ago
Reduce side effects of isDefaultClient/shouldCheckDefaultClient in shell service code
Categories
(SeaMonkey :: OS Integration, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: mcsmurf, Unassigned)
References
Details
Currently when isDefaultClient (interface nsIShellService) is called with the first parameter being true, it changes the return value of shouldCheckDefaultClient. This can be problematic as shouldCheckDefaultClient is often used together with isDefaultClient in if statements and so the order of those two commands will determinate whether the if statement is true or false. Possible way to fix this is that calling GetShouldCheckDefaultClient will change mCheckedThisSessionClient to true and isDefaultClient would no longer change mCheckedThisSessionClient and the first parameter could then be removed.
Reporter | ||
Updated•15 years ago
|
Assignee: general → nobody
Component: General → OS Integration
QA Contact: general → os-integration
You need to log in
before you can comment on or make changes to this bug.
Description
•