14 Commits

Author	SHA1	Message	Date
gorhill	46fb194904	fix #2084	2016-10-18 12:33:50 -04:00
gorhill	da2902524b	code review: avoid `forEach`	2016-01-15 09:21:33 -05:00
gorhill	690421aead	sync feature (#80): draft	2015-08-11 15:29:14 -04:00
gorhill	57c177c995	this fixes #1129	2015-03-31 09:25:39 -04:00
gorhill	2504f8ad35	#1013: Firefox support	2015-03-26 09:50:07 -04:00
gorhill	cad5a6cbf6	code review	2015-03-09 20:04:07 -04:00
gorhill	f362dff643	code review: do not pollute global namespace	2015-03-09 19:19:08 -04:00
gorhill	e7479dd4be	this fixes #313	2015-03-09 19:10:04 -04:00
Deathamns	95b778fbc7	Change extension description	2015-03-07 19:20:18 +01:00
gorhill	d5af32eaef	use blank string if no translation found	2015-03-03 09:37:15 -05:00
Chris	09deb9906e	request log filtering: add i18n prompt	2015-03-03 00:22:26 -07:00
Deathamns	0d9d285608	Building extension files ... Adds possibility to build extension files (Chrome and Safari) from command line. To run from the project directory: python tools/build.py [meta] If the optional `meta` argument is set, then only the manifest and language files are uptated. Without that everything is being built (extension files too) into the `dist/build/version_number` folder. For Chrome there will be two files, a crx, and a .zip file which includes the key.pem private key (so this must not be shared, it's just a bit help for publishing it to the Chrome Web Store). Beside the extension files, update-files are generated too (for self hosting - Safari needs it).	2014-11-09 18:58:46 +01:00
Deathamns	0886f7e886	Add .jshintrc, and use the "use strict" directive ... .jshintrc's otion-set is a personal choice, merely a suggestion. Beside that, it includes some common globals for specific browsers, so there's no need to set the globals in every .js file. In order to force strict coding, "use strict" directive was added into every .js file.	2014-11-09 17:39:17 +01:00
Deathamns	5b79bf3536	Work on vendor API abstraction, and near complete Safari support	2014-11-09 17:39:12 +01:00