Mirrors/uBlock
1
0
Fork 0
mirror of https://github.com/gorhill/uBlock.git synced 2024-11-07 03:12:33 +01:00
Code Issues Releases Wiki Activity
ba0b11aabe
uBlock/src/popup.html

67 lines
2.0 KiB
HTML
Raw Normal View History

first commit
2014-06-24 00:42:43 +02:00
<!DOCTYPE html>
<html>
<head>
Avoid using Chrome's @@bidi_* type i18n messages ... for the sake of portability. When including vapi-common.js in an HTML file, then the body element there will have a "dir" attribute filled with the current locale's direction (ltr or rtl). The following languages are considered right-to-left: ar, he, fa, ps, ur. Everything else is left-to-right. After the "dir" attribute is set, we can decide in CSS which elements should have different styling for rtl languages (e.g., body[dir=rtl] #id).
2014-10-21 16:45:54 +02:00
<meta charset="utf-8">
first commit
2014-06-24 00:42:43 +02:00
<link rel="stylesheet" href="css/common.css" type="text/css">
mind right-to-left language
2014-08-03 06:08:27 +02:00
<link rel="stylesheet" href="css/popup.css" type="text/css">
first commit
2014-06-24 00:42:43 +02:00
<title>µBlock</title>
</head>
<body>
Use a dedicated file for storing extension info Chrome has getManifest(), Safari doesn't have anything, Firefox has an asynchronous API... So, instead of using extension APIs, store the common informations (extension name, version, homepage url) in a file (vapi-appinfo.js), which can be included when it's needed (its data will be available at vAPI.app.____). The file's content is updated each time the extension is being built, so it shouldn't be modified manually.
2014-10-20 22:10:59 +02:00
<h4 title="popupTipDashboard">v<span id="version"></span></h4>
first commit
2014-06-24 00:42:43 +02:00
<div>
this fixes #172
2014-08-24 16:04:22 +02:00
<p id="switch" data-i18n-tip="popupPowerSwitchInfo"><span class="fa">&#xf011;</span></p>
<p id="switch-hint"></p>
lnaguage stuff
2014-06-24 02:03:41 +02:00
<p style="font-size: 16px;" data-i18n="popupBlockedRequestPrompt"></p>
this fixes #172
2014-08-24 16:04:22 +02:00
<p id="stats">
<span data-i18n="popupBlockedOnThisPagePrompt"></span>&ensp;
strike that: I can't hold development for bleeding edge unstable version of chromium
2014-09-27 19:27:33 +02:00
<span id="gotoPick" class="fa tool" data-i18n-tip="popupTipPicker" data-tip-anchor="top">&#xf1fb;</span>&ensp;
this fixes #172
2014-08-24 16:04:22 +02:00
<span id="gotoLog" class="fa tool" data-i18n-tip="popupTipLog" data-tip-anchor="top">&#xf06e;</span>
</p>
first commit
2014-06-24 00:42:43 +02:00
<p id="page-blocked">?</p>
lnaguage stuff
2014-06-24 02:03:41 +02:00
<p id="stats" data-i18n="popupBlockedSinceInstallPrompt"></p>
first commit
2014-06-24 00:42:43 +02:00
<p id="total-blocked">?</p>
</div>
code review + fine tuning UI
2014-10-07 16:46:10 +02:00
<div id="dynamicFilteringToggler" class="fa on">
more fine-tuning before release
2014-10-07 21:09:43 +02:00
<div></div>
<div></div>
<div></div>
<div></div>
code review + fine tuning UI
2014-10-07 16:46:10 +02:00
<a href="https://github.com/gorhill/uBlock/wiki/Dynamic-filtering" target="_blank">?</a>
</div>
dynamic filtering
2014-10-06 20:02:44 +02:00
<div id="dynamicFilteringContainer">
<div class="dynamicFiltering local" data-scope=".">
<div data-first-party data-type="inline-script"></div>
<div data-first-party data-type="script"></div>
<div data-type="script"></div>
<div data-first-party data-type="sub_frame"></div>
<div data-type="sub_frame"></div>
<div class="label">&lt;script&gt;</div>
<div class="label">&lt;iframe&gt;</div>
</div>
<div class="dynamicFiltering global" data-scope="/">
<div data-first-party data-type="inline-script"></div>
<div data-first-party data-type="script"></div>
<div data-type="script"></div>
<div data-first-party data-type="sub_frame"></div>
<div data-type="sub_frame"></div>
<div class="label">&lt;script&gt;</div>
<div class="label">&lt;iframe&gt;</div>
</div>
</div>
Work on vendor API abstraction, and near complete Safari support
2014-10-17 21:44:19 +02:00
<script src="js/js-loader.js" data-jsList="
js/vapi-common.js
js/vapi-client.js
Use a dedicated file for storing extension info Chrome has getManifest(), Safari doesn't have anything, Firefox has an asynchronous API... So, instead of using extension APIs, store the common informations (extension name, version, homepage url) in a file (vapi-appinfo.js), which can be included when it's needed (its data will be available at vAPI.app.____). The file's content is updated each time the extension is being built, so it shouldn't be modified manually.
2014-10-20 22:10:59 +02:00
js/vapi-appinfo.js
Work on vendor API abstraction, and near complete Safari support
2014-10-17 21:44:19 +02:00
js/udom.js
js/i18n.js
js/popup.js
"></script>
first commit
2014-06-24 00:42:43 +02:00
</body>
</html>
Reference in New Issue Copy Permalink