Difference between revisions of "User:Sardisson/Troubleshoot Camino Bugs and Features Scratchpad"

From Camino Wiki
Jump to navigation Jump to search
(→‎Feature Requests: add peeja's feature request; add version targets)
(→‎Bugs: record the known bug, too)
Line 1: Line 1:
 
==Bugs==
 
==Bugs==
 +
 +
===1.2.2===
 +
*  <s>Sometimes continues trying to launch Camino after encountering an error which should terminate the launching process.</s> ''fixed in Mar 2007 1.2.2 beta''
  
 
==Feature Requests==
 
==Feature Requests==

Revision as of 11:07, 5 January 2009

Bugs

1.2.2

  • Sometimes continues trying to launch Camino after encountering an error which should terminate the launching process. fixed in Mar 2007 1.2.2 beta

Feature Requests

1.2.2

  • possibility to start with about:blank
    Probably the way to implement this is to read a preferred homepage from a user defaults key, then echo it into the profiledir's user.js before launching Camino; this should approximate what Tinderboxen and test harnesses do to launch apps
    • If the last-ordered pref's value is not in quotes, the parsing code barfs right now
    • Sometimes we fail with "profile folder already exists", which seems to be really bad luck with random not being random :/ Did this change appreciably in the dev version?
      • I'm seeing this again on 10.3.9; the last time I looked, the diff was insignificant
      • Maybe in a failure case, that value is getting saved internally?
        • rnd itself gets cleared before being populated on each run, and the profile path is constructed by calling rnd, not by calling some other var that might be saved
      • This (seems) to go away when I re-save on 10.3.9
    • If there is only one pref, the dict is a single line on 10.3.9; it's always at least 3 lines on 10.5
    • On 10.3.9, the prefs are being written with leading spaces somehow; this doesn't happen on 10.5
  • remember location of last-launched Camino
    • Various keys control this, and the interplay between them is not clear; plus, the keys differ between OS versions.

Future

  • handling org.mozilla.camino.plist to ensure freshness
  • option to re-use last fresh profile for testing round-trip bugs
  • Troubleshoot Firefox
    • This would of course be a separate util; most of the needed code exists in the NSPR logging utils and in TC