[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4781: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3916)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4783: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3916)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4784: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3916)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4785: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3916)
Chuck Baker's Firefox Extension Forum • View topic - Misc. suggestions, questions, and issues from a new user

Misc. suggestions, questions, and issues from a new user

Discussion and bug reporting for the Text Input Recovery Extension

Misc. suggestions, questions, and issues from a new user

Postby yeltommo » Mon Nov 13, 2017 4:56 am

First of all, I was thrilled to find this extension. I lost hours' worth of writing a few days ago when the friggin' site timed out without letting me know until I clicked Submit! (Why don't such sites provide a warning?) I finally thought to search for some kind of solution to this recurrent problem. Lazarus looked great until I noticed the recent reviews. Then somehow I found a discussion on a Google Support Forum page, where you (Chuck) explained your plan to fill the void. I may not have found TIRE if I hadn't seen that discussion, which brings me to my first point...

1) When I clicked on "Related" on the Lazarus page in the Chrome web store TIRE didn't show up. It also didn't show up when I searched for "form recovery" or anything else I thought of. TIRE is a fine acronym, but if finding the extension depends on searching for "text input," I fear this tool won't get the use it deserves. I don't know much about Google's search algorithm works or how "Related" extensions are chosen, but I figure you do. It seems pretty clear that the word "form" should be in the description. I also just noticed that the full title in the Chrome web store has a typo: "Recover" instead of "Recovery." I'd think a search for "form recovery" would show me titles that include "Recover" (especially on a Google site), but it doesn't.

2) One similar extension that I did find when I searched for "form recovery" (after I had discovered TIRE) was Typio: https://chrome.google.com/webstore/deta ... pppbpoedaa. I'm now testing it out at the same time that I'm using TIRE. Do you think that could cause problems for either extension (or Chrome)? If not, maybe I'll continue to use both.

3) You mention that TIRE can slow down Chrome on old computers, leading to your suggestion to choose "Individual" and whitelist just a few pages. That sounds dangerous to me, so I'd like to know roughly what you mean by "old computers." (Btw, it took me a while to find the "Individual" and "All but blacklisted" options, so perhaps you could mention that you need to scroll to the bottom of the Pages page.) I'm guessing that scanning frequency can be relevant to speed. True? I changed it to 10 seconds.

4) I found the idea of whitelisting and blacklisting confusing because the whitelisting example that first comes to mind involves *disabling* one's ad blocker on certain websites. So from that POV, whitelisting seems to be what you call blacklisting. Although I'm sure the distinction seems like common knowledge to you, I suggest you spell out what the two words mean for the sake of tech-challenged users like me.

5) I've found at least one page with a form where the TIRE icon shows the NI label and rescanning the page doesn't help: http://www.abjortho.com/contactus. Is this simply an example of a page where the "TML coding... is so complex and/or convoluted that TIRE cannot proceed"? The page doesn't look complicated, but I suppose that has little to do with the complexity of the coding.

6) The "Show TIRE button" option doesn't always work the way it's supposed to. Depending on where exactly the button appears (which seems unpredictable), it can be a little distracting, so I tried the "Only when hovering" option. I hadn't read the description on the "About" page, which says the button should still appear in the input field (when your cursor is there as wll), but in many cases the button appears outside the input field (see attached screenshot). I actually prefer this in a way, but the button's behavior is still unpredictable. Sometimes its visibility works the way you describe (apart from its location), but other times it will disappear 1.5 seconds (or less) after your cursor moves *into* the input field. I might just turn the button off completely, look for the "Fill" badge, and hope that's enough. Right now, it seems the biggest risk is forgetting to exit the Options properly, but I suspect that won't be an issue once I'm done experimenting.

7) When I clicked on the link in TIRE that opened this forum, I wondered if it was the wrong link because of the forum's name. When I saw that the only TIRE entry in the Board Index was listed under "Firefox Extensions" and that there was no other category, my hunch only got stronger. I figured you had created a TIRE extension for Firefox as well and that I needed to find your forum for Chrome extensions. Needless to say, I eventually realized I was in the right place. I suspect you have a reason not to mess with the forum name, but don't you think TIRE belongs in a category other than Firefox Extensions?

That's it for now...
Attachments
TIRE.jpg
Last edited by yeltommo on Mon Nov 13, 2017 5:16 pm, edited 6 times in total.
yeltommo
 
Posts: 2
Joined: Fri Nov 10, 2017 5:44 pm

Re: Misc. suggestions, questions, and issues from a new user

Postby cbaker_admin » Mon Nov 13, 2017 12:15 pm

Thank you very much for the detailed report.

I'm currently under the gun addressing issues with my Firefox extensions being ported to Pale Moon (Firefox releases the much talked about and often feared v57 tomorrow). I will investigate all your suggestions, questions, and issues and respond in greater detail soon.
Chuck
cbaker_admin
Site Admin
 
Posts: 4580
Joined: Sun Nov 27, 2005 10:51 pm
Location: Glendale, AZ USA

Re: Misc. suggestions, questions, and issues from a new user

Postby yeltommo » Mon Nov 13, 2017 4:28 pm

No rush. Btw, I forgot one minor thing, so I added a seventh point to my original post.
yeltommo
 
Posts: 2
Joined: Fri Nov 10, 2017 5:44 pm


Return to TIRE

Who is online

Users browsing this forum: No registered users and 0 guests

cron