-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[svg] Introduce "Frozen line" to mark the edge of fixed rows/columns #6639
Labels
Comments
6 tasks
9 tasks
15 tasks
I have an implementation that I will soon push to the PR. However, one change was proposed and I will decide if I can make it in 8.0.0: #6651 |
warpech
added a commit
that referenced
this issue
Jan 20, 2020
The frozen line is implemented as a special case of gridline, with the color soldered in CSS. This commit adds a class name ""wtTableCornerCell" for the corner cell in the top left overlay. This allows to write specific CSS selectors for that cell.
wojciechczerniak
changed the title
[8.0.0-svg] Introduce "Frozen line" to mark the edge of fixed rows/columns
[svg] Introduce "Frozen line" to mark the edge of fixed rows/columns
May 19, 2020
mrpiotr-dev
added
Core: Walkontable
Plugin
and removed
Type: Improvement suggestion
labels
Apr 15, 2021
6 tasks
Closing as the SVG PR was closed. Explanation in #6157 (comment) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The SVG borders PR (#6157) contains a visual breaking change:
More details about that problem here by @aninde: #6594 (comment)
@krzysztofspilka, @wojciechczerniak and I have discussed how to change the spec to fix the problem reported in #6594 (comment).
Our conclusion is to introduce a new feature in this PR: "Frozen line" [1]. The borders (incl. custom borders and selection borders) will not be rendered on the frozen line, except for the parts of borders that are thicker than the frozen line [2].
This will be fixed within the SVG borders PR #6157.
Links to the updated specs:
🚨 This is a (Visual) breaking change
The text was updated successfully, but these errors were encountered: