BETA

Transvision

Displaying 11 results for the string expression in tl:

Entity tl en-US
Entity # all locales devtools • client • debugger.properties
expressions.errorMsg
tl
Di-wastong expression
en-US
Invalid expression
Entity # all locales devtools • client • debugger.properties
expressions.label
tl
Magdagdag ng watch expression
en-US
Add watch expression
Entity # all locales devtools • client • debugger.properties
expressions.placeholder
tl
Magdagdag ng watch expression
en-US
Add watch expression
Entity # all locales devtools • client • debugger.properties
expressions.remove.tooltip
tl
Tanggalin ang watch expression
en-US
Remove watch expression
Entity # all locales devtools • client • debugger.properties
watchExpressions.header
tl
Panoorin ang mga expression
en-US
Watch expressions
Entity # all locales devtools • client • webconsole.properties
webconsole.editor.toolbar.executeButton.tooltip
tl
Patakbuhin ang expression (%S). Hindi nito buburahin ang input.
en-US
Run expression (%S). This won’t clear the input.
Entity # all locales devtools • client • webconsole.properties
webconsole.editor.toolbar.history.nextExpressionButton.tooltip
tl
Susunod na Expression
en-US
Next Expression
Entity # all locales devtools • client • webconsole.properties
webconsole.editor.toolbar.history.prevExpressionButton.tooltip
tl
Nakaraang Expression
en-US
Previous Expression
Entity # all locales dom • chrome • xslt • xslt.properties
2
tl
Nabigo ang pag-parse ng XPath expression.
en-US
Parsing an XPath expression failed.
Entity # all locales dom • chrome • xslt • xslt.properties
20
tl
XPath parse failure: unexpected end of expression:
en-US
XPath parse failure: unexpected end of expression:
Entity # all locales dom • chrome • xslt • xslt.properties
8
tl
An XPath expression was expected to return a NodeSet.
en-US
An XPath expression was expected to return a NodeSet.

Displaying 22 results for the string expression in en-US:

Entity tl en-US
Entity # all locales devtools • client • debugger.properties
expressions.errorMsg
tl
Di-wastong expression
en-US
Invalid expression
Entity # all locales devtools • client • debugger.properties
expressions.label
tl
Magdagdag ng watch expression
en-US
Add watch expression
Entity # all locales devtools • client • debugger.properties
expressions.placeholder
tl
Magdagdag ng watch expression
en-US
Add watch expression
Entity # all locales devtools • client • debugger.properties
expressions.remove.tooltip
tl
Tanggalin ang watch expression
en-US
Remove watch expression
Entity # all locales devtools • client • webconsole.properties
webconsole.editor.toolbar.executeButton.tooltip
tl
Patakbuhin ang expression (%S). Hindi nito buburahin ang input.
en-US
Run expression (%S). This won’t clear the input.
Entity # all locales devtools • client • webconsole.properties
webconsole.editor.toolbar.history.nextExpressionButton.tooltip
tl
Susunod na Expression
en-US
Next Expression
Entity # all locales devtools • client • webconsole.properties
webconsole.editor.toolbar.history.prevExpressionButton.tooltip
tl
Nakaraang Expression
en-US
Previous Expression
Entity # all locales devtools • client • webconsole.properties
webconsole.editor.toolbar.prettyPrintButton.tooltip
tl
Warning: Source string is missing
en-US
Pretty print expression
Entity # all locales dom • chrome • xslt • xslt.properties
2
tl
Nabigo ang pag-parse ng XPath expression.
en-US
Parsing an XPath expression failed.
Entity # all locales dom • chrome • xslt • xslt.properties
20
tl
XPath parse failure: unexpected end of expression:
en-US
XPath parse failure: unexpected end of expression:
Entity # all locales dom • chrome • xslt • xslt.properties
28
tl
Pag-evaluate ng di-wastong pagpapahayag.
en-US
Evaluating an invalid expression.
Entity # all locales dom • chrome • xslt • xslt.properties
8
tl
An XPath expression was expected to return a NodeSet.
en-US
An XPath expression was expected to return a NodeSet.
Entity # all locales extensions • irc • chrome • chatzilla.properties
cmd.dcc-accept.help
tl
Warning: Source string is missing
en-US
Accepts an incoming DCC Chat or Send offer. If a |nickname| is not specified, the last offer that arrived will be accepted (for security reasons, this will not work in the first 10 seconds after an offer is received). You can also use a regular expression for either <nickname> or <file>.
Entity # all locales extensions • irc • chrome • chatzilla.properties
cmd.dcc-close.help
tl
Warning: Source string is missing
en-US
Closes an existing DCC connection. |nickname| may be omitted if run from a DCC view, in which case the DCC connection for that view will be closed. |type| and |file| may be needed to identify the connection. You can also use a regular expression for either <nickname> or <file>.
Entity # all locales extensions • irc • chrome • chatzilla.properties
cmd.dcc-decline.help
tl
Warning: Source string is missing
en-US
Declines an incoming DCC Chat or Send offer. If a |nickname| is not specified, the last offer that arrived will be declined. You can also use a regular expression for <nickname>.
Entity # all locales extensions • irc • chrome • chatzilla.properties
cmd.eval.help
tl
Warning: Source string is missing
en-US
Evaluates <expression> as JavaScript code. Not for the faint of heart.
Entity # all locales extensions • irc • chrome • chatzilla.properties
cmd.eval.params
tl
Warning: Source string is missing
en-US
<expression>
Entity # all locales extensions • irc • chrome • chatzilla.properties
cmd.evalsilent.params
tl
Warning: Source string is missing
en-US
<expression>
Entity # all locales extensions • irc • chrome • chatzilla.properties
cmd.rlist.help
tl
Warning: Source string is missing
en-US
Lists channel name, user count, and topic information for the network/server you are attached to, filtered by the regular expression.
Entity # all locales extensions • irc • chrome • chatzilla.properties
msg.err.invalid.regex
tl
Warning: Source string is missing
en-US
Invalid Regular Expression. For help with regular expressions, see http://en.wikipedia.org/wiki/Regular_expression#Syntax.
Entity # all locales extensions • irc • chrome • chatzilla.properties
pref.bugKeyword.help
tl
Warning: Source string is missing
en-US
You can define multiple issue tracker keywords as a regular expression perhaps by separating them with "|" e.g. bug|issue|case|ticket
Entity # all locales toolkit • toolkit • featuregates • features.ftl
experimental-features-devtools-execution-context-selector-description
tl
Warning: Source string is missing
en-US
This feature displays a button on the console’s command line that lets you change the context in which the expression you enter will be executed. See <a data-l10n-name="bugzilla1">bug 1605154</a> and <a data-l10n-name="bugzilla2">bug 1605153</a> for more details.
Please enable JavaScript. Some features won't be available without it.