elinks doesn't require libX11 (unlike links2),
and webclient can become e.g. rekonq pulling
in kde4libs -- that's exactly what I ran into
while preparing 201612xx server starterkits.

...as suggested for the next starterkits since
seamonkey 2.40 is officially full of security bugs
and there's no 2.46 (or whatever stable/plugged)
release available despite the plans:

https://wiki.mozilla.org/SeaMonkey:Home_Page
https://forum.altlinux.org/index.php?topic=37268

There's no more 1.7.0 browser plugin package in sisyphus,
move on to 1.8.0...

These packages have been suggested by mvk@ to enable H.264 support
when no flash plugin is shipped (most likely for security reasons).

...and Sun JDK to OpenJDK (thx cas@).

The issue with this was that plain use/browser/firefox/esr
didn't actually pull in the feature as such; it MUST NOT
pull in use/browser/firefox since it will change semantics
from "if it's Firefox make it ESR" to outright "use FX ESR"
(starterkits depend on the former and it was intentional).

FX_FLAVOUR variable can be set anywhere to switch
use/browser/firefox to prefer ESR packages, including
the appropriate localization ones.

Note that there's no dependency as it can be set in e.g.
starterkits (still unset in regular builds) wholesale
but shouldn't affect those of them lacking firefox.

The current branches lack both firefox 29+ and
firefox-classic_theme_restorer, correspondingly;
sisyphus has those; the feature shouldn't pose
any problems in both cases, should it?

This one has been asking to be implemented for too long already,
and zerg@ was interested in a bit more lean and mean regular-kde4
either (there are two browsers provided with it via metapackage).

There's another reason to do it recently: Firefox Australis UI
is not exactly the best for many of us, and good ol' seamonkey
seems preferable for "vintage"/low-resource images coming with
icewm or windowmaker.