Skip to content

CSS fixes for Swage#7608

Merged
Alkarex merged 29 commits intoFreshRSS:edgefrom
Inverle:swage-css-fixes
Sep 1, 2025
Merged

CSS fixes for Swage#7608
Alkarex merged 29 commits intoFreshRSS:edgefrom
Inverle:swage-css-fixes

Conversation

@Inverle
Copy link
Member

@Inverle Inverle commented May 23, 2025

  • Fixes for Swage
    • Buttons not showing correctly [Bug] Sort button with Swage disappears on small screen #7465
    • Dropdown placement (some dropdowns couldn't fit in viewport)
    • Icons not appearing in some places due to color i.e. label management and subscription management page
    • Made .form-group and button inside search dropdown hover colors slightly darker, for better visibility
    • Nav menu style improvements on mobile
      • Smaller if not on main page
      • Align settings icon on configuration pages to the right
      • Support nav menu for feed statistics page
    • Text alignment in search dropdown
    • Ensure input, select, textarea don't overflow the page
    • Login link placement in anonymous view
    • Other fixes for
      • Add via bookmarklet page
      • About page
      • Shared HTML query page
      • Register page
    • Text visibility for debug log
  • Provide classes layout.phtml within <html>:
    • logged_in if applicable
    • controller_$NAME if applicable
    • file_$NAME if applicable
  • Some other fixes

Moved to #7616

the PR is still dependent on these changes, and isn't complete without them

  • Named some elements with IDs in nav_menu.phtml to make them easier selectable in Swage
  • Fixes for frss.css
    • It wasn't possible to scroll fully to the bottom in aside menu and configure menu on mobile
    • Align text on expandable sections to the left on mobile
    • Show not-allowed cursor on disabled buttons instead of a pointer

Tested on Chrome, Firefox and GNOME Web

@Inverle
Copy link
Member Author

Inverle commented May 23, 2025

QuickCollapse button for example is still broken though, but only on mobile

@Alkarex Alkarex added this to the 1.27.0 milestone May 23, 2025
@Alkarex
Copy link
Member

Alkarex commented May 23, 2025

For Swage, the changes need to be done in https://github.com/FreshRSS/FreshRSS/blob/edge/p/themes/Swage/swage.scss
and then run:

sass swage.scss:swage.css

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.

@Alkarex Alkarex linked an issue May 23, 2025 that may be closed by this pull request
@Alkarex Alkarex added UI 🎨 User Interfaces Theme 🖌 labels May 23, 2025
@Alkarex Alkarex modified the milestones: 1.27.0, 1.26.3 May 23, 2025
@Inverle
Copy link
Member Author

Inverle commented May 23, 2025

make dropdowns full width on mobile

turns out I didn't fix them correctly

Comment on lines -2 to -6
--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;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please check the text indentation and respect the given.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure why that happened

Comment on lines +11 to +15
--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;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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:

.form-group {
padding: 5px;
border: 1px solid transparent;
&:hover {
background-color: var(--color-background-light);
border: 1px solid var(--color-border-light);
}

I think it's fine as is though.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Inverle
Copy link
Member Author

Inverle commented May 24, 2025

I broke the actualize button from appearing after moving changes from css to scss, so I'll have to fix that too.

@Inverle Inverle requested a review from math-GH May 24, 2025 12:56
@Inverle
Copy link
Member Author

Inverle commented May 24, 2025

todo:

  • sign in button is incorrectly positioned on anonymous view
  • the search is hidden for some reason (on anonymous view)
  • about page is broken
  • add feed via bookmarklet page is broken

@math-GH
Copy link
Contributor

math-GH commented May 24, 2025

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

@Inverle Inverle mentioned this pull request May 25, 2025
@Inverle
Copy link
Member Author

Inverle commented May 25, 2025

to be honest: this PR blewed up to much more than just CSS fixes for Swage.

Yes.

  • Fixes for Swage
  • Fixes for frss.css that also affect Swage
  • Added necessary ids and class names in layout.phtml and nav_menu.phtml to use them in Swage
    • also moved an if block in nav_menu.phtml

I would suggest to split the PR and keep the focus here on Swage

Which parts?

@math-GH
Copy link
Contributor

math-GH commented May 25, 2025

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:

* Provide `logged_in` class within `<html>` if applicable, and a controller class

* Fixes for frss.css
  
  * It wasn't possible to scroll fully to the bottom in aside menu and configure menu on mobile
  * Align text on expandable sections to the left on mobile
  * Show `not-allowed` cursor on disabled buttons instead of a `pointer`

* Some other fixes

* Made more navigation buttons accessible within anonymous view

@Inverle
Copy link
Member Author

Inverle commented May 25, 2025

  • Provide logged_in class within <html> if applicable, and a controller class

It doesn't look like any other themes aside from Swage can benefit from those changes

  • Fixes for frss.css

I guess this does affect all themes, not just Swage

  • Some other fixes

Those are just for Swage (adding borders, margins and paddings in some places)

  • Made more navigation buttons accessible within anonymous view

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 bookmark current query button inside the user queries dropdown)

Before:

image

After (still have to make user queries visible):

image

@Inverle Inverle mentioned this pull request May 25, 2025
@Inverle Inverle changed the title CSS fixes for Swage + some in frss.css CSS fixes for Swage May 25, 2025
@Inverle
Copy link
Member Author

Inverle commented May 25, 2025

Done #7616

@Inverle
Copy link
Member Author

Inverle commented Aug 14, 2025

Anonymous view when more buttons were shown (mobile view)
image
Now:
image
A little empty

@Inverle Inverle marked this pull request as ready for review August 14, 2025 23:30
@Alkarex Alkarex modified the milestones: 1.27.0, 1.28.0 Aug 15, 2025
@Inverle
Copy link
Member Author

Inverle commented Aug 15, 2025

I consider it ready but testing welcome

@Alkarex
Copy link
Member

Alkarex commented Aug 15, 2025

Yes, I would like to take time to look a bit closer to the changes in layout.phtml but would first like to release FreshRSS 1.27.0.
This PR can land in a minor 1.27.1 or whichever is the next release.

@Inverle
Copy link
Member Author

Inverle commented Aug 15, 2025

Yes, I would like to take time to look a bit closer to the changes in layout.phtml

I did just find one issue, fixing it right now

@Inverle
Copy link
Member Author

Inverle commented Aug 15, 2025

Resolves the same x dropdown-menu issue as in #7722 (tested with darkMode field from user config)

@Inverle
Copy link
Member Author

Inverle commented Aug 15, 2025

What's the specific concern with layout.phtml?
@Alkarex

@math-GH
Copy link
Contributor

math-GH commented Aug 28, 2025

It looks now ok for me.

@Alkarex
Copy link
Member

Alkarex commented Sep 1, 2025

The SCSS annoyances will vanish when we get to implement:

@Alkarex Alkarex merged commit 335adda into FreshRSS:edge Sep 1, 2025
1 check passed
@Inverle Inverle deleted the swage-css-fixes branch September 2, 2025 04:48
@Alkarex Alkarex modified the milestones: 1.28.0, 1.27.1 Sep 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Theme 🖌 UI 🎨 User Interfaces

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Sort button with Swage disappears on small screen

3 participants