Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code

Side by Side Diff: README.md

Issue 29367151: Issue 4721 - Use IndexedDB for storage in Edge (Closed)
Patch Set: Created Dec. 9, 2016, 6:38 a.m.
Left:
Right:
Use n/p to move between diff chunks; N/P to move between comments.
Jump to:
View unified diff | Download patch
« no previous file with comments | « no previous file | edge/ext/background.js » ('j') | edge/ext/background.js » ('J')
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 Adblock Plus for Chrome, Opera and Safari 1 Adblock Plus for Chrome, Opera and Safari
2 ========================================= 2 =========================================
3 3
4 This repository contains the platform-specific Adblock Plus source code for 4 This repository contains the platform-specific Adblock Plus source code for
5 Chrome, Opera and Safari. It can be used to build Adblock Plus for these 5 Chrome, Opera and Safari. It can be used to build Adblock Plus for these
6 platforms, generic Adblock Plus code will be extracted from other repositories 6 platforms, generic Adblock Plus code will be extracted from other repositories
7 automatically (see _dependencies_ file). 7 automatically (see _dependencies_ file).
8 8
9 Building 9 Building
10 --------- 10 ---------
(...skipping 26 matching lines...) Expand all
37 all the certificates it was signed with (Apple's root certificate and 37 all the certificates it was signed with (Apple's root certificate and
38 intermediate certificates) in PEM format - in that order. 38 intermediate certificates) in PEM format - in that order.
39 39
40 ### Development environment 40 ### Development environment
41 41
42 To simplify the process of testing your changes you can create an unpacked 42 To simplify the process of testing your changes you can create an unpacked
43 development environment. For that run one of the following commands: 43 development environment. For that run one of the following commands:
44 44
45 ./build.py -t chrome devenv 45 ./build.py -t chrome devenv
46 ./build.py -t safari devenv 46 ./build.py -t safari devenv
47 ./build.py -t edge devenv
47 48
48 This will create a _devenv.platform_ directory in the repository. In Chrome you 49 This will create a _devenv.platform_ directory in the repository. In Chrome you
49 should load _devenv.chrome_ as an unpacked extension directory. After making 50 should load _devenv.chrome_ as an unpacked extension directory. After making
50 changes to the source code re-run the command to update the development 51 changes to the source code re-run the command to update the development
51 environment, the extension should reload automatically after a few seconds. 52 environment, the extension should reload automatically after a few seconds.
52 53
53 For Edge you can use the same development environment as Chrome. You should load 54 For Edge you should load _devenv.edge_ as an unpacked extension directory. After
kzar 2016/12/12 14:17:50 Seems like these REAMDE changes clash with the oth
Oleksandr 2016/12/13 06:21:18 Done.
54 _devenv.chrome_ as an unpacked extension directory. After rebuilding the 55 rebuilding the extension you should usually force reloading it in Edge.
55 extension you should usually force reloading it in Edge.
56 56
57 In Safari you should load _devenv.safari/adblockplussafari.safariextension_ as 57 In Safari you should load _devenv.safari/adblockplussafari.safariextension_ as
58 unpacked extension directory. After making changes to the source code re-run the 58 unpacked extension directory. After making changes to the source code re-run the
59 command to update the development environment. You will still need to reload the 59 command to update the development environment. You will still need to reload the
60 extension explicitly in the Extension Builder, Safari currently doesn't allow 60 extension explicitly in the Extension Builder, Safari currently doesn't allow
61 automating this action. 61 automating this action.
62 62
63 Running the unit tests 63 Running the unit tests
64 ---------------------- 64 ----------------------
65 65
66 To verify your changes you can use the unit test suite located in the _qunit_ 66 To verify your changes you can use the unit test suite located in the _qunit_
67 directory of the repository. In order to run the unit tests go to the 67 directory of the repository. In order to run the unit tests go to the
68 extension's Options page, open the JavaScript Console and type in: 68 extension's Options page, open the JavaScript Console and type in:
69 69
70 location.href = "qunit/index.html"; 70 location.href = "qunit/index.html";
71 71
72 The unit tests will run automatically once the page loads. 72 The unit tests will run automatically once the page loads.
OLDNEW
« no previous file with comments | « no previous file | edge/ext/background.js » ('j') | edge/ext/background.js » ('J')

Powered by Google App Engine
This is Rietveld