Flyspray - The bug killer!

  • Status Unconfirmed
  • Percent Complete
    0%
  • Task Type Feature Request
  • Category Backend/Core
  • Assigned To No-one
  • Operating System All
  • Severity Low
  • Priority Very Low
  • Reported Version 1.0 devel (github master)
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Flyspray - The bug killer!
Opened by Florian Jäcksch - 20.02.2017

FS#2346 - Custom css inheritance

If i set up a custom css in the main FS settings the style doesn’t get applied to all nested projects. I have to set the css to all projects explicitly to get the stylings work on all project pages.
Wouldn’t it be a good idea to first load the css set in the main dialog and after that load an additional css specified in the sub project? Then it would be possible to specify general stylings for all projects and project based stylings also.

Project Manager
peterdd commented on 23.02.2017 11:55

How many flyspray projects do you have?

You could load a custom_global.css with

@import url('custom_global.css');

in your custom_p1.css, custom_p2.css, ..

So the custom_all.css css rules are applied after theme.css, but before 'custom_px.css' rules.

This way you have the freedom to ignore a 'custom_global.css' in a 'custom_specialextraproject.css' theme.

Florian Jäcksch commented on 23.02.2017 12:17

I use it on different companies and one company has about 30-40 projects in it and we updated a few days ago to the latest version. I told them that they must set the custom css on each project and that is quite a bit of work ;)
And for new projects they must remember to set this each time to keep the settings.

Maybe an own theme would be the better solution but there are only small changes and upcoming updates (to the main theme) will be applied with additional work on our side.

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing