301–310 of 536 posts
Earlier quoted context omitted.
I honestly don't remember what the last time was Chrome introduced some cool new feature in Chrome. Maybe the PDF reader?
PWA, WebComponents, File Access, Worklets and Houdini and everything else in HTML5/CSS3 still missing from ChromeOS are all being pushed by Chrome.
Here's hoping. The proliferation of browser standards has made this appear a more daunting task as time has gone by. There was a point where if you built a good DOM, javascript engine, and a layout engine and had a reasonable ability to fetch resources, you could bootstrap a browser. That's how Konquerer got there. But now, I think we're past that point -- if your browser can't do native video conferencing and opengl…
To move Chrome development to some non-commercial "free world" institution. Like UN for example.
That's the only option to have a) security first and b) free browser.
No other options for free browser. Web client stack is so complex that to finance its development it should be a company that gets income from each browser instance installed. How they do that is a rhetoric question I think.
Other browsers need to catch up to Chrome with their development tools. I'd be happy to use Safari or Firefox for development, but... - I can't disable CORS in Firefox (yes, sometimes you have to disable CORS rather than modify the Allow-Origin header response, for example if you need to test against a production backend) (and, no, CORS Everywhere is not a sufficient solution). - I can't inspect WebSocket frames in a…
Other browsers need to catch up to Chrome with their development tools. I'd be happy to use Safari or Firefox for development, but... - I can't disable CORS in Firefox (yes, sometimes you have to disable CORS rather than modify the Allow-Origin header response, for example if you need to test against a production backend) (and, no, CORS Everywhere is not a sufficient solution). - I can't inspect WebSocket frames in a…
Earlier quoted context omitted.
> Chrome's appeal was primarily technical. Each tab got its own process and could crash without taking down the entire browser. Curious, I remember speed being the primary reason. Google invented V8 (the javascript engine), with some pretty decent optimizations and a well-working JIT on i386/amd64 platforms. At the time when chromium came out, it handled some JS-heavy applications very nicely that Firefox struggled w…
I'm surprised there aren't more people on here who moved to chome for the dev tools. That is what moved me over there. Firebug was great in it's day but at some point Chrome's dev tools just became too much better to make staying on Firefox possible.
... years later ...
- A year ago I often used Firefox for its great Canvas debugger. They broke it. I've since forgotten about Firefox.
... 2019 ...
- Microsoft is trying to drive people away from IE, hoping for Edge adoption. I don't care for Firefox. Opera is almost Chrome with extensions. Edge sounds like it wants to be Chrome. Chrome won on most battlefronts. I don't like that fact, because of the "free from corporate greed" reasons mentioned, but it's going to be hard to change the status quo.
Earlier quoted context omitted.
Yup. I'm using Firefox on macOS as well and suffering from the same bug. If you use your Macbook with the resolution set to 'scaled' Firefox absolutely murders your battery. On top of that there's a bug where H264 video doesn't get properly accelerated. Both these bugs have been in Firefox at least since FF62. Both have alternatingly been marked 'priority 2' or 'fix-optional' which is absolutely baffling to me consid…
It isn't a bug; it's the fact that Firefox uses a transparent window and doesn't yet use Core Animation, which offloads scrolling to the window server. Switching to CA involves heavy lifting inside the compositor and is not an easy task. My planeshift crate does some of the work needed to make the WebRender path use Core Animation. In the meantime, setting gfx.compositor.glcontext.opaque to true in about:config helps…
Also, coincidentally, do you know what exactly causes the H264 problem on macOS? I've tried to track it down in bugzilla to no success, but I am 100% sure it is a bug. The energy impact for playing a H264 YouTube video in Safari has an energy impact of ~25. Firefox used to be ~60, but these days its ~180 (!)
> In the meantime, setting gfx.compositor.glcontext.opaque to true in about:config helps battery life significantly, at the cost of rounded corners and vibrancy.
Thanks for this! :)
Earlier quoted context omitted.
PWA, WebComponents, File Access, Worklets and Houdini and everything else in HTML5/CSS3 still missing from ChromeOS are all being pushed by Chrome.
Aside from File Access, I haven't seen any of these. PWA is sometimes mentioned on HN but I've never seen one in the wild (I had to look up the term a few weeks ago). Worklets, WebComponents, and Houdini, I never heard of. I'm not the most in the loop person since I'm not a web developer, but you'd think the cool stuff gets at least mentioned, so going with that, the most recent progressive feature that comes to mind…
Houdini allows for low level control of CSS rendering, basically it allows for creating CSS classes with our own paint methods, and in the process having lower level JavaScript concurrency using less resources than workers.
Earlier quoted context omitted.
I'm surprised there aren't more people on here who moved to chome for the dev tools. That is what moved me over there. Firebug was great in it's day but at some point Chrome's dev tools just became too much better to make staying on Firefox possible.
I vaguely remember all of those things as separate phases. - Moving away from IE, I fell in love with Opera (lots of built-in features), most others with Firefox - Chrome comes in, it's Google, it's lightweight, people try it and like it - Chrome gets really fast, it appeals to even more people - Meanwhile, Firefox has enough extension power to replace Opera for me (who can live with the tabs BELOW address bar or wit…
Lolno, they gave up and are ditching Edge to use Chrome because Electron. https://9to5google.com/2018/12/03/microsoft-chrome-based-bro...