SM 2.35 end of May?

[patrickjdempsey]

I'm splitting from this convo because it's getting pretty far off topic now:
viewtopic.php?f=3&t=2920331&start=60

I'm trying to put together a picture of what the next SM release is going to look like here. According to the last meeting log, it looks like folks are hopeful about the possibility of a 2.35 release to coincide with the release of Thunderbird 38 near the end of the month: http://logs.glob.uno/?c=mozilla%23seamo ... 2+May+2015

Features and fixes-wise, here are the fixed bugs for 2.34:
https://bugzilla.mozilla.org/buglist.cg ... monkey2.34

And 2.35:
https://bugzilla.mozilla.org/buglist.cg ... monkey2.35

Highlights:

- Findbar status messages should now work again.
- Quickfind should now automatically invoke Findbar again.
- Search suggestions for DuckDuckGo.
- Printing from Composer should be fixed now.
- Addressbook birthdays storing wrong fixed.
- Bookmarks menu now offers Open in Private Window.

Anything else we should know about? Any home builders (barbaz?) have any input about extension or theme issues that might need to be rectified? I suppose extensions and theme authors should probably go ahead and visit AMO and bump version compatibility via Manage Status and Versions.

[barbaz]

I don't use SeaMonkey 2.35, and was actually planning to skip that cycle if SeaMonkey project cancelled that release..

But I can say that the transition to SeaMonkey 2.34 was pretty smooth, I don't recall needing to do anything extensions-wise for that. And in my experiences with SeaMonkey 2.37a1, all I had to do extensions-wise (as far as I noticed) was fix the findbar on my Adblock Plus fork - but then again, who knows what bugs popped up after 2.34 and were fixed by 2.37a1...

Anyone actually used 2.35 at this point?

[patrickjdempsey]

Ok. Thanks. For some reason I thought you said you had built 2.35.

[Anonymosity]

What does "After Bug 1066383 the navigator context menu is huge" mean? Is that referring to the context menu for a web page? How big is huge? The context menu for this page does not look huge to me - it looks normal.

[patrickjdempsey]

Context menus include every possible item in one big long list and there is a function that is used to restrict that list down based on the specific click-case. (Right-click on a document page, an image, and a textbox input to see what I mean). In bug 1066383 Mozilla changed the name of the function that restricts that list (as well as it's implementation to support e10s) which undoubtedly caused SM context menus to be just one big long list. I can see this possibly breaking extensions as well. Hmm.

[barbaz]

I don't use SeaMonkey 2.35, and was actually planning to skip that cycle if SeaMonkey project cancelled that release..

Not necessarily true anymore... The reason I said that is because when I looked there was no Firefox 38 release tagged, and it seemed that Firefox was going to push 38.0.5 as a "special" release and the first Firefox 38.x release, with crap features that I didn't want anything to do with (although it seems from what I looked at that those were limited to browser/ but I didn't want to mess with it).

Anyway, back on topic, I tried to build SeaMonkey based on Gecko 38.0.1 (cset FIREFOX_38_0_1_RELEASE) for Linux x86_64, but unfortunately it does not build.

[barbaz]

Anyway, back on topic, I tried to build SeaMonkey based on Gecko 38.0.1 (cset FIREFOX_38_0_1_RELEASE) for Linux x86_64, but unfortunately it does not build.

The problem is client.py is updating to the wrong revision of DOM Inspector. This got it to build:

Code: Select all

cd comm-release/mozilla/extensions/inspector
hg update -C -r b2005ebad365

Off to go evaluate 2.35

[barbaz]

No obvious problems yet...

@patrickjdempsey: anything specific you'd like me to check while I have this up?

[patrickjdempsey]

It sounds like everything is working as expected... you might try testing a few popular themes as especially on Linux there can be theme-related issues. I don't think any of the common breakages in the last few versions of Firefox apply to SeaMonkey.

[barbaz]

you might try testing a few popular themes as especially on Linux there can be theme-related issues.

Seemingly nothing major wrong, but there might be some minor issues...

Tried "EarlyBlue 2.33" and "Metal Lion Silver SeaMonkey 2.0.3.0". Both work, with one problem common to both - the theme's vertical scrollbars lack a "scroll up" button, it's just the scrollbar and the scroll down button. No related messages in the Error Console.
(FWIW my system theme has no scroll buttons on the scroll bar...)

Otherwise, no problems with themes AFAICT.

[patrickjdempsey]

Yeah I don't think Firefox themes with custom scrollbars are compatible with that Linux configuration. There's also issues with some of the exotic scrollbars in OSX. Custom scrollbars are one of those things that was solidly broken about 5 years ago due to changes in both Firefox development and in various OS platforms.

[Anonymosity]

Yeah I don't think Firefox themes with custom scrollbars are compatible with that Linux configuration. There's also issues with some of the exotic scrollbars in OSX. Custom scrollbars are one of those things that was solidly broken about 5 years ago due to changes in both Firefox development and in various OS platforms.

Which exotic scrolllbars for Mac OS? Which themes? The only themes where I saw a problem with scrollbars with SeaMonkey on Mac OS were Early Blue and LCARSTrek, where the bottom scroll button is missing. The problem is minor and easily fixed by commenting out a certain section of code in scrollbar.css.

[patrickjdempsey]

There are only a handful of themes that still use custom scrollbars, most of them based on Modern. Most developers abandoned them when Mozilla kept breaking them back in 3.6 days. OSX introduced iOS-style scroll bars that are thin and disappear onto the desktop a few years ago. Windows has copied, so now there are similar ones in modern versions of Windows as well.

Edit: You are apparently using a version of OSX from before the introduction of weird scrollbars: "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:36.0) Gecko/20100101 Firefox/36.0 SeaMonkey/2.33.1"
https://bugzilla.mozilla.org/show_bug.cgi?id=636564

[barbaz]

Well, there are no issues on Linux... but on Mac OS X, Flash player (17.0.0.134) no longer responds to keyboard input, and atm I don't see any workaround other than downgrading SeaMonkey...
Judging from the Flash changelog, updating Flash probably won't help...

[patrickjdempsey]

Other than pressing space bar to pause/play video (which only works on a handful of websites) I don't think I've ever used the keyboard with Flash. But I also never play games online, so yeah.