-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generalize title customization code for all supported applications #20
Comments
I have a question about that: "supported applications." Currently only FF and TB is supported by the title customization feature, but some others by NTT. |
With supported applications I mean any application which is listed in our install.rdf. It shouldn't be that hard to add titlebar customization for those later on. |
I'm not sure about that. Of course titlebar customization support for Songbird could be easier than Seamonkey, but I never digged myself into that. |
Tried out title customization with Songbird. After filing that issue, this should depend on it, if You want SB covered by this issue. SM support still needs another issue. Due it's nature. IMHO. |
Thanks @xabolcs for looking into it and sorry for the late reply, but I'm still out of office and check my mail infrequently. So I would say lets start with Firefox and Thunderbird and apply the implementation to SeaMonkey and Songbird later, whenever they will get the title modification code. |
I can't say it right out of my head. But we should check for the entry points like:
|
whimboo wrote:
Would You like to give an examle? |
Leave "${Something}" untouched if nightly.variables doesn't have such property, and let it be "Undefined" if it's a known variable, but currently unavailable. For example in the "${Changeset}" case, when application.ini doesn't always contain a "SourceStamp" key.
This we basically got for free with the rewrite of the extension based on the WebExtension API. |
The code to modify the title bar with the custom title differs between each supported application. We should generalize it so that the methods look like the same but only access different elements to retrieve/set the necessary data.
The text was updated successfully, but these errors were encountered: