[tor-bugs] #16528 [Tor Browser]: Enable IndexedDB (for Twitter and other sites) (was: TorBrowser 5.0a3 acting very odd with Twitter)

[Tor Bug Tracker & Wiki]

#16528: Enable IndexedDB (for Twitter and other sites)
-------------------------+-------------------------------------------------
     Reporter:  erinn    |      Owner:  tbb-team
         Type:  defect   |     Status:  new
     Priority:  major    |  Milestone:
    Component:  Tor      |    Version:
  Browser                |   Keywords:  TorBrowserTeam201507, ff38-esr,
   Resolution:           |  tbb-5.0a, tbb-usability-website
Actual Points:           |  Parent ID:
       Points:           |
-------------------------+-------------------------------------------------

Comment (by mikeperry):

 I think it is actually fine if we enable IndexedDB. I spent some time
 looking into it, and due to
 https://bugzilla.mozilla.org/show_bug.cgi?id=595307 and
 https://developer.mozilla.org/en-
 US/docs/Web/API/IndexedDB_API/Using_IndexedDB#Security, IndexedDB is
 disabled for third parties. This means we don't have to isolate it to
 enable it.

 We will want to ensure the following:
 1. IndexedDB data is cleared on New Identity. Right now, we don't do
 anything explicit for this, but it may get cleared automatically during
 cookie clearing. We should verify that.
 2. IndexedDB data can't get written to disk if we're in private browsing
 modes.

 Unfortunately, it seems as though flipping the pref doesn't actually
 properly enable IndexedDB. This test reports tons of errors:
 http://nparashuram.com/IndexedDBShim/test. Still investigating.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16528#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online