TypeError: l.getRowCount is not a function

[GuestPassingBy]

TypeError: l.getRowCount is not a function noscriptOptions.js:606:18

I'm seeing the above error message (many repeats) in the browser console after the last step of:

1) Go to NoScript Options->Advanced->ABE->USER Rulesets
2) Add or remove a BLANK line (before, after or amongst many existing rulesets)
3) Hit OK or cancel

Known? If not, can duplicate?

NoScript = 2.6.9.34
Firefox = 39.0.3

[Thrawn]

Can't reproduce it here.

[GuestPassingBy]

Thank you for the attempt and reply. I'm seeing this in three different FF39.0.3 browsers running on different Windows 7 systems. Two are installed versions with an Internet connection. One is a fresh portable app install with a fresh NoScript install (both unmodified) on a system with no Internet connection.

I looked at it again, and I now think that it doesn't happen the first time you attempt it after browser startup. Example:

1) Launch Firefox
2) Click NoScript Icon, go to Options->Advanced->ABE->USER Rulesets
3) Click in the right side box, move the cursor to the end of the existing text, then hit ENTER to add a blank line
4) Click OK button at bottom <-- I don't see the browser console error message after this first attempt
5) Click NoScript Icon, go to Options->Advanced->ABE->USER Rulesets
6) Click in the right side box, move the cursor to the end of the existing text, then hit ENTER to add a blank line
7) Click OK <-- I do see the browser console error message after this second attempt, and during all subsequent attempts

It also happens with System Rulesets, so I suspect it is a problem with the control/list code that they both share. Given that it happens on all the browsers I've tested, including a fresh FF portable + fresh NoScript, I think this is very likely to be a genuine bug.

[Thrawn]

Ah, yes, it does happen on the second try.

It doesn't seem to affect the functionality of ABE, so it's probably not high priority, but it might also be trivial to fix. Up to Giorgio.

[GuestPassingBy]

Good, thanks for trying again. By the way, I am aware of the NoScript Development "Bug reports and enhancement requests" area. However, I am seriously trying to reduce accounts and wish to continue doing so. Is there an easy way for you green nick peeps to mark a thread "please have a look Giorgio", or in some other way bring it to his attention? Would putting a subject tag in bug reports make your lives easier? I'd like to continue pointing out things I think are bugs (if I do come across any more in the future) via this no account required area. That OK?

[barbaz]

Sure, no problem.

Unfortunately we don't have any way to flag threads for his attention. So unless someone finds the cause & contributes a patch, just have to hope he eventually sees this thread and gets to it.

[Giorgio Maone]

Should be fixed in latest development build 2.6.9.35rc1, thanks.