Zo byšće tute přidatki wužiwał, dyrbiće Firefox sćahnyć.

Přizjewić
Přidatkowy symbol

Pohódnoćenja za Regex Search & Replace

Regex Search & Replace wot code-for-charity

2,8 z 5 hwěžkow
5
0
4
4
3
2
2
0
1
3
9 pohódnoćenjow
  • wot Orlando, 2ヶ月前
  • wot Wužiwar Firefox 19714388, 5ヶ月前
    Non-performant regex implementation is worse then no -regex implementation. Do not install.
  • wot grayich, 8ヶ月前
    In Firefox 144, the extension works glitchy: when typing text, the last letter becomes invisible
  • wot Attacktive, 2年前
    I'd like it to focus on the regex input automatically. 🙂
  • wot Cyberknight, 2年前
    It only works in simple Pages, that is, without frames or iframes or any other complex structure.
  • wot Wužiwar Firefox 17995068, 2年前
    Would be nice to have the Manifest V3 "Only When Clicked" permission option
  • wot Wužiwar Firefox 18349586, 2年前
    Not search in popup (play.google.com reviews)
  • wot ravenwolfzero, 2年前
    Same annoying experience as the other review that the input is always a keystroke behind what you've actually typed. The best workaround for that seems to be just hitting the left or right arrow key.

    Additionally, it causes Firefox to lock up when searching very large pages (which is unfortunately exactly what I need it for).
  • wot ratSprite, 3年前
    First thing I did was try searching for "http://", to test how the extension handles escaping characters.
    We did not get that far. Final character of the search isn't processed until focus changes or you add an extra character and then backspace.
    Search and replace seems to need a "Do it!" button because it just sits there.

    Wotmołwa wuwiwarja

    je so 3年前 napisał
    thanks, you might be curious to review the situation: https://github.com/code-charity/ultimate-REGEX-extension/issues/4 (- if you like the design/vision you can give it 5 stars already rather than being its negative fate for long to come. )
    this bug seems a bit familiar from testing an old version, however i didnt write the code and this version works great in Chrome. - Documenting it: https://github.com/code-charity/ultimate-REGEX-extension/issues/5
    - probably you could even fix it quickly & feel great about that.