Skip to content
Snippets Groups Projects
  1. Jul 25, 2012
  2. Jul 13, 2012
  3. Jul 09, 2012
    • Shane Tomlinson's avatar
      Yak shave to clean up the error-display. · e0e0e5e0
      Shane Tomlinson authored
      Generalize error-display to extended-info.  For every "screen" that is shown, create an extendedInfo and instantiate it.  Remove the "error-display.show" code that was in page_helpers and page_module.
      
      issue #1916
      e0e0e5e0
  4. Jul 06, 2012
  5. Jun 28, 2012
  6. Jun 27, 2012
  7. Jun 18, 2012
  8. Jun 14, 2012
  9. Jun 13, 2012
  10. Jun 11, 2012
  11. Jun 06, 2012
  12. May 30, 2012
  13. May 24, 2012
  14. May 18, 2012
    • Shane Tomlinson's avatar
      Yak shave for interaction_data. Ensure timestamp, lang, etc are always sent in interaction data. · eb545b49
      Shane Tomlinson authored
      * Removed the .interactionData namespace from storage.js, created our first model - shared/models/interaction_data.js
      * Simplified how data is stored into interaction_data, created current and staged sub-namespaces
      * Added stageCurrent and publishStaged functions.
      * in shared/modules/interaction_data.js, simplified calls to model.
      * Tried to make the xhr mock make more sense and provide facilities usable for peeking at last XHR request data.
      
      issue #1597
      eb545b49
  15. May 05, 2012
  16. May 04, 2012
  17. May 02, 2012
    • Shane Tomlinson's avatar
      Putting the set password back into add_email_address and verify_email_address · 7df7b9c9
      Shane Tomlinson authored
      * user.js: Update verifyEmail and verifyUser to take a password.
      * network.js: Update completeEmailRegistration and completeUserRegistration to take a password.
      * Replace verify_email_address.js and add_email_address.js with a single verify_secondary_address.js to reduce duplication.
      * Update the templates.
      * Bring back verify_email_address and add_email_address templates, but remove the verify password field.
      * To dom-jquery, add show, hide functions.
      7df7b9c9
  18. May 03, 2012
  19. May 02, 2012
  20. Apr 27, 2012
    • Shane Tomlinson's avatar
      Change the order of assertion generation to be after the user is asked "is this your computer?" · be035ba2
      Shane Tomlinson authored
      * This fixes a problem where it is possible that a user takes more than 2 minutes to answer, making the already generated assertion invalid.
      * A lot of general cleanup of the state machine.
      * Push all post email selection flows to a new state, "email_valid_and_ready" which decides whether to ask the user the computer ownership status.
      * Assertions are generated after the "is this your computer" is asked.
      * doEmailChosen is replaced with doGenerateAssertion - there were multiple calls to generate an assertion, not very DRY.
      * Fix a problem in network.js where a user who completes user registration should be marked as authenticated.
      * rename email_chosen.js to generate_assertion.js to clarify its purpose.
      
      issue #1460
      be035ba2
  21. Apr 12, 2012
    • Shane Tomlinson's avatar
      A bunch of changes to make the design more responsive to all screen sizes -... · ea5ce6ca
      Shane Tomlinson authored
      A bunch of changes to make the design more responsive to all screen sizes - mobile, desktop and tablet.
      
      * Start with a slight refactor of the CSS and DOM.
      * Vertical center content when content is smaller than the screen size.
      * Constrain email addresses and show ellipsis if emails overflow box width.  Make sure width is updated when browser window size changes or user changes the screen direction of their device.
      * If form/email address list is taller than available form area, show scroll bar on desktop or expand contents so that entire app must be scrolled on mobile.
      * If dialog opened on a tablet or large desktop window, add a gradient to the left size of the white area that matches the gradient on the arrow.
      * On mobile, footer should always be at the very bottom of the screen unless contents overflow screen height, where it will be pushed off the bottom of the screen.
      
      Things to test and be aware of:
      * Dialog should respond to various screen sizes when resizing browser window on desktop.
      * IE8 does not support media queries so narrowing the browser window will not force the dialog into "mobile" mode.
      * Contents in the "form area", wait, delay, or error screens should always be vertically centered.
      * IE6/IE7 should still see the unsupported dialog with the correct layout (untested on checkin due to #1390)
      * Wide emails should always be constrained to the screen width on mobile or box width on desktop.  The layout should respond to changes in device orientation.
      * The box surrounding the emails should show a scroll bar on desktop/tablet if there are more emails the available screen height.  On mobile, the entire screen height should expand so that the entire app must be scrolled.
      * On mobile, the footer should always be at the very bottom of the screen unless the form area takes up more vertical space than the device height.
      
      issue #1101
      issue #1317
      ea5ce6ca
  22. Mar 29, 2012
  23. Mar 28, 2012
  24. Mar 14, 2012
  25. Mar 02, 2012
  26. Mar 01, 2012
  27. Feb 29, 2012
  28. Feb 15, 2012
Loading