Firefox in Safe Mode ignores this preference. The only added pref is _resumed_crashes (default value: 1) which determines after how many consecutive crashes about:sessionrestore is displayed (setting that value to -1 prevents the page from being displayed).Can the end user configure settings, via a UI or about:config? Hidden prefs? Environment variables?.No files are involved, all required data is stored inside the about:sessionrestore page and then backed up by SessionStore as form data is backed up for all web pages.Can its files be corrupted by failures? Does it clean up any locks/files after crashes?.The user can decide to restore the crashing session (potentially unselecting unwanted tabs) or load the homepage (which loads in the same tab, so undo is possible).What failure modes or decision points are presented to the user?.None, the data is provided by nsSessionStore.None/a restored session (same as to what SessionStore already does).Session data as provided by nsISessionStore (JSON format).What data is read or parsed by this feature.
Firefox sessionrestore batches code#
None (besides the SessionStore service component where the code has been added).What other modules are used (REQUIRES in the makefile, interfaces).Does it change any existing interfaces?.Are the externally visible interfaces documented clearly enough for a non-Mozilla developer to use them successfully?.Explain the significant file formats, names, syntax, and semantics.Does it interoperate with a web service? How will it do so?.Please provide a table of exported interfaces (APIs, ABIs, protocols, UI, etc.).about:sessionrestore is displayed before the user could enter private browsing mode.How are transitions in/out of Private Browsing mode handled?.It is assumed that correctly implementing nsIAboutModule prevents this from happening. Web content must not be able to access about:sessionrestore, as this page contains potentially sensitive data (the whole session) and the possibility to load arbitrary URLs/cookies (needed to selectively restore the session).Include a thorough description of the security assumptions, capabilities and any potential risks (possible attack points) being introduced by your project.Shipped default preferences should prevent this from accidentally happening. Wrongly configured prefs will break the SessionStore service as a whole.Is system or subsystem security compromised in any way if your project's configuration files / prefs are corrupt or missing?.What security issues do you address in your project?.Tracking bug 448976 - turn the Session Restore prompt into an error page.About:sessionrestore is the new in-browser page displayed for repeated crashes from which users can choose to (selectively) restore the crashed session.
0 kommentar(er)
