No changes still produce changes
See original GitHub issueGiven
<script src="foo.js"></script>
<script>console.log('foo')</script>
Morph this into
<script>console.log('foo')</script>
Morhdom seems to be doing two changes in scenarios like this.
- It will morph the removed script tag that has a src attribute into the other inline script tag.
- It will discard the second script tag.
The “right” thing to do, would be to use the best match (e.g, its more likely that node 1 was removed here rather than node 1 was mutated into the properties of node 2, and node 2 was removed).
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (2 by maintainers)
Top Results From Across the Web
Git says there are changes but there are none - Stack Overflow
If something is different here, git status prints the file's name and tells you that this is a change that is not yet...
Read more >GitHub Desktop is showing changes but I havent made ...
I just closed GitHub Desktop and re-opened it and it's still showing 1 file under changes. Any way I can resolve this with...
Read more >Git commit, no changes detected (problem solved)
Hi all : After I edit a file and commit, it always shows " No changes detected ", and the file I edit,...
Read more >Why Change Programs Don't Produce Change
Successful change efforts focus on the work itself, not on abstractions like “participation” or “culture.” Once general managers understand the logic of this ......
Read more >Make changes to an existing data source in Power Pivot
Table and column mappings. Remove references to columns that are no longer used. The tables, views, or columns you get from the external...
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 FreeTop 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
Top GitHub Comments
No action items. Closing for now…
@patrick-steele-idem Am already doing that, but the issue is more on a whole IMHO. Take a collection of
<li>
items, remove one. All of the items are then repurposed (first match is used) rather than the one item removed, semantically this seems like the wrong thing to do.