Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox 68.0

mozilla.org

Post reply on HN
Print view View original

41–50 of 282 posts

Re: Firefox 68.0

#41

Post by lucideer »

zubspace wrote: post #16

1) Regarding WebRender: Maybe I'm a bit out of the loop, but aren't they working on Servo? It seems, WebRender is a Gecko thing. I'm confused. 2) I'm also confused about the state of Gecko Embedding. As far as I know many are jumping to Chromium instead of Gecko. What's the plan there? Is Chromium better/easier to embed? Will I be able to embed Servo at some point?

Servo is an experimental browser project to explore ideas/techniques: it's never been intended to be a replacement for/embedded into Firefox.

What was planned and is happening is that a lot of the exploratory work happening on Servo is being integrated into Firefox in parallel. WebRender is one example of this work: it's (effectively) a Servo component that is now in Firefox.

Another example of the above is Stylo/QuantumCSS, Servo's CSS component. This post on Stylo/QuantumCSS gives a good early insight into the overall project to bring these components to Firefox https://hacks.mozilla.org/2017/08/inside-a-super-fast-css-en...

> many are jumping to Chromium instead of Gecko. What's the plan there? Is Chromium better/easier to embed? Will I be able to embed Servo at some point?

- Chromium is much easier to embed than Gecko

- Servo can be embedded now (and uses the same/a similar system to Chromium), but as mentioned above, Servo as a whole isn't stable.

- Making Gecko/Firefox easy to embed would be great, but at this stage I think this is largely a matter of focus, resources, priorities.

- On a related note, there is the GeckoView[0] which is a project to build an easily-embeddable Firefox for Android

[0] https://github.com/mozilla/geckoview

Re: Firefox 68.0

#42

Post by helb »

Santosh83 wrote: post #22
gjm11 wrote: post #14

Earlier quoted context omitted.

> Windows 10 users with AMD graphics cards It may be worth noting that WebRender was already deployed to Win10/Nvidia users in Firefox 67.

Will it also eventually roll out for those with Intel Integrated Graphics?

Eventually… https://bugzilla.mozilla.org/show_bug.cgi?id=1479781

You can enable/disable webrender in about:config if you want to try it out (gfx.webrender.all). I've switched to it on my laptop (HD Graphics 620, Gentoo Linux). So far so good.

Re: Firefox 68.0

#43

Post by the_duke »

Santosh83 wrote: post #22
gjm11 wrote: post #14

Earlier quoted context omitted.

> Windows 10 users with AMD graphics cards It may be worth noting that WebRender was already deployed to Win10/Nvidia users in Firefox 67.

Will it also eventually roll out for those with Intel Integrated Graphics?

Webrender will by the default everywhere ... eventually.

Mozilla is just using a conservative, staged rollout to limit the impact of bugs.

Re: Firefox 68.0

#45

Post by kpcyrd »

ceezuns wrote: post #2

"Dark mode in reader view expands so that windows are also dark on the controls, sidebars and toolbars." Thank god.

Is there an about:config setting to force this, for example for i3 users?

Re: Firefox 68.0

#46

Post by kijin »

bzbarsky wrote: post #37
Wehrdo wrote: post #18

Earlier quoted context omitted.

For what it's worth, I'm still able to open and use Doxygen HTML docs without running a web server. Looks like it loads both CSS and JS. So I'm not sure what the changenote actually means.

The changenote is talking about access from script. Script running in a page loaded from file:// will not be able to access the DOM or text of any other file:// URLs, other than the one it's running in.

That makes sense, because so much security nowadays depends on keeping origins separate. It's hard to tell whether any given file:// URL belongs in the same origin as another file:// URL. Better treat each file:// URL as its own origin.

Re: Firefox 68.0

#47

Post by kevin_b_er »

This marks the last Android release with extensions/add-on support. There will not be a 69 release of this edition of Firefox for Android ("Fennec").

The new remake of the mobile browser ("Fenix") does not have extensions support and it is on an indefinite and easily ignorable backlog. It is explicitly not being worked on this quarter. At the end of this quarter is the scheduled release of Firefox 69. Unless there's no release at all of Firefox 69 upon the Android platform, that's the time when Mozilla I think will deceptively try to drop support for extensions/addons on android.

Bug to have Add-ons pages declare Fenix extensions as unsupported. "version = 68.0.99 is Fenix (or some other GeckoView-powered browser)" https://bugzilla.mozilla.org/show_bug.cgi?id=1548428

"Or do nothing because Fennec 68 and Fenix 68 will overlap for only 6–8 weeks with a preview audience." https://github.com/mozilla/addons-frontend/issues/7963

Firefox 69 releases 2019-09-03 at the end of Quarter 3. https://wiki.mozilla.org/Release_Management/Calendar

Extensions support are in the "Reserved Backlog" category. Also locked to prevent any more comments about it. https://github.com/mozilla-mobile/fenix/issues/574

Extensions support is not in Q3 backlog https://github.com/mozilla-mobile/fenix/projects/19

Re: Firefox 68.0

#48

Post by tssva »

untog wrote: post #31
giancarlostoro wrote: post #3

> WebRender will roll out to Windows 10 users with AMD graphics cards. This sounds awesome: https://mozillagfx.wordpress.com/2019/05/21/graphics-team-sh... > WebRender is a major rewrite of the Firefox rendering architecture using the same kind of GPU-based acceleration techniques used by games. I really hope it gets pushed to other Operating Systems as well in the future. Edit: Here's the link to their hacks mozilla…

It's a shame it hasn't made it over to Mac yet - graphics card options are a lot more limited there so you'd figure it would be easier to support. But I suppose it's a much smaller market share.

There is a known severe performance issue on MacBooks with retina screens and integrated Intel graphics which this is suppose to be the solution to. Unfortunately this doesn't seem to have driven macOS to be a priority for the rollout.

Re: Firefox 68.0

#49

Post by capitol_ »

basch wrote: post #8
ceezuns wrote: post #2

"Dark mode in reader view expands so that windows are also dark on the controls, sidebars and toolbars." Thank god.

the blank white page is killer. inbetween page loads a bright flash of white.

This can be fixed with some user css.

/* Put the content below into your /chrome/userChrome.css */ .browserContainer { background-color: #000000 !important; }

Re: Firefox 68.0

#50

Post by llao »

benologist wrote: post #7
whatshisface wrote: post #5

> Local files can no longer access other files in the same directory. What impact will this have on web development without a web server? It sounds like you won't be able to load CSS or JS.

You can use software like https://serveo.net to assign a temporary domain to access your local files through a web server.

That's not necessary, if you run a local web server then this does not affect you. file:// is for access directly through the filesystem.
Post reply on HN