search

piroor / informationaltab

Informational Tab, Provides thumbnail, progress meter, or others to each tab.
http://piro.sakura.ne.jp/xul/informationaltab/
4 stars 5 forks source link

Unread Tabs #28

Open viking2 opened 4 years ago

viking2 commented 4 years ago

There is an option to emphasize unread tabs which then shows the unread tabs with italics. Would it be easy for you to modify this so that it shows italic and red font?

(I am using the legacy TST with Waterfox)

piroor commented 4 years ago

You can apply different appearance for unread tabs with userChrome.css. This addon's CSS declaration for unread tabs is defined at: https://github.com/piroor/informationaltab/blob/c55bc6e347651b168823c995a70a5f5c2f43139a/skin/classic/informationaltab/informationaltab.css#L119-L121

Sorry but I have no motivation to maintain this project anymore because I already migrated to Firefox Quantum. If you seriously need more features, please fork this and extend please.

viking2 commented 4 years ago

I wish that I was able to create forks, but I have no clue how to do this.

In any case, I am a little confused about the userChrome.css vs informationaltab.css.

I unzipped informational_tab-0.5.2017061501-fx.xpi and found the informationaltab.css inside. It is quite different from the one you pointed to (informationaltab/skin/classic/informationaltab/informationaltab.css).

Am I supposed to replace the informationaltab.css inside with the one at informationaltab/skin/classic/informationaltab/informationaltab.css (and add the red font)? Do I then also somehow create a userChrome.css? If so, how do I create it and where do I put it?

p.s. I also need to have a legacy setup for an essential extension that doesn't work in Firefox Quantum.

piroor commented 4 years ago

Did you see https://github.com/piroor/informationaltab/blob/trunk/content/informationaltab/informationaltab.css ? This addon contains two files named "informationaltab.css". 1) under "content": it defines basic behavior, 2) under "skin". CSS files in the "skin" folder is suitable if your changes are mainly about appearance of tabs.

The file "userChrome.css" is a way to apply your own custom style declarations overriding styles of addons without editing addons themselves. "userChrome.css" is easier than editing of addons, but you cannot put any runnable codes to it. https://www.userchrome.org/

Anyway, forking and modifying was my first step of addon development. I hope you successfully help yourself...