Autofill v6.12.0 released

[thdoan]

This release's main feature is something that I've been wanting to add for awhile now: the ability to save text fields as you type in case Chrome crashes when you're in the middle of filling out a form or writing a long post. With this option enabled, every text field you enter will be automatically backed up to a special profile named Backup - {site domain} if you enter the minimum number of characters (default: 100). Backup profiles are always executed without having to set the profile as active when you return to the same site the rules were generated from. NOTE: Avoid changing the backup threshold to something too low like 1 char or else Autofill can generate A LOT of backup profiles. As a good house cleaning practice, you should delete the backup profiles when you no longer need them to prevent the backup rules conflicting with your normal rules.

Full changelog:

• Added option to automatically back up text fields
  
• Added logic to replace numbers in 'name' with regex pattern
  
• Added ability to randomly select menus and toggle checkboxes
  
• Improved support for form validation
  
• Improved dynamically inserted elements observer
  
• Automatically enable context menu when in manual mode
  
• Fixed delay range input still disabled after importing
  
• Fixed manual mode not honored for dynamically inserted fields
  
• Fixed JavaScript error for some values containing line breaks
  
• Fixed import issue
  
• Fixed selected field highlighting issue
  

Version 6.12.0 should roll out to all Chrome browsers shortly.

[thdoan]

Version 6.12.1 has just been released.

Changes:

• Fixed site filters getting wiped when adding rules
  

[ell...@ninjatune.net]

This new version seems to break google forms compatibility for me.

When adding rules for the whole page every field is assigned the same name in Autofield options:

^entry\.\d{3,}$

This previously was being recorded as the unique id for individual form elements ie:

^entry\.2009076994$

Any idea of a fix / could you provide a link to a previous version from ~the last week that was working?

This extension is a real time saver and I appreciate your hard work.

Thanks!

[ell...@ninjatune.net]

Some further information (again pertaining to google forms) - when trying to use the wizard on a per form-field basis, I now get receive the error

Enter a value for the highlighted field.

Thanks 

[thdoan]

Oh, it seems like one of the new features in v6.12.0 ("Added logic to replace numbers in 'name' with regex pattern") is creating an issue for Google forms. That feature was added to try and solve the problem of input fields that have dynamically generated names containing random numbers (e.g., <input name="field_858651051351">). For such fields, a rule generated by the wizard would not work because the next time the user goes to that page, the field would have a different name (e.g., <input name="field_915865811911">). By replacing the series of numbers with the regular expression \d{3,} (match any string containing at least three numbers), the aim was to make the wizard smarter, but I see now that it is also causing issues as in your case.

Okay, I will remove this feature and release the hotfix v6.12.2 shortly. Thanks for reporting!

[thdoan]

Version 6.12.2 has just been published to address this issue.

[Elliot Seeds]

Great, that seems to have fixed the issue.

Thanks for the swift update! 

Elliot Seeds
Ninja Tune / Big Dada / Counter / Brainfeeder / Werkdiscs / R'COUP'D
90 Kennington Lane
London, SE11 4XD
+44 (0) 20 7820 3535

www.ninjatune.net
www.bigdada.com
www.counterrecords.com
www.brainfeedersite.com
www.werkdiscs.com

[les.ua...@gmail.com]

Hi. I'm now running Google Chrome Version 56.0.2888.0 canary (64-bit) and Autofill v 6.12.2 and am still getting this error. Any help, please?

[thdoan]

Hi les.uat.test, which error are you referring to?

[les.ua...@gmail.com]

The one where it says "Enter a value for the highlighted field".

[thdoan]

I cannot reproduce this on the practice form. Can you send me the URL to this form to test? Also let me know which input you're right-clicking on.

One thing you can try: wait about 10 seconds before right-clicking on the input and let me know if that solves the problem. Sometimes the page takes longer to finish loading, so you might be right-clicking before Autofill is initiated.

[les.ua...@gmail.com]

Sorry, they're internal pages. I tried waiting and after about 20+ seconds it saved. There must be a lot more happening behind the scenes than I realise!

cheers

On Friday, October 7, 2016 at 1:54:14 PM UTC+8, thdoan wrote:

[thdoan]

Yeah, when a server is slow to load pages or if a page is loading very large files, then things can get unpredictable -- that is the nature of the internet beast.

I was even able to reproduce this issue on the Practice Form by right-clicking inside the Description text box and selecting "Add rule for this field" as soon as I could as the page is loading.

[thdoan]

Since this is beyond our control, I've come up with the next best thing: in the next release you'll see a message saying "The page is still loading, please try again in a few seconds." if you try to use the wizard before the page is done loading.

On Wednesday, October 19, 2016 at 8:31:32 AM UTC+8, les.ua...@gmail.com wrote:

[les.ua...@gmail.com]

Hi. Good job on the extension, BTW. It's gaining traction in the office and has made repetative tasks SO much easier.

These pages are quite simple (i.e. 1/2 dozen fields) and hosted on an internal server for development.

Something I have been able to narrow down is that if I click in a field and try Add Rules for a Field, then I get the error. Even if I try after a couple of minutes (i.e. between the time I started replying to this post and the time I finished typing - which, using 2 fingers, can take some time ;-), the error still occurs.

If I click outside of a field and Add Rules for a Page, then it works.

Could there be something in this?

[thdoan]

Hmm...can you maybe save the page as HTML and attach it in the next reply? It's hard to debug without the actual form you're having issue with.

[les.ua...@gmail.com]

Ok, here you go. I was positioned in the Contact Name field trying to add Form 4 to the profile.

And while we're here, what's the feasability of adding a sort of "dynamic" field filler. As in I would like to have the Reference generate a new number each time the profile is run. 

E.g. the first time I run the Contact Information profile, it fills in Reference with "sometext 1". The next time I run it it would fill in Reference with "sometext 2" (automatically incrementing the numeric value).

Or not possible??

On Friday, October 7, 2016 at 1:54:14 PM UTC+8, thdoan wrote:

[thdoan]

Cool, I'll take a look at your form when I get a chance.

Regarding "dynamic" field filler: it's already possible using the special variable {number++}

e.g.: Value = sometext {1++}

You can find out about the other variables here (under "Expand variables" section):

http://www.tohodo.com/autofill/help-chrome.html#other

[les.ua...@gmail.com]

Excellent - just what I wanted!

[thdoan]

To give you an update, I just looked at your test page today and was able to reproduce your issue. That's the first step in debugging this :-)

[thdoan]

UPDATE: This issue has been fixed and it go out in the next release.

[les.ua...@gmail.com]

That is good news. Looking forward to the next release, then!