[edit]

Introduction

A list of issues around Appalachian. See also Priority Codes.

[edit]

Issues

  • P3 Investigate multiple XPI bundling for PB and Appalachian
  • P4 Find-as-you-type for associated sites listing
  • P4 Regex for URLs instead of one per page
  • P4 Store per-tab states in per-window object so changing active tabs makes sense
  • P8 Somewhere down the line, something corrupts Appalachian into appearing to be a 4GB extension while downloading in FF's dialog window, even though it's only around 80KB
  • P8 Encryption? Or go under passwordmanager somehow?
  • P8 It seems to be learning associated sites when ever I hit the globe, independent of successful login
    • This is going to be a problem. Tracking success requires watching the user over the course of several pages, any stage of which could be an unintentional error that precedes success but is recorded as failure: it's hard to tell when to stop waiting for success.
  • P8 Direct manipulation of the default rather than a "set as default button" would be nice
    • Perhaps in addition to would work
  • P8 subject.QueryInterface(Components.interfaces.nsIHttpChannel); observer.js line 38 each time I do a google search, at least
    • Cannot duplicate
  • P9 Maybe openid.aol.com/foo is preferable to http://openid.aol.com/foo as display text and what's entered into the forms
    • I'm not yet convinced the http vs. https resolution matter is properly defined. The default resolution of a URL minus its scheme is to go to http, and if the actual ID is https, the http version should (RECOMMEND) be a redirect to the https. There is a pathological case where a user has control over https but not http, in which case they will be very confused when they start entering their scheme-less URL everywhere. Furthermore, this is an OpenID 2.0 convention and is not mentioned at all in OpenID 1.1. I won't put it in the UI but there is some code for its later adoption.
[edit]

Links

Retrieved from "http://simile.mit.edu/wiki/Appalachian_Todos"