Firefox Regex

[Elnora Heidrick]

Besttext search on page/in tabs -count/regex/match distribution/list/find-as-you-type.Fastest Instant web/history search in URLBar.Best custom search and multi-tab preview in anybox or for selected text. Autocopy, dnd link/image.

Since the other alternatives offered here have been left in the dust of technological change, and rendered incompatible with latest versions, I'll drop the two current compatible addons I found (though I haven't tested them):

A new stable Firefox version rolls out today, providing new features for web developers. A new regex engine, updates to the ECMAScript Intl API, new CSS selectors, enhanced support for WebAssembly, and many improvements to the Firefox Developer Tools await you.

Uncaught promise errors are critical in modern asynchronous JavaScript, and even more so in frameworks like Angular. In Firefox 78, you can expect to see all details for thrown errors show up properly, including their name and stack:

The implementation of this functionality was only possible through the close collaboration between the SpiderMonkey engineering team and a contributor, Tom Schuster. We are investigating how to improve error logging further, so please let us know if you have suggestions.

Failed or blocked network requests come in many varieties. Resources may be blocked by tracking protection, add-ons, CSP/CORS security configurations, or flaky connectivity, for example. A resilient web tries to gracefully recover from as many of these cases as possible automatically, and an improved Network monitor can help you with debugging them.

Version 78 sees Firefox add support for the :is() and :where() pseudo-classes, which allow you to present a list of selectors to the browser. The browser will then apply the rule to any element that matches one of those selectors. This can be useful for reducing repetition when writing a selector that matches a large number of different elements. For example:

In this version, Firefox has enabled support for the non-prefixed versions of :read-only and :read-write. As their name suggests, they style elements based on whether their content is editable or not:

You should be aware that these pseudo-classes are not limited to form elements. You can use them to style any element based on whether it is editable or not, for example a element with or without contenteditable set:

Thanks to the RegExp engine in SpiderMonkey, Firefox now supports all new regular expression features introduced in ECMAScript 2018, including lookbehinds (positive and negative), the dotAll flag, Unicode property escapes, and named capture groups.

Lookbehind and negative lookbehind assertions make it possible to find patterns that are (or are not) preceded by another pattern. In this example, a negative lookbehind is used to match a number only if it is not preceded by a minus sign. A positive lookbehind would match values not preceded by a minus sign.

Rules for formatting lists vary from language to language. Implementing your own proper list formatting is neither straightforward nor fast. Thanks to the new Intl.ListFormat API, the JavaScript engine can now format lists for you:

Enhanced language-sensitive number formatting as defined in the Unified NumberFormat proposal is now fully implemented in Firefox. See the NumberFormat constructor documentation for the new options available.

Firefox now supports ParentNode.replaceChildren(), which replaces the existing children of a Node with a specified new set of children. This is typically represented as a NodeList, such as that returned by Document.querySelectorAll().

This method provides an elegant way to empty a node of children, if you call replaceChildren() with no arguments. It also is a nice way to shift nodes from one element to another. For example, in this case, we use two buttons to transfer selected options from one box to another:

Multi-value is a proposed extension to core WebAssembly that enables functions to return many values, and enables instruction sequences to consume and produce multiple stack values. The article Multi-Value All The Wasm! explains what this means in greater detail.

In addition to that, we provide a new Extended Support Release (ESR) for enterprise users once a year. Firefox 78 ESR includes all of the enhancements since the last ESR (Firefox 68), along with many new features to make your enterprise deployment easier.

A noteworthy feature: In previous ESR versions, Service workers (and the Push API) were disabled. Firefox 78 is the first ESR release to support them. If your enterprise web application uses AppCache to provide offline support, you should migrate to these new APIs as soon as possible as AppCache will not be available in the next major ESR in 2021.

Firefox 78 is the last supported Firefox version for macOS users of OS X 10.9 Mavericks, OS X 10.10 Yosemite and OS X 10.11 El Capitan. These users will be moved to the Firefox ESR channel by an application update. For more details, see the Mozilla support page.

Technical details aside, this means that executeScript_Sandbox works fine in Firefox except that it can not process any regular expression. If you have regular expression in your Javascript, you will get the error E501.

Thank you for the suggestion. Looks like executeScript is the only immediate solution as I have well beyond a thousand regex expressions throughout my macros. While rewriting the scripts would certainly be good practice for my JS skills , hopefully there will eventually be a JS interpreter that handles regex (and ES6+) in a way that is V3-compliant for all browsers. Thanks again for the help.

Let's try to do it as Sebastian pictured it: we should do a regex search if the filter text is of the following form /xyz/flags (we should make sure flags are valid, so we don't confuse this with a path search, e.g. /src/test)

Good point about paths searches. It needs to be ensured that searching by path is still possible. And there might be cases where the entered string is a valid regular expression but is meant to be a path search, a simple example is /path/.

So the question is what to do in this case. Either do both, a normal text search and a regex search or somehow introduce an option to toggle regex search. Toggling might be implemented as a prefix regex: similar to the filters within the Network Monitor.

In this case, both the strings matching the regex and the value "/path/" will be displayed. Suppose my file path looks like foo.bar/bug/123. If a user enters as /bug/ in the input then it will match this URL and show this message. As bug also seems to be a valid regular expression. I hope this is what Sebastian meant.

That isn't the case for all patterns though. For example, suppose the user searches for "/?path=/" hoping to search for the string "/?path=/", but since "?path=" isn't a a valid regex it doesn't work as expected.

The /path/ example was bad, because it matches in both cases, via a string and a regex search. Thayne gave a better example. So, /?path=/ should still match paths containing the string, even when the regex search fails in this case.

I can't seem to find a regex search that provides results any different than a regular search. And all searches seem to be case insensitive. I need to be able to enter a regex string and get visibly different results than a standard search value. Can someone help me on this?

You can also use a valid regular expression to filter the console output. For example, the following show video shows the results when filtering on two simple regular expressions: /(coolrad)/ and /(cool)/.

You can flip the javascript.options.relimit preference in Firefox to make it test for exponential regexps (switched on by default in Firefox 4). This might not be quite as comfortable as RegEx Buddy but if you test your regexp in error console on bad input and it throws you know that something is wrong.

So ps -ef grep firefox searches for lines with firefox in it. Since the grep process itself has "firefox" in it, grep finds that as well. By adding a [], we are only searching for the character class "[f]" (which consists of only the letter "f" and is therefor equivalent to just an "f" without the brackets). The advantage of the brackets now is that the string "firefox" no longer appears in the grep command. Hence, grep itself won't show up in the grep result.

First of all, notice that ps's unfiltered output will contain a line corresponding to the grep process launched by your shell. If you're running grep firefox at the moment you run ps, you'll see it in the output:

without any single-quotes, it caused grep to look for lines matching the regex [f]irefox precisely because there was no file matching the glob [f]irefox in your current working directory! This doesn't relate to your actual observations, but it's interesting to note that you could have observed the following behavior:

In the second case here, because the current directory has an entry named firefox, the unquoted argument [f]irefox is expanded by Bash before grep gets to see it, and you end up grepping for the regex firefox instead of [f]irefox. The solution would be to add single-quotes:

I use a map display of the office in Checkmk NagVis, with mainly client machines to get a general overview of their status. I used a similar map outside of NagVis, which shows placement of users, network outlets in the wall, etc. Thought it be nice if they could be combined, but turn on/off information layers when needed. Like how mapping services like OSM, Google offers too.

3a8082e126