Announcement

Collapse
No announcement yet.

Chrome 35 Released With Aura Replacing GTK+

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

  • #21
    Originally posted by cynical View Post
    I'm using an Intel CPU with Intel HD4000 graphics and getting 13-20% cpu usage on 720p HTML5 videos on Chrome 36.0.1985.8 dev. It's hard to say where the issue is on your system with all the components involved in hardware acceleration but it's not an inevitable part of Chrome.
    There's also no noticable performance hit on my on my old Core2Duo while playing 720p HTML5 video, its probably not chrome like cynical already stated.

    Ofcourse it could be the propertary driver :P (just kidding... nvidia's drivers are awesome).

    Comment


    • #22
      Nice, I like it. Finally fixed the font problem in Omnibar. Using the default theme suddenly became viable.

      Originally posted by 0xBADCODE View Post
      blaa blaa blaa Any sane replacements of this horrible bullshit, anyone?
      Epiphany
      Midori
      Rekonq
      Konqueror
      Opera
      Maxthon
      Internet Explorer
      360hao
      inbuilt-browsers of Eclipse and Netbeans
      Emacs browser
      lynx
      elinks
      that QML browser I made one morning

      You have choice. I recommend Epiphany, allows you to create web apps easily.

      Comment


      • #23
        Originally posted by hourwatch View Post
        Looks very ugly in Arch!! At least we still have Firefox
        Looks great here on my Archlinux... much better than before.
        Running with Openbox.

        Comment


        • #24
          Originally posted by tmpdir View Post
          There's also no noticable performance hit on my on my old Core2Duo while playing 720p HTML5 video, its probably not chrome like cynical already stated.

          Ofcourse it could be the propertary driver :P (just kidding... nvidia's drivers are awesome).
          I don't think GPU acceleration works on decoding video in Chrome properly on anything but Intel.

          I'm possibly wrong though.

          Comment


          • #25
            Out here this version fails to start because of SSE2 .

            Comment


            • #26
              Originally posted by Britoid View Post
              I don't think GPU acceleration works on decoding video in Chrome properly on anything but Intel.

              I'm possibly wrong though.

              Easy te check from the chrome adresbar: chrome://gpu

              Edit: do we still have to enable video acceleration manually in chrome? Been a while I configured this machine.
              Last edited by tmpdir; 21 May 2014, 08:12 AM.

              Comment


              • #27
                What about chrome on Wayland?

                Comment


                • #28
                  Originally posted by sp82 View Post
                  What about chrome on Wayland?
                  That's already being worked on but not part of upstream:
                  Wayland implementation for Chromium Ozone classes. Contribute to intel/ozone-wayland development by creating an account on GitHub.


                  I have trouble building this myself to test more recent changes (the chrome/ozone source tree is huge and my machine runs out of memory).

                  There's a new milestone release past due but it looks like there's no binary up yet.

                  You can get binaries for the milestones here:


                  My last experience was with the Valentine release on that page:
                  * the browser works but was not running in a sandbox
                  * you get a few warnings about things that are not working when you launch
                  * the browser window does not allow itself to be resized without using the mouse/keyboard shortcuts provided by weston

                  Chromium was still missing some functionality but it was fast and basically usable to visit webpages. I have high hopes.

                  I would actually rather see Firefox ported but progress on bugzilla seems slow. My understanding is that Firefox basically works on GTK3 now with some rough edges.

                  To be fair to the developers it hardly looks like a simple effort and they have resolved tens of related bugs already toward this porting effort:


                  If you want to take a shot at compiling the chromium browser for wayland (via wayland-ozone) you can find instructions here:
                  Wayland implementation for Chromium Ozone classes. Contribute to intel/ozone-wayland development by creating an account on GitHub.


                  Many of these links have previously appear on this website before. My apologies for reposting them but I figure somebody might find it helpful.

                  Comment


                  • #29
                    Originally posted by paintbynumbers View Post

                    I would actually rather see Firefox ported but progress on bugzilla seems slow. My understanding is that Firefox basically works on GTK3 now with some rough edges.

                    To be fair to the developers it hardly looks like a simple effort and they have resolved tens of related bugs already toward this porting effort:

                    Does GTK3 means a working FF on wayland or we will need more stuff for it?

                    TBH i don't think we'll see FF running on pure WL anytime soon

                    Comment


                    • #30
                      GTK

                      If it doesn't use GTK, why does it link to GTK? And Cairo? They probably just reimplemented the widgets or something like that.

                      Comment

                      Working...
                      X