Closed Bug 1499533 Opened Last year Closed Last year

Clicking report site issue does nothing on a specific page (probably due to weird console logging)

Categories

(Web Compatibility :: Tooling & Investigations, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: miketaylr, Assigned: twisniewski)

References

()

Details

Attachments

(1 file)

STR: 

1. in nightly, navigate to https://miketaylr.com/bzla/console-shit.html (pardon my language there...)
2. click the report site issue page action item

expected:
new tab opens in @ webcompat.com, etc

actual:
nothing

In the browser console, you get the following message:

TypeError: arg is null; can't access its "toString" property 
data:function getInfoFrameScript(messageName) { /* eslint-env mozilla/frame-script:40:9 

(it's a demo page logging out a bunch of different data types, maybe it's barfing on null or Infinity?)
Fix console log stringifying bug in webcompat reporter
And a try run (just to test our fault-tolerance against cosmic rays, I guess): https://treeherder.mozilla.org/#/jobs?repo=try&revision=32b5892ee931edebab97cbe1f8b95eb734ba06e8
Hah... look like those pesky cosmic rays got us again after all. Here's another try-run that doesn't expect the line numbers in the console log to always be the same: https://treeherder.mozilla.org/#/jobs?repo=try&revision=3b0e72b8e0da1e3deb43757ae4b4b283bc222d3a
Pushed by mitaylor@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/8f1ae707ff7b
Fix console log stringifying bug in webcompat reporter; r=miketaylr
https://hg.mozilla.org/mozilla-central/rev/8f1ae707ff7b
Status: NEW → RESOLVED
Closed: Last year
Resolution: --- → FIXED
Assignee: nobody → twisniewski
You need to log in before you can comment on or make changes to this bug.