-
Notifications
You must be signed in to change notification settings - Fork 69
feat: solve the problem of numbers changing after li tag indentation #469
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
wuyiping0628
wants to merge
1
commit into
dev
Choose a base branch
from
wyp/indentation-0513
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider the impact of forcing all indent levels to decimal numbering.
The new rules override the original varied counter styles with uniform decimal numbering:
lower-alpha(a, b, c) → Now:decimal(1, 2, 3)lower-roman(i, ii, iii) → Now:decimal(1, 2, 3)lower-alpha→ Now:decimallower-roman→ Now:decimallower-alpha→ Now:decimallower-roman→ Now:decimalWhile this change solves the stated problem of "numbers changing after indentation," it eliminates the visual hierarchy that different numbering styles provide in deeply nested lists. Users may find it harder to distinguish nesting levels when all levels use the same decimal format.
If the varied styles are intentionally being removed, consider documenting this behavior change and its UX implications. If the original varied styles should be preserved while fixing the indentation bug, the root cause may require a different solution.
Also applies to: 144-146, 160-162, 176-178, 192-194, 208-210, 224-226, 240-242, 256-258
🤖 Prompt for AI Agents
🧩 Analysis chain
🏁 Script executed:
Repository: opentiny/tiny-editor
Length of output: 3138
🏁 Script executed:
cat -n packages/fluent-editor/src/assets/editor.scss | head -280Repository: opentiny/tiny-editor
Length of output: 7290
🏁 Script executed:
rg -n "li\.ordered\.ql-indent|li\.ql-indent" packages/fluent-editor/src/assets/editor.scssRepository: opentiny/tiny-editor
Length of output: 1345
Remove or refactor the new
li.ql-indent-{1-9} .ql-ui:beforerules to avoid dual marker rendering and selector scope conflicts.The new rules at lines 128–258 introduce two critical problems:
Dual marker rendering: Both
li.ordered.ql-indent-1::before(line 124) andli.ql-indent-1 .ql-ui:before(line 128) target the same list item. Since they render on different DOM elements (the<li>itself vs. its.ql-uichild span), both markers will display simultaneously if the.ql-uielement is present.Selector scope too broad: The new selector
li.ql-indent-1matches any<li>with that class, including unordered lists. From the DOM evidence, both<li class="ordered">and<li class="bullet">contain.ql-uichildren, meaning bullet lists will incorrectly display decimal counters via the new rules with!important, overriding any intended styling.Additionally, all nine new rules use uniform decimal formatting, discarding the original visual hierarchy of alternating formats (lower-alpha, lower-roman, decimal). Consider either removing these new rules if the original
li.ordered.ql-indent-n::beforeapproach is now working, or replace them with a single SCSS mixin to reduce duplication and improve maintainability.🤖 Prompt for AI Agents