logseq / logseq/logseq

parse the relationship between ul > li (html list elements) from the clipboard into outlier hierarchy

Open
#9,635 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

:type/feature-request done-by-plugin editor:copy-paste estimate: large estimate: medium
Dominant language
Clojure
Stars
45k
Forks
2.8k
Avg merge
1d 22h
Merged PRs (30d)
105

Description

### Search first

- [X] I searched and no similar issues were found

### What Happened?

When pasting a sturcture for list elements, the relationship of the parent-children is incorrect.

### Reproduce the Bug

1. Paste the following structure into a [codepen](https://codepen.io/) page (or any HTML renderer)
```


  • level1-1

  • level1-2

    • level2-1

    • level2-2


      • level3-1


    • level2-3



  • level1-3


```
2. Copy the result HTML
3. Paste into Logseq

### Expected Behavior

Expected:
```
- level1-1
- level1-2
- level2-1
- level2-2
- level3-1
- level2-3
- level1-3
```

Current results:
```
- level1-1
- level1-2
- level2-1
- level2-2
- level3-1
- level2-3
- level1-3
```

### Screenshots

_No response_

### Desktop or Mobile Platform Information

Logseq version 0.9.8 on windows 10 build 19044.2965.

### Additional Context

_No response_

### Are you willing to submit a PR? If you know how to fix the bug.

- [ ] I'm willing to submit a PR (Thank you!)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue in Logseq by copying the provided nested HTML list and pasting it into the editor, then trace the clipboard HTML handling that builds the outliner hierarchy. The work is done when nested ul > li relationships produce the expected indentation, including the level3-1 item under level2-2.

Written by the indexing model from the issue text.

Assessment

Tech stack
clojure, html
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.