doc.body is undefined

[flying-sheep]

in makeRequestToPrivilegedScript, neither doc.head nor doc.body exist, resulting in exception flood.

[adam-p]

Is this Firefox or Thunderbird? What version? Does the problem persist after you restart the application?

[flying-sheep]

sorry. the error is in the browser inspector (browser tools console). i have alternatingly

TypeError: doc.body is undefined

and

"Markdown Here: failing back to content script preferences code" utils.js:20
SyntaxError: JSON.parse: unexpected end of data at line 1 column 1 of the JSON data
Stack-Trace:
MozillaOptionsStore._sendRequest@chrome://markdown_here/content/background-services.js -> resource://markdown_here_common/options-store.js:308:1
MozillaOptionsStore.get@chrome://markdown_here/content/background-services.js -> resource://markdown_here_common/options-store.js:263:1
markdown_here.setupButton/intervalCheck@chrome://markdown_here/content/ff-overlay.js:351:9

[adam-p]

Can you check another thing? Go into your about:config page, search for "markdown-here" and share a screenshot of the results. Thanks.

I'm now experiencing the same problem you had, and it seems to be be due to extensions.markdown-here.services.sync.prefs.sync.extensions.markdown-here.*. Those shouldn't exist at all. They should instead be services.sync.prefs.sync.extensions.markdown-here.*. (I have both forms.)

So, if you do have config entries that start with ``extensions.markdown-here.services.sync.prefs.sync.extensions.markdown-here.`, then the fix (or at least workaround) is to delete them.

[adam-p]

I believe I fixed this problem in 89359f0. But I would still really appreciate a screenshot of your "markdown-here" results in about:config, because I don't understand how you could have gotten into the bad state.

(It happened to me only by fooling around with test code.)

[flying-sheep]

idk if this was the PC where it happened, but here you go:

[adam-p]

@flying-sheep: Thanks. I can't see anything there what would cause the problem. So maybe it was a different computer? Anyway, hopefully the fix in the next release will sort out your problem.