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

From Camino Wiki
Jump to navigation Jump to search
(→‎Feature Requests: another bug in the dev version)
Line 4: Line 4:
 
* handling <tt>org.mozilla.camino.plist</tt> to ensure freshness
 
* handling <tt>org.mozilla.camino.plist</tt> to ensure freshness
 
* possibility to start with about:blank
 
* 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
+
*: 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
 
** 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?
 
** 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?
 
* remember location of last-launched Camino
 
* remember location of last-launched Camino
 
* option to re-use last fresh profile for testing round-trip bugs
 
* option to re-use last fresh profile for testing round-trip bugs

Revision as of 22:13, 2 June 2008

Bugs

Feature Requests

  • handling org.mozilla.camino.plist to ensure freshness
  • 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?
  • remember location of last-launched Camino
  • option to re-use last fresh profile for testing round-trip bugs