-
Notifications
You must be signed in to change notification settings - Fork 259
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Sticky" not working in Firefox extension content script #447
Comments
Hello, and sorry for the delay! That message shows up when an exception occurs in the _init method of UI components. So Sticky.prototype._init must be throwing an exception somewhere. Could you try to wrap it in a try..catch, and log the error? Also, what options are you using? |
I'm using Here's my
Thanks! |
Errors in _init just get trapped in the UI component machinery. That's why
you need the try..catch to really be inside the _init function.
Those options don't seem too advanced. Probably your problem will be
reproducible in any usage of Sticky in that environment. I'll give it a try
later today and tell you how it went.
|
I'm sorry, but I can't find the time to learn how to do this. Could you try to modify ink-all by wrapping Sticky's _init method in a try..catch and logging the exception and stack for me? I should be able to tell what went wrong and devise a fix for Firefox extensions then. |
I built a Chrome extension that injects the Ink CSS and JS into certain pages that the user views. It works wonderfully. But now I'm trying to port the extension to Firefox, and I can't get Ink to work.
I'm injecting the Ink JS using a content script. When I run
cfx run
to test the extension, I get this error:The text was updated successfully, but these errors were encountered: