Currently css patches have comments above them that describe what that particular patch fixes or changes. This has been fine in the past but now since there are a lot of users of Caprine, Facebook is changing the design every day, introducing some new bugs to css and fixing some old ones, it's getting harder to follow what patches actually fix. Also the actual text for the comment has been the responsibility of the contributor so there is basically a different description/naming convention for almost every patch.
I'm proposing that this be standardized in some way. First, the comment needs to show the information about the location of the target of the patch (Left Sidebar
(the vertical tabs bar on the new design), Chats list
, Peoples list
, Marketplace list
, Requests list
, Archived list
, Community List
(all these lists are actually views for tabs in the left sidebar), Message list
(the list of messages in the selected chat, aka. message view), Chat titlebar
(titlebar containing users avatars, chat title and chat buttons on the right side), Chat bottom bar
(bottom bar containing message entry field, send button and other insert buttons), Right sidebar
, modals for specific functionalities...
That way it would be easier to follow what specific patch fixes and it would be much easier to find whether there are already some existing patches for related elements (so they could be fixed by one unified more general patch). With the naming convention, there would be also a strict placement convention, where in the file should be the patch places so they are written in some specific order. That would also contribute to finding patches more easily.
This thread could be used as a place for discussion of this.
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
You're funding impactful open source efforts
You want to contribute to this effort
You want to get funding like this too