Announcement

Collapse
No announcement yet.

GTK3 Version Of Firefox Up For Fedora Testing

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • IsacDaavid
    replied
    What? Are people still using Flash?

    Leave a comment:


  • LLStarks
    replied
    Originally posted by oleid View Post
    I think it more has to do with Flash being linked to GTK2; currently it is not possible to use GTK2 and GTK3 in the same process, thus Flash won't work with a GTK3 built of firefox where the plugin lives in the same process as the browser gui.

    https://bugzilla.mozilla.org/show_bug.cgi?id=624422
    https://bugzilla.mozilla.org/show_bu...id=627699#c275
    And the Firefox devs still have the nerve to refuse implementing PPAPI (Pepper) to replace NPAPI plugins

    Leave a comment:


  • Delgarde
    replied
    Originally posted by oleid View Post
    AFAIR it's not only porting to GTK3, it's also removing (or better: isolating) direct X11 dependencies to allow the port to Wayland.
    Yeah, that's my understanding too. They could have done the port in two pieces - a quick-and-dirty port to Gtk3 but still featuring all the deprecated stuff tied to X11, then a cleanup that allows them to support Wayland - but they've chosen to combine them. And as usual, "do it right" takes longer...

    Leave a comment:


  • gufide
    replied
    Originally posted by oleid View Post
    Must be some broken KDE integration, possibly distribution specific, Firefox looks fine here, too ([email protected])
    Firefox widgets don't have alpha, so it cannot have rounded borders.

    Leave a comment:


  • oleid
    replied
    Originally posted by GreatEmerald View Post
    The Flash right-click looks fine, yes. It's the non-Flash Firefox right-clicks that are square. And I'm using KDE, with the oxygen theme for GTK2.
    Must be some broken KDE integration, possibly distribution specific, Firefox looks fine here, too ([email protected])

    Leave a comment:


  • GreatEmerald
    replied
    Originally posted by Daktyl198 View Post
    It could be because I'm using Nightly (version 29 currently) with the Australis interface, but I have no trouble at all with Firefox integrating with my GTK theme. Heck, even the flash right-click looks completely integrated... it looks no different from any other right-click in my DE (Cinnamon 2)
    The Flash right-click looks fine, yes. It's the non-Flash Firefox right-clicks that are square. And I'm using KDE, with the oxygen theme for GTK2.

    Leave a comment:


  • zxy_thf
    replied
    Originally posted by Daktyl198 View Post
    I could-of swore plugin-container was already a separate process... *shrug*

    At this point, I'd go for a Qt-based Firefox if it meant faster porting to newer versions :/
    (btw, what versions of Qt does flash support?)
    You still need Gtk2 because the shitty old Flash needs it

    Leave a comment:


  • Krejzi
    replied
    Originally posted by Daktyl198 View Post
    I could-of swore plugin-container was already a separate process... *shrug*

    At this point, I'd go for a Qt-based Firefox if it meant faster porting to newer versions :/
    (btw, what versions of Qt does flash support?)
    IIRC, Epiphany, the GNOME Web Browser had the same issue that Mozilla has now - flash player couldn't be loaded. The solution was WebKit2 seperate plugin process architecture, where they link plugin process to GTK+2 and libXt and library in some way gets what is necessarry from the web process itself. But still, that wouldn't work on Wayland, at least not without XWayland because of directy dependency on libXwhatever and libgdk-2.0-x11

    As for Firefox, plugin-container is indeed a split process, but it currently uses the same library the browser does - libxul.so. They would need:

    a) to both link to gtk+2 and gtk+3, in order for plugin container to work correctly (which is impossible because of reasons mentioned above)
    b) to rewrite plugin-container to be a standalone binary, without any dependency on libxul.so
    Last edited by Krejzi; 13 January 2014, 05:15 PM.

    Leave a comment:


  • kdekorte
    replied
    [QUOTE=oleid;388742]I think it more has to do with Flash being linked to GTK2; currently it is not possible to use GTK2 and GTK3 in the same process, thus Flash won't work with a GTK3 built of firefox where the plugin lives in the same process as the browser gui.

    Had this same problem with mplayerplug-in when Firefox was transitioning from GTK1 to GTK2. I had to have a bunch of code in configure to try and figure out which GTK to use or to just use X11 code. I was a total pain and then there were problems with reusing the binary in other browsers on the same machine, because those other browsers might be using GTK1 while Firefox was using GTK2.

    When I developed gecko-mediaplayer, the replacement for mplayerplug-in, I made sure not to use any GTK code in the plugin so this kinda stuff would not happen again.

    Leave a comment:


  • Daktyl198
    replied
    Originally posted by GreatEmerald View Post
    Huh, now that you said it, I see that the menus I get when right-clicking on a Flash applet and when right-clicking elsewhere are different... That also shows just how poorly Firefox integrates with themes at the moment.
    It could be because I'm using Nightly (version 29 currently) with the Australis interface, but I have no trouble at all with Firefox integrating with my GTK theme. Heck, even the flash right-click looks completely integrated... it looks no different from any other right-click in my DE (Cinnamon 2)

    Currently, the only trouble I have with Firefox "integrating" with my theme is that the theme uses a combination of light and dark colors, the dark taking over the tab section of Firefox. If I want to move a button (Like Home or Downloads) into the tab bar, they become really hard to see because they don't change from their own dark-grey color.
    But that's not Firefox's fault, really.

    Leave a comment:

Working...
X