3 ms·

There is always Qupzilla[1], which is just Qt Web Engine with good Qt UI wrappings. I believe webrtc and even widevine works with it. [1]http://www.qupzilla.c

by zanny 10y ago

There is always Qupzilla[1], which is just Qt Web Engine with good Qt UI wrappings. I believe webrtc and even widevine works with it. [1]http://www.qupzilla.com/ http://www.qupzilla.com/ Its basically just pretty Chrome through Qt.

kuschku 10y ago
Except, it still doesn’t provide a UI customizable with CSS, HTML + JS, doesn’t run firefox addons, and is generally inferior. Sadly, it looks like Firefox will soon not do either of those things anymore.
- zanny 10y ago
  Its a Qt app. Why would you ever want to edit its UI with CSS? Its UI is controlled by the Qt widget and color themes. While its not a Qt specific feature, KDE applications let you drag and drop pretty much every element of every applications interface wherever you want and however you want. While it doesn't have an app ecosystem, it has an extensions API and they have already ported adblock and greasemonkey over. The amount of insane work required to make it work with either Firefox or Chrome extensions, none of which were meant to operate outside the UI architecture of their host environments, cannot be reasonably considered a major flaw. A disadvantage, but it is the cost of using a native UI toolkit instead of writing your own from scratch like Firefox / Chromium do.
  - kuschku 10y ago
    Well, because I want Firefox addons, because I want to be able to add tab previews just with an addon, or redesign the entire UI with an addon, or have tree style tabs. I want to be able to write an addon integrating with a custom server for storage of browser history, or an addon that allows me to tag history entries. I want to be able to add entire websites in iframes to the UI – for example, as small windows floating in the bottom containing an audio player widget. That’s why I use Firefox in the first place. Sadly, half of its UI is unusable thanks to GTK.

by zanny 10y ago

kuschku 10y ago

Except, it still doesn’t provide a UI customizable with CSS, HTML + JS, doesn’t run firefox addons, and is generally inferior. Sadly, it looks like Firefox will soon not do either of those things anymore.

zanny 10y ago
Its a Qt app. Why would you ever want to edit its UI with CSS? Its UI is controlled by the Qt widget and color themes. While its not a Qt specific feature, KDE applications let you drag and drop pretty much every element of every applications interface wherever you want and however you want. While it doesn't have an app ecosystem, it has an extensions API and they have already ported adblock and greasemonkey over. The amount of insane work required to make it work with either Firefox or Chrome extensions, none of which were meant to operate outside the UI architecture of their host environments, cannot be reasonably considered a major flaw. A disadvantage, but it is the cost of using a native UI toolkit instead of writing your own from scratch like Firefox / Chromium do.
- kuschku 10y ago
  Well, because I want Firefox addons, because I want to be able to add tab previews just with an addon, or redesign the entire UI with an addon, or have tree style tabs. I want to be able to write an addon integrating with a custom server for storage of browser history, or an addon that allows me to tag history entries. I want to be able to add entire websites in iframes to the UI – for example, as small windows floating in the bottom containing an audio player widget. That’s why I use Firefox in the first place. Sadly, half of its UI is unusable thanks to GTK.