Firefox/Projects: Difference between revisions

Jump to navigation Jump to search

Firefox/Projects (view source)

Revision as of 08:13, 21 March 2009

8,706 bytes removed ,  21 March 2009
no one saw that
(some changes, still working)
(no one saw that)
Line 1: Line 1:
= Overview =
= General Sprints =
'''Sprint lead:''' curtis <br/>
* [[Firefox3.1/Sprints/Async Annotation Protocol Handler|Asynchronous Annotation Protocol Handler]] (COMPLETED)
'''Sprinters:''' johnath, boriss


'''Description:'''
= Work Week Code Sprints =
<blockquote>More useful/helpful set of network error pages that offer tools helping users get to a useful end point via search, analysis of Places DB, or automatic redirects/reloads.</blockquote>
* [[Firefox3.1/Sprints/Bookmark Dialog Focus|Bookmark Dialog Focus]] (COMPLETED)
* [[Firefox3.1/Sprints/about me|about:me]]
* [[Firefox3.1/Sprints/Network Error Pages|Network Error Pages]]
* [[Firefox3.1/Sprints/Tab Matches in Awesomebar|Tab Matches In Awesomebar]]
* [[Firefox3.1/Sprints/Clear Recent History by Time Range|Clear Recent History by Time Range]]
* [[Firefox3.1/Sprints/Always have option to Add Search|Always have option to Add Search]]
* [[Firefox3.1/Sprints/Restore Visible Tabs First|Restore Visible Tabs First]] (COMPLETED)
* [[Firefox3.1/Sprints/Improve Plugin Find and Install|Improve Plugin Find and Install]]
* [[Firefox3.1/Sprints/Places Expiration Performance Refactoring|Places Expiration Performance Refactoring]] (COMPLETED)
* [[Firefox3.1/Sprints/Rebuild Software Update without browser element|Rebuild Software Update without browser element]]
* [[Firefox3.1/Sprints/Awesomeformcomplete|Awesomeformcomplete]]
* [[Firefox3.1/Sprints/Places DB Creation Scripts|Places DB Creation Scripts]]
* [[Firefox3.1/Sprints/Focus Ring Cleanup|Focus Ring Cleanup]]
* [[Firefox3.1/Sprints/Windows Theme Polish|Windows Theme Polish]]


= Project steps =
= Other Open sprints (pick 'em up and take 'em!) =
* '''String Freeze for Beta 4''': Mar 19, 2009
* [[Firefox3.1/Sprints/Privacy Prefpane Refresh|Privacy Prefpane Refresh]]
* '''Code Freeze for Beta 4''': April 6, 2009
* [[Firefox3.1/Sprints/Visual Affordance for Tear Off Tabs|Visual Affordance for Tear Off Tabs]]
 
* [[Firefox3.1/Sprints/Ts Wins|Ts Wins]]
*Open initial bug for 404 handling<br><br>
* [[Firefox3.1/Sprints/Update hunspell|Update dictionaries]]
*:[[Image:250px-Pictogram voting keep.svg.png|20px]] '''Completed:''' [https://bugzilla.mozilla.org/show_bug.cgi?id=482874 Bug 482874] and [https://bugzilla.mozilla.org/show_bug.cgi?id=484313 Bug 484313] (DTD changes).
* [[Firefox3.1/Sprints/Add Search to Awesomebar|Add Search to Awesomebar]]
 
*Create experimental 404 extension and send it out for comments<br><br>
*:[[Image:250px-Pictogram voting keep.svg.png|20px]] '''Completed,''' comments were:
** Works well for simulated small errors in URLs
** Hard to say how well it works for real errors in the wild.
** Drawing alternatives from the Places DB looks like a practical tool we can use for suggesting alternatives.
 
* Discuss with Google Link Doctor team<br><br>
*:[[Image:250px-Pictogram voting wait.svg.png|20px]] '''In progress,''' next: follow up on experimental access to the service.
 
* Discuss possible 404 implementation with bzbarsky and others<br><br>
*:[[Image:250px-Pictogram voting keep.svg.png|20px]] '''Completed,''' comments were:
** 404 interception unified with the existing error handling architecture is too deep a change to make for 3.1.
** A less intrusive approach similar to the one the experimental 404 extension uses may be possible -- need to investigate further.
 
* Implement Levenshtein Distance algorithm in C++<br><br>
*:[[Image:250px-Pictogram voting keep.svg.png|20px]] '''Completed'''
** Followup: Plug algorithm into Firefox+Sqlite, providing better performance and accuracy compared to the approach used in the extension.<br><br>
**:[[Image:250px-Pictogram voting wait.svg.png|20px]] '''In progress'''
 
* Proposed a plan for actual implementation<br><br>
*:[[Image:250px-Pictogram voting wait.svg.png|20px]] '''In progress,''' see below
 
= Proposed Plan =
 
'''We're targeting two error types:'''
# 404 errors.
# DnsNotFound errors.
   
'''Tools to draw on:'''
# Places alternatives: Places DB + Edit Distance -- can be called automatically.
#* Good for errors on URLs that the user has visited before
#* Might be especially useful for misspelled hostnames.
# Google Link Doctor
#* Assuming partner issues are worked out with Google.
#* Can't be called automatically for privacy reasons.
#* Available with one click (similar to pre-loaded Google search box)
# Other easy to implement tools
#* common transformations (www..example.com --> www.example.com, etc.)
#* pre-loaded search box
#* etc.
 
=404 redirection=
==Design scope==
* Will use 404-specific error page for 3.1 rather than trying to re-use the generic network error page.  The goal is to give the user better indication of the problem and provide tools for next steps if needed.
* Will not redirect obvious custom server error pages.  To this end, we'd like to use a heuristic beyond simple page size for identifying default 404 pages.  Possibilities:
*# Compare to standard Apache and IIS 404 pages, possibly fuzzy (use edit istance?)
*# Use EndDocumentLoad (or other event) + redirect
*# Implement listener in C++, should be able to access 404 status directly from dcument.
*# <s>Deep docshell changes</s> (Not possible for 3.1}
* Will allow original error page to be available at one click
* Will unify with existing error page architecture in v.next.
 
==Open questions==
* Which tools will be provided?
* Should indication that the error is "404" be provided in the first screen?
* Is it possible to link to a page with more information about the problem?
* How many alternatives should be shown, and how closely should those match user input?
* What distinction should be drawn from the user's perspective between this and a DnsNotFound error?
* Problem: The 404 error page can't be a chrome page, since that could expose us to privilege escalation attacks piggy-backed on XSS attacks.<br><br>
*:[[Image:250px-Pictogram voting keep.svg.png|20px]] '''Solution:''' Use an about: URL to access the 404 error page.
 
 
==Resources==
===Sketches===
<gallery>
Image:Linkdoctor places 404.png|A near match has been found (http://www.americas.com) along with the level above (http://news.bbc.co.uk), either via Places or Google
</gallery>
===Notes===
 
==Most current design==
 
 
=DnsNotFound=
==Design scope==
* Will use the DnsNotFound error page to give the user better indication of the problem and provide tools for next steps if needed
* Will provide the user tools via one-click access to Google Link Doctor
* Will provide the user with better link options with data drawn from Places
 
==Open questions==
* Which tools will be provided?
* Should indication that the error is "DnsNotFound" be provided in the first screen?
* Is it possible to link to a page with more information about the problem?
* How many alternatives should be shown, and how closely should those match user input?
* What distinction should be drawn from the user's perspective between this and a 404 error?
 
==Resources==
===Sketches===
<gallery>
Image:Dns error 1 suggestion.png|A suggestion is found, via Google or Places, and search is provided
Image:Dns error 2 suggestions.png|Two suggestions might be given if two are clear strong matches
</gallery>
===Notes===
 
==Most current design==
 
 
<hr>
<hr>
<hr>
 
= To Do =
 
# Get the experimental extension out to concerned parties: Boriss, Johnath, and Aza, etc.  Work with Boriss to get a first cut on an official 404 page design.
# Follow up with contact on Link Doctor team about experimental access to the Link Doctor service.
# Extend the 404 extension to intercept other error types so we can use it to prototype improved error page designs.
# Figure out how to plumb 404 interception into Firefox proper (talk to Johnath).
# Investigate implementing a proper edit-distance algorithm in C++ that can be used with Sqlite.
# Come up with a plan for a production-quality Firefox 3.5 patch.
 
= Goals / Use Cases =
tbd
 
= Non Goals =
tbd
 
= Design =
tbd
 
= Bugs =
 
[http://bugzilla.mozilla.org/show_bug.cgi?id=479922 Bug 479922] -  Network error pages should give me tools instead of asking me questions
 
= Reference =
 
[http://mxr.mozilla.org/mozilla-central/source/docshell/base/nsDocShell.cpp#3031 nsDocShell::DisplayLoadError] -- dispatches various error pages
 
[http://mxr.mozilla.org/mozilla-central/source/docshell/resources/content/netError.xhtml netError.xhtml]
 
[http://mxr.mozilla.org/mozilla-central/source/browser/components/certerror/aboutCertError.js aboutCertError.js]
 
''about:neterror''
 
''about:config'' -- urlclassifier.alternate_error_page default string = "blocked" -- for example -- tells nsDocShell::DisplayLoadError to use the "blocked" page instead of the default generic page.
 
[https://johnath.com/ https://johnath.com/] -- triggers a "Secure Connection Failed" error page.
 
[http://example.example.com/ http://example.example.com/] -- triggers an "Address Not Found" error page.
 
== Error Types ==
 
''Which ones do we want to improve first?''
 
* Some "tools" may broadly apply -- change the generic template? (e.g. search)
* No new pages, just make the existing pages better?
* Add a search field to addressNotFound page.
 
* neterror important???
* protocolNotFound
* fileNotFound
* dnsNotFound important???
* connectionFailure important???
* netInterrupt
* netTimeout important???
* nssBadCert
* nssFailure2
* phishingBlocked
* malwareBlocked
* malformedURI
* redirectLoop
* unknownSocketType
* netReset
* netOffline
* isprinting
* deniedPortAccess
* proxyResolveFailure
* proxyConnectFailure
* contentEncodingError
* unsafeContentType
 
= dnsNotFound error =
 
[http://example.cmm URL that results in a dnsNotFound error page]
 
[[Image:Picture_13.png|Firefox error page after a dnsNotFound error.]]
 
= connectionFailure error =
 
[http://127.0.0.1:81 URL that results in a connectionFailure error page]
 
[image:xxxxxxxxxxx Screenshot of a connectionFailure error page]
 
= Notes =
 
Can we use Places autocomplete for link correction?  A mis-typed link will often be in error in only the last couple of characters -- we can truncate the last 2 or 3 characters and rely on Places auto-complete to give us recommendations...
 
http://mxr.mozilla.org/mozilla-central/source/toolkit/components/places/tests/autocomplete/
 
A related alternative would be to construct an edit-distance function and register it with SqlLite.  We can then do a query on minimal edit distance (async of course) to get the best link correction matches.
 
Problem is, how do we hook link correction into the error page?  We'd like to provide suggestions inside the web page similar to Google's "did you mean" on the search results page.
 
= More Notes =
 
Google Chrome's Friendly 404 Error Page
 
[[Image:GoogleChrome404ScreenShot.png|Google Chrome's Friendly 404 Error Page]]
 
= Notes Mark III =
 
[https://wiki.mozilla.org/Firefox:1.5_Network_Error_Messages Summary of error types (FF 1.5)]
 
''Google Chrome LinkDoctor Service (linkhelp.clients.google.com)''
 
  wget -U "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.13 (KHTML, like Gecko) Chrome/0.2.149.27 Safari/525.13" "http://linkhelp.clients.google.com/tbproxy/lh/fixurl?sourceid=navclient%20&hl=en&sd=com&error=http404&url=http://news.speeple.com/sunflowers"
 
  wget -U "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.13 (KHTML, like Gecko) Chrome/0.2.149.27 Safari/525.13" "http://www.google.com"
 
= Notes: Herdict =
 
Email from Jesse:
 
  Here's the bug I filed with my ideas for error pages:
 
  https://bugzilla.mozilla.org/show_bug.cgi?id=479922
 
  and here's the page that Curtis coincidentally wrote:
 
  https://wiki.mozilla.org/Firefox3.1/Sprints/Network_Error_Pages
 
  Jonathan Zittrain was talking about HerdictWeb
  (http://www.herdict.org/web/) in building K today and had interesting
  ideas about integrating it into Firefox's error pages.  Instead of
  Firefox just telling you the site is unreachable, maybe it could tell
  you whether it has been gone for minutes or months, and whether it is
  broken for everyone or only for certain ISPs or countries.
 
  jz -- Curtis and I are in building S today if you want to come over
  and chat with us.
Jboriss
Confirmed users
954

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/135248"

Navigation menu