diff options
author | Pale Moon <git-repo@palemoon.org> | 2016-09-01 13:39:08 +0200 |
---|---|---|
committer | Pale Moon <git-repo@palemoon.org> | 2016-09-01 13:39:08 +0200 |
commit | 3d8ce1a11a7347cc94a937719c4bc8df46fb8d14 (patch) | |
tree | 8c26ca375a6312751c00a27e1653fb6f189f0463 /toolkit/locales/en-US/chrome/global/devtools/csscoverage.properties | |
parent | e449bdb1ec3a82f204bffdd9c3c54069d086eee3 (diff) | |
download | palemoon-gre-3d8ce1a11a7347cc94a937719c4bc8df46fb8d14.tar.gz |
Base import of Tycho code (warning: huge commit)
Diffstat (limited to 'toolkit/locales/en-US/chrome/global/devtools/csscoverage.properties')
-rw-r--r-- | toolkit/locales/en-US/chrome/global/devtools/csscoverage.properties | 32 |
1 files changed, 32 insertions, 0 deletions
diff --git a/toolkit/locales/en-US/chrome/global/devtools/csscoverage.properties b/toolkit/locales/en-US/chrome/global/devtools/csscoverage.properties new file mode 100644 index 000000000..c1df46a09 --- /dev/null +++ b/toolkit/locales/en-US/chrome/global/devtools/csscoverage.properties @@ -0,0 +1,32 @@ +# This Source Code Form is subject to the terms of the Mozilla Public +# License, v. 2.0. If a copy of the MPL was not distributed with this +# file, You can obtain one at http://mozilla.org/MPL/2.0/. + +# LOCALIZATION NOTE These strings are used in the 'csscoverage' command and in +# the user interface that this command creates. + +# LOCALIZATION NOTE (csscoverageDesc, csscoverageStartDesc2, +# csscoverageStopDesc2, csscoverageOneShotDesc2, csscoverageToggleDesc2, +# csscoverageReportDesc2): Short descriptions of the csscoverage commands +csscoverageDesc=Control CSS coverage analysis +csscoverageStartDesc2=Begin collecting CSS coverage data +csscoverageStopDesc2=Stop collecting CSS coverage data +csscoverageOneShotDesc2=Collect instantaneous CSS coverage data +csscoverageToggleDesc2=Toggle collecting CSS coverage data +csscoverageReportDesc2=Show CSS coverage report +csscoverageStartNoReloadDesc=Don't start with a page reload +csscoverageStartNoReloadManual=It's best if we start by reloading the current page because that starts the test at a known point, but there could be reasons why we don't want to do that (e.g. the page contains state that will be lost across a reload) + +# LOCALIZATION NOTE (csscoverageRunningReply, csscoverageDoneReply): Text that +# describes the current state of the css coverage system +csscoverageRunningReply=Running CSS coverage analysis +csscoverageDoneReply=CSS Coverage analysis completed + +# LOCALIZATION NOTE (csscoverageRunningError, csscoverageNotRunningError, +# csscoverageNotRunError): Error message that describe things that can go wrong +# with the css coverage system +csscoverageRunningError=CSS coverage analysis already running +csscoverageNotRunningError=CSS coverage analysis not running +csscoverageNotRunError=CSS coverage analysis has not been run +csscoverageNoRemoteError=Target does not support CSS Coverage +csscoverageOneShotReportError=CSS coverage report is not available for 'oneshot' data. Please use start/stop. |