Simmer stops working after reconfigure
See original GitHub issueHi, I’m trying to use Simmer library in my JS project (using dist/simmer.js). I need to use configuration different than default one so I’ve tried to reconfigure Simmer in this way:
var simmer = window.Simmer.configure({
depth: 6
});
var selector = simmer(node);
In this case “selector” is always false, no matter what node is. If I remove .configure() call then everything works as expected.
Issue Analytics
- State:
- Created 6 years ago
- Comments:13 (8 by maintainers)
Top Results From Across the Web
How to Simmer: 4 Ways to Maintain a Simmer - Masterclass
Adjust the temperature. Turn the temperature down slightly if the water is on the verge of boiling. If the temperature is too low...
Read more >What does "bring to a simmer" mean? - Seasoned Advice
A simmer is when the liquid at the very of the bottom of pan boils, but not all the liquid. You get little...
Read more >Simmer vs. Boil: What Is Simmering & What Does It Mean?
When liquid, either water or broth, is simmering, you'll see a few bubbles floating up to the surface. This method slowly cooks the...
Read more >Cooking Class: Boiling and Simmering
This technique cooks food at a relatively high temperature―212 degrees is the boiling point for water at sea level. When liquids boil, bubbles ......
Read more >Why Recipes Say to Bring to a Boil, Then Reduce to Simmer
The biggest reason why recipes have you boil first, then reduce to a simmer is speed and efficiency. When you're bringing water, a...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Amazing, it works now. Thank you very much 😃
Hi, I have found the problem. This should work now, as the context was expecting a window not a document, but I’ve extended it to support document fragments and should work across the board, now.