-
-
Notifications
You must be signed in to change notification settings - Fork 55
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
dom.webcomponents.shadowdom.enabled doesn't exist #40
Comments
You also will need to enable dom.getRootNode.enabled. :) Then it will work for you. I did not knew about waterfox browser, I will add this too in addons page and in github also so that future users of this extension does not face problem when using waterfox browser. :) |
Thanks! Works as expected now. I'd also recommend adding a bit on what these two settings do and why they need to be changed. I've used lots of add-ons and don't recall ever having to change anything in about:config for them to work, including when using ones that generate pop-ups like this one does, so I wonder if there's a better way to achieve whatever is needed that requires them to be changed and I'd like to know what's happening when I change them so I know I'm not reducing security or functionality in some way. |
I use shadow dom for the popup. I use Shadow DOM due to level of encapsulation it provides. |
Thanks. A few follow-up questions:
|
Yeah missed the link: https://glazkov.com/2011/01/14/what-the-heck-is-shadow-dom/ By encapsulation I mean by popup is separated from other things in page and their CSS does not affect my popup. Other addon if they do achieve they are simply not using shadow dom and it may cause style from outside bleed into their popup. |
Thanks again. Looks pretty neat. Didn't understand it all, but the gist seems to be that essentially it's like an island for code in the page, like an iframe for a single object. So getRootNode must also be enabled by default in newer/other browsers, and just disabled by default in Waterfox for some reason, so calling the function failed. Interesting. Anyways, it's good to know more about these entries. Thanks for all the info. :) Feel free to close the issue when you want. I'd do it but not sure if you want to keep it open until you make changes to the instructions. |
Addons page says to set dom.webcomponents.shadowdom.enabled to enabled, but my browser (Waterfox 2020.12 64-bit) doesn't have that; it only has dom.webcomponents.enabled, which did make a difference when setting to enabled though it still doesn't work (just says "Searching Please Wait...") as mentioned in issue #34.
The text was updated successfully, but these errors were encountered: