Conversation
|
QuickCollapse button for example is still broken though, but only on mobile |
|
For Swage, the changes need to be done in https://github.com/FreshRSS/FreshRSS/blob/edge/p/themes/Swage/swage.scss sass swage.scss:swage.cssAs a side note, I would like to get rid of SCSS at some point to use only standard CSS, using CSS nesting. It should be possible to make an automatic conversion from our current SCSS files used by some of our themes. Help welcome. |
|
turns out I didn't fix them correctly |
| --color-text-light: #fcfcfc; | ||
| --color-text-light-darker: #969696; | ||
| --color-text-dark: #181621; | ||
| --color-text-nav: rgb(0, 71.6947368421, 139); | ||
| --color-text-aside: #22303d; |
There was a problem hiding this comment.
Please check the text indentation and respect the given.
There was a problem hiding this comment.
I'm not sure why that happened
p/themes/Swage/swage.css
Outdated
| --color-text-shadow-light: #f5f3f3; | ||
| --color-box-shadow-light: rgb(221.8181818182, 215.1818181818, 215.1818181818); | ||
| --color-border-light: #f5f3f3; | ||
| --color-border-light-darker: rgb(221.8181818182, 215.1818181818, 215.1818181818); | ||
| --color-border-grey: #e3e3e3; |
There was a problem hiding this comment.
Could you please give examples why you change so many colors?
Would it be possible to have cleaner numbers instead of having 10 positions after decimal point?
There was a problem hiding this comment.
I think that is due to the current SASS default conversion when running sass swage.scss:swage.css. It may require an option to the command line. Suggestion welcome
There was a problem hiding this comment.
By the way, as written above:
As a side note, I would like to get rid of SCSS at some point to use only standard CSS, using CSS nesting. It should be possible to make an automatic conversion from our current SCSS files used by some of our themes. Help welcome.
which would also solve such issues
There was a problem hiding this comment.
Yes, it is due to SASS, I changed one color variable inside the .scss file, and that changed more colors.
It may be enough to just change the color --color-background-light in .form-group:hover, where I specifically need it:
FreshRSS/p/themes/Swage/swage.scss
Lines 235 to 243 in 37fa681
I think it's fine as is though.
There was a problem hiding this comment.
yes ,I agree to get rid of SCSS (it is a task outside this PR). But before we should check the compatibility with older devices and browser. CSS nesting is quite new
There was a problem hiding this comment.
Yes for another PR.
CSS nesting is "Baseline 2023", so I think it is good enough to migrate some of our non-default themes. In case of problem, a user can fall back to another theme
There was a problem hiding this comment.
|
I broke the actualize button from appearing after moving changes from css to scss, so I'll have to fix that too. |
|
todo:
|
|
to be honest: this PR blewed up to much more than just CSS fixes for Swage. I would suggest to split the PR and keep the focus here on Swage |
Yes.
Which parts? |
|
This parts could be a separate PR because it will affect also the other themes or the other themes could be benefit from it too:
|
It doesn't look like any other themes aside from Swage can benefit from those changes
I guess this does affect all themes, not just Swage
Those are just for Swage (adding borders, margins and paddings in some places)
Yes, this part would make sense, but I will also make the user queries dropdown visible (I haven't made it visible yet, I'll have to also hide the Before: After (still have to make user queries visible): |
|
Done #7616 |
|
I consider it ready but testing welcome |
|
Yes, I would like to take time to look a bit closer to the changes in |
I did just find one issue, fixing it right now |
|
Resolves the same |
|
What's the specific concern with layout.phtml? |
|
It looks now ok for me. |
|
The SCSS annoyances will vanish when we get to implement: |




.form-groupand button inside search dropdown hover colors slightly darker, for better visibilityinput, select, textareadon't overflow the pagelayout.phtmlwithin<html>:logged_inif applicablecontroller_$NAMEif applicablefile_$NAMEif applicableMoved to #7616
the PR is still dependent on these changes, and isn't complete without them
Named some elements with IDs innav_menu.phtmlto make them easier selectable in SwageFixes for frss.cssIt wasn't possible to scroll fully to the bottom in aside menu and configure menu on mobileAlign text on expandable sections to the left on mobileShownot-allowedcursor on disabled buttons instead of apointerTested on Chrome, Firefox and GNOME Web