-
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
Add basic Seamonkey support to titlebar customization #31
Comments
Sounds fair enough. Code should be window type specific and we should take care of in #20 as well. |
@tonymec noted again that NTT doesn't support SeaMonkey:
Phillip Chee's commit does the most of work with SeaMonkey's main window. @tonymec (as SM and NTT user) (and also @whimboo) do You agree with |
On 22/10/12 22:37, Szabolcs Hubai wrote:
IMHO, titlebar customization only in the browser is better than none. So my take on this question is: if you can do browser window title Best regards, Tony.MESKIMEN'S LAW |
@whimboo, @tonymec |
If we get the remaining issue fixed which @tonymec is facing, I would be happy to include it. |
@tonymec's issue is not just his issue as You can read in the related pull request (#104). |
Opps, wrong number. |
If that's the case we can go ahead with pull #104 once I got the confirmation from tony. |
That would be fine! :) |
@whimboo Which confirmation? Do you want me to test some advance build? Normally I pull the "mozilla" master on my local clone (I refrained recently because it had no titlebat customization and I had a "test xpi" which fixed that, well, except for that "known issue"), but I can test any xpi if I know exactly which one. |
@tonymec: check #104! (specifically |
- aBroswer -> call(gBrowser) + this - getWindowTitleForNavigator jsdoc description - docShell.contentViewer jsdoc TODO - not polluting with Logger.jsm
@xabolcs thank you for the patch! Good to see that this feature has been landed now. |
Edited description:
|
@tonymec and I talked a little bit on mozillaZine about how to support Seamonkey.
It isn't trivial. SM has got two window types, at least. :)
Depends on #20 - wait for it's "output", and reuse from modules as much as possible.This issue was modified to contain BASIC titlebar customization only!
It overlays
chrome://navigator/content/navigator.xul
only!The text was updated successfully, but these errors were encountered: