SeaFox - Development

[Exalm]

Code: Select all

/* fix skinny alltabs button */
.tabs-alltabs-button > .toolbarbutton-menu-dropmarker {
  margin: 4px;
}


This thing works bad on Linux. The problem is that Linux theme uses native button appearance AND native dropmarker appearance. They both are pretty thick, so that margin makes the button stretch the whole tab bar.
Reverting that:

Code: Select all

@namespace url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul);

.tabs-alltabs-button > .toolbarbutton-menu-dropmarker {
  margin: 0px;
}

it looks just fine.

See yourself:

Note that I have a pretty compact GTK (system) theme here. It may be even worse with some.

[patrickjdempsey]

Thanks. On Windows there is no padding applied by default so it makes the dropmarker too tiny to hit. I'm honestly somewhat reeling over recent news regarding the future of Gecko products and am not sure what I am going to be doing.

[Frank Lion]

I noticed that, but assumed that the default theme was meant to look like that.

Don't forget you've got by default a 45px Nav Bar directly above the Tab Bar, which is 39px with that bug. So, it's not like it's that out of keeping with the general large look of default.

[patrickjdempsey]

Looks like 2.35 breaks the combined back/forward dropmarker. I'm going to the beach on Thursday and I'm *very* busy working on putting together a friend's new Lebanese restaurant, so I'm not sure when I'm going to have time to look into it let alone work on a fix.

[Frank Lion]

Ah, the old 'Renovating the Lebanese Restaurant' excuse, eh? Always a good one that, used it myself a good few times.

[patrickjdempsey]

A beautiful woman offered me "free shwarama forever". What's a fella supposed to do?

[LoudNoise]

Oh, I have made taboon in about eight years.

[malliz]

. I'm going to the beach on Thursday and I'm *very* busy working on putting together a friend's new Lebanese restaurant,

Did they get the kit from Ikea ?

[patrickjdempsey]

Nah, just throwing some paint around:
http://s16.photobucket.com/user/patrick ... n.jpg.html

So far I have two issues with the current 2.38 version of SeaMonkey. The Findbar is borked, as is the back/forward history drop menu. I do have errors for them:

Error: TypeError: this._browser.messageManager.sendAsyncMessage is not a function
Source File: chrome://global/content/bindings/findbar.xml

Error: NotFoundError: Node was not found
Source File: chrome://navigator/content/sessionHistoryUI.js

If anyone else notices any strange errors in the Error Console or weird behavior let me know.

[patrickjdempsey]

Looks like the Addons Manager is borked again. Didn't we JUST do this crap?

Edit: I guess the way the style started isn't the way it finished. Not sure how to progress on this ATM. Most likely the next version of SeaFox will have a minimum cutoff at SM 2.38 so as to not break older versions.

[patrickjdempsey]

Crap, and I still don't have a simple way to unpack omni.ja on this machine yet. Win 7 File Explorer will do it, but it's roundabout.

[patrickjdempsey]

So fixing the findbar was so stupid easy that the development gods have cursed me with the mystery of the back/forward dropmarker. All I'm doing is using the exact same function that SM already uses to populate the Go (history) menu on the menubar. But apparently something changed in that function and one of two things is happening: either the function is failing altogether so the menu is not populating, or the cleanup function that deletes old entries is overactive and destroying it. I'm sad because this worked great before 2.35.

[patrickjdempsey]

Quick fix for Findbar and Addons Manager in SM 2.38:
https://addons.mozilla.org/en-us/seamon ... sion-0.4.4

[patrickjdempsey]

Hmm. Now I'm seeing the toolbar grippies as Frank mentioned. It looks like my global.css file has not been loaded at all this session because the Findbar is showing the Firefox style and the Download manager is reverted as well. Hmmm. Opening a new window does not cause any clues to appear in the Error Console. It seems like the chrome.manifest is failing somehow.

[patrickjdempsey]

I'm almost 100% positive that AdBlock Plus is the cause of the global.css not loading. Have heard reports of the newest version breaking other extensions as well. And Mozilla thinks hacky crap like this is the future.