privly / privly-jetpack Goto Github PK

Currently only the extension unit tests run on Travis when pushing. This will require adding a web server initialization to the script, as in chrome.

The Senkeys/BililiteRange library is a bit too big to be run every time on a page load. The inclusion of this library(if used) should be optimized. This will be looked at when we have the extension ready with all the necessary features and then we can profile across the whole extension and prioritize what we need to optimize.

@summerwish emailed me about porting the Seamless Posting work to JetPack. Since @hitesh96db has also wanted to port the functionality, I figured I would open this issue to help organize.

Given the time remaining in the GSoC program, this functionality will not be considered part of the official GSoC program. A higher priority is to finalize the existing functionality with documentation and tests.

The day of reckoning has arrived and Mozilla has (finally) deprecated Xul. It looks like we are in good shape with the JetPack extension since we make minimal use of the XPCom and require("chrome"). Still, we need to refactor all these references so the JetPack extension will not get swept up in the Firefox extension apocalypse.

After more than a month in the review queue, AMO reviewed the extension and want these two changes in a subsequent version:

1. Please remove testing files (message_test, the tests subdir, etc) from the next version.

2. Please use a non-remote url here: span.style.background = "url(https://raw.githubusercontent.com/privly/privly-jetpack/master/data/skin/logo_16.png) no-repeat";

The extension is now live on the Mozilla web store.