-
-
Notifications
You must be signed in to change notification settings - Fork 1
Description
Feature
I wonder if it is necessary to reset the shadow and add an additional border for the button at the bottom of a closed ticket.
A effect after deactivating the border and shadow, without fixing the top button (in which case the selectors would have to be split into two or CSS nesting would have to be implemented, as if Chrome allows this (Sources say that the minimum version will then change from 105 to 112 or 120 so as not to activate the Experimental Web Platform features) and the minimum version of Firefox supports CSS nesting).
Theoretically, the ‘activation’ state is quite short, and a second click on the anchor with the date does not activate it anymore, but the navigation buttons in the card history do (same other anchors and back to completed "anchor").
Reason
Potentially compatible with other buttons.
I am uncertain to what extent this interferes with maintaining a consistent UI with the borders of other sections (rejected status, unplanned or entry) or with disabled persons, given that this element does not have a border.
I don't know how it worked about 5 years ago (at that time, there may not have been any borders at all when the website owners ignored the issue of active elements).
It is possible that this has already been discussed somewhere in the reports.
Theoretically, it is not even noticeable that the button is about 1 circle-range pixel larger than the rest, until the stock marking of the active section is unlocked (where making the circle about one pixel larger may become slightly noticeable, especially when it comes across the avatar).
Theoretically, this topic gives me déjà vu.
