[Suggestion] Comment the CSS Code



  • It would really help people trying to alter the configuration.css code if there were comments in the code noting which section controls which output, etc. For example: [code]// Navigation Buttons[/code] [code]// Search Box[/code] [code]// Scroll Bars[/code] Would the developers consider such?



  • The content of the .css files is actually not the real working version, but a generated+minified one (from Sass or LESS probably).
    So the original stylesheet code is already well commented (at least I hope so :D)
    The publication of the original working file would be much more interesting (imho) instead of just additional comments (which would be not very feasible to add inside the current tool chain).
    This could be done separately in a tech blog or on github.

    There is no real harm in doing so (only modified on individual client), but as always, licensing issues 'might' cause problems.



  • @AlexRuppert:

    The publication of the original working file would be much more interesting (imho) instead of just additional comments (which would be not very feasible to add inside the current tool chain).

    Indeed. It would make it so much easier to find the areas we need to work in to make the changes we want. Would save a lot of time.



  • It probably won't be possible to alter that code in final version at all. So don't expect any help in this regard.
    Don't worry though, customization will be possible in one way or another! ;)



  • @Christoph142:

    It probably won't be possible to alter that code in final version at all. So don't expect any help in this regard.
    Don't worry though, customization will be possible in one way or another! ;)

    Altering is not a good way to go anyway (because it would have to be repeated for each new release).
    I think the idea is more of a documentation, like the old Presto skins, where the complete original skin was available.

    CSS has the nice feature of overriding previous settings if loaded in the appropriate order (one could even use multiple skins together).
    Imho it would be easier to preparse CSS of skins for potential malicious content (like detection of non-local resource links) to avoid vulnerabilities caused by skins, than shutting the whole system down and implementing something (most likely less flexible and not necessarily more secure) on its top.



  • @AlexRuppert:

    Altering is not a good way to go anyway (because it would have to be repeated for each new release). I think the idea is more of a documentation, like the old Presto skins, where the complete original skin was available.

    Indeed altering is not a solution for the reason you mention. I also think most users would not like to dig around in a .css file to make these changes anyway. So if a skinning system was available we would see adventurous people make skins for others to choose from with the result that more people would have choice to customize their browser.



  • @Christoph142:

    It probably won't be possible to alter that code in final version at all. So don't expect any help in this regard.
    Don't worry though, customization will be possible in one way or another! ;)

    I hope the customization we will be able to make will be enough. Three things I did in the .css were tighten the spacing between bookmarks to see more at once, expand the list of visible folders when adding bookmarks, and placed the tabs tight to the top of the screen. These are the types of things I hope we can customize.


Log in to reply
 

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.