Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DON'T MERGE, this is still for discussion:
Meaningful changes:
fn test_dom_vdom_standalone()
in order to test a standalone DomUpdater concept.question on style
Do you like the 'style' extension (this PR, top most commit), if so I can create a seperate PR for it. It basically can now parse a <div with a style attribute like:
and then build html from it. I think there is still changes to be desired, for instance the generated html from the parsed strucutre looks like: so it basically removes spaces between key and value of the style parameter ...question on updates
When I integrate the DomUpdater into my project at nixcloud/pankat-replit@37b6ca1#diff-5365bd0f6f96dba0088da6cc6d5640f519c460110eb53ae48377086445666490 and try to let it update a already existing section I see a huge changes in the html structure on the first update (unexpected as there are no meaningful changes) and minimal changes on consecutive ones (expected). Why is that?
I can build a standalone version tonight. For now, this is the code i'm using to create a DomNode from existing html.
html before dom update:
html after dom update