8 Commits (6cbde7894ab9633aff43e816a84d3188c4f079b2)

Author	SHA1	Message	Date
lilia	5762e59c41	DRY up registration event callbacks ... This was just a special case of the extension.on/trigger interface.	11 years ago
lilia	470346c9c4	Save incoming messages and pass to frontend asynchronously ... After a message is saved asynchronsly, fire an event and pass the message attributes to frontend listeners via the chrome-runtime API. This behavior is similar to the 'storage' event fired by localStorage.	11 years ago
lilia	5a0e199fc5	Namespace registration helpers	11 years ago
Sumit Bindal	d537d6a91f	Fixing lint errors ... Fixing JSLint Problems	11 years ago
lilia	13446e9c17	"Fix dirty hack" (runtime.reload) in chromium.js ... Runtime reload is overkill and causes a jarring ux. Instead, send and receive messages across the runtime. Also, if we need to jump between the main ui and options pages, simply navigate within the current tab rather than spawning a new one.	11 years ago
Marco	69ba6581b0	moved some chromium-specific code into chromium.js (using extension.navigator namespace)	11 years ago
Matt Corallo	aec36468bc	Request new keys (largely untested)	11 years ago
Matt Corallo	d9bf0a41fb	textsecure.storage, chromium.js	11 years ago