Page MenuHomePhabricator

Quicksand - make things work properly with high security mode
ClosedPublic

Authored by btrahan on Apr 23 2015, 11:33 PM.
Tags
None
Referenced Files
F14048567: D12536.id30099.diff
Thu, Nov 14, 8:25 AM
F13982560: D12536.id30101.diff
Sun, Oct 20, 12:13 AM
F13981517: D12536.id.diff
Oct 19 2024, 5:06 PM
F13980733: D12536.diff
Oct 19 2024, 12:23 PM
F13971407: D12536.id30099.diff
Oct 17 2024, 1:12 PM
F13967457: D12536.id30100.diff
Oct 16 2024, 1:44 PM
F13961479: D12536.id.diff
Oct 15 2024, 5:15 AM
Unknown Object (File)
Oct 13 2024, 10:16 AM
Subscribers

Details

Summary

Fixes T7064. We need to pass the quicksand magic request variable around and then instrument the javascript to handle quicksand page loads.

Test Plan

Enabled two factor auth on my account and then

  • visited password page
  • filled out 2 factor auth request
  • saw high security bubble
  • clicked about still seeing high security bubble
  • refreshed page and still saw security bubble
  • dismissed bubble by following through workflow after clicking bubble

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

btrahan retitled this revision from to Quicksand - make things work properly with high security mode.
btrahan updated this object.
btrahan edited the test plan for this revision. (Show Details)
btrahan added a reviewer: epriestley.
epriestley edited edge metadata.
epriestley added inline comments.
webroot/rsrc/js/core/behavior-high-security-warning.js
39

Maybe this should return if it isn't a fresh response, like how notifications work?

This revision is now accepted and ready to land.Apr 23 2015, 11:35 PM
btrahan edited edge metadata.

Dont update hi sec if the response isn't from the server. Handles the case where hi sec -> not hi sec -> user hits back to the hi sec stuff.

This revision was automatically updated to reflect the committed changes.