1287598 - shouldLog error in Console.jsm prevents form submission

Status: RESOLVED INCOMPLETE

(Toolkit :: Form Manager, defect)

Description

[Peter Bengtsson [:peterbe]]

Attachment: Screen Shot 2016-07-18 at 4.39.50 PM.png

On various pages that contain a form with a sbumit button, nothing happens when I press the button. I get this error in the browser console:

TypeError: shouldLog is not a function[Learn More]

This started to happen today. Using 49.0a2 (2016-07-18).

At the moment, I can fill in this form because I've signed in with Chrome.

Comment 1

[:Gijs (he/him)]

Does this happen on a clean profile? e10s on or off make a difference?

Comment 2

[:Gijs (he/him)]

(also, can you link to a concrete testcase so it's easier for others to try to reproduce the problem?)

Comment 3

[:Gijs (he/him)]

e.g. http://jsbin.com/qoducavamu/edit?html,output does not reproduce this problem for me on today's devedition build.

Comment 4

[:Gijs (he/him)]

If you open resource://gre/modules/Console.jsm and search for 'shouldLog', do you see a function shouldLog() entry? Because I do (on OS X devedition from the 19th). So the errors don't really make sense unless your copy of devedition got corrupted or some add-on is messing with things.

Comment 5

[Peter Bengtsson [:peterbe]]

Attachment: Screen Shot 2016-07-19 at 8.44.58 AM.png

Problem no longer reproducible after todays DevEdition update. 

The problem could still happen I guess. Clearly, wherever the shouldLog function is defined, there's some race condition where it relies on this to be in the scope but it's not.

Comment 6

[Peter Bengtsson [:peterbe]]

Wow! The shouldLog function is defined in the very same file. 
https://dxr.mozilla.org/mozilla-central/source/toolkit/modules/Console.jsm#508

Comment 7

[:Gijs (he/him)]

(In reply to Peter Bengtsson [:peterbe] from comment #6)
> Wow! The shouldLog function is defined in the very same file. 
> https://dxr.mozilla.org/mozilla-central/source/toolkit/modules/Console.
> jsm#508

Well, yes, so "not in scope" doesn't make any sense. It should always be in scope. I don't understand why it would ever not be available. If you download yesterday's devedition separately, does the problem reoccur? :-\

Comment 8

[Peter Bengtsson [:peterbe]]

How do I download yesterdays devedition?

Comment 9

[:Gijs (he/him)]

https://queue.taskcluster.net/v1/task/UyRui6_rRaSwS5x-fVJB6w/artifacts/public%2Fbuild%2Ffirefox-49.0a2.en-US.mac.dmg

from:

https://tools.taskcluster.net/index/artifacts/#gecko.v2.mozilla-aurora.nightly.2016.07.18.latest.firefox/gecko.v2.mozilla-aurora.nightly.2016.07.18.latest.firefox.macosx64-opt

Comment 10

[Peter Bengtsson [:peterbe]]

That did not work. Downloading yesterdays build and running it did work, but the problem is no longer reproducible :(

Comment 11

[:Gijs (he/him)]

Going to resolve INCO because without being able to reproduce it seems impossible to track down what's causing this. If it happens again we can investigate further.