Chris Andrejewski

> @matthewp a few times people have done something like require("can-util/js/assign/") which is a steal thing From a thread in #team-open-source Jul 6th at 2:50 PM > @matthewp but breaks...

I've suggested that before, but I think you said it seemed bad to have an option that is basically "do things the right way." I care less about `~` and...

@c0ncentus In the first example, the behavior of `` is a bit odd; when given the Chrome (90.0.4430.212) as an `innerHTML` we get: ```html ``` I see the same treatment...

See https://github.com/andrejewski/himalaya/issues/55#issuecomment-321808564. I am against changing what `tagName` means in the current spec. Maybe we can add a `rawStartingTagName` and `rawClosingTagName` fields to the output as was done for position...

Himalaya does account for some of these cases with [`closingTagAncestorBreakers`](https://github.com/andrejewski/himalaya/blob/7f1f8900b3d545f87a36cf93d3b8e8101ae3a394/src/tags.js#L23), where we could add `{ p: [...blockLevelTags] }`. I think my hesitation to include all possible rules stems from not...

@DAreRodz I *think* the fix to your issue is a few lines of code on your end: ```js import {parseDefaults} from 'himalaya' parseDefaults.closingTagAncestorBreakers.p = ['div'] ``` This is preferable to...

Hmm; this ought to be fixed, it should work as you expect and has some special handling already: https://github.com/andrejewski/himalaya/blob/master/src/tags.js#L5 @07akioni are you interested in making the fix and adding tests...

A reproducible test case with data would be really helpful! There are a few functions where recursion is used. From a quick reading, they all relate to nesting levels. I...

Unfortunately I don't think I can reproduce it on my own. I also played around with some nested divs and it handled that fine. If I could guess, since you...

Is the issue that it is not scrollable or that there isn't a way to copy the full output? The demo site is generally for playing with small HTML snippets,...