26 comments

[ 3.7 ms ] story [ 58.9 ms ] thread
> Kats is standing up WebRender in Firefox for Android

I'm guessing "standing" should be "setting"? Anyway, doesn't seem to work just yet for nightly. I enabled in about:config, but get "unavailable by runtime: WebRender not ready for use on non-e10s Android". Also, "WEBRENDER_QUALIFIED: blocked by env: Has battery"

I filtered by e10s and electrolysis in about:config but couldn't find anything

Standing up here means getting into a working but unfinished state. It’s a slightly uncommon turn of phrase, but it’s legit English.
Is this the opposite of "stand down"? It seems to be.
I think its more like "to erect"; "to stand down" is more like "hold back", "disengage" or "retreat" (intransitive).

stand up (intransitive) ~= stand from a sitting or lying position

stand up <direct-object> == erect, build, appoint, enact

stand-up, upstanding (adjective) == moral, ethical

stand-up [comedian] == actually standing on ones feet

To me it's very common in the tech community. Maybe a transfer from the embedded/sysadmin/DBA side of things, from what I've seen its usage move over time.
You aren't used to hearing about "standing up" new servers?
I must have written my text poorly, that's what I intended to convey; that in my experience the term's popularity started in the embedded/sysadmin/dba communities and then spread to the wider tech communities. Sorry! :)
It doesn't yet work on fennec (regular Firefox for Android, which is non-e10s). Instead we're working on it for geckoview.
To add to this - this means it could be enabled in focus/klar nightlies, except they don't have an about:config page. You can build it from source, though!

It's very early days currently so you're not missing anything, but as it gets more stable I'm sure it'll be easier to try out.

Me too. A bit of Googling told me that if you set the variable MOZ_WEBRENDER=1 it enables it. That worked.
Firefox has become crazy fast lately. Which is great! But on systems like a Surface tablet it seems to chew through battery much faster than Edge.

It seems to be pages that are actively modifying themselves. If they just sit there being static the power use isn't a problem.

Does it work on macOS atm?
(comment deleted)
Yes, I'm using it in Firefox 65.0a1 on a 15" 2017 MBP running High Sierra.

After setting gfx.webrender.all to true and restarting, check about:support and you should see "Compositing: WebRender"

Of course you may still hit bugs.

I think it's still disabled on beta for Mac laptops, but it could just be that I have an older (2014) MBP than you do.
Wondering if Pathfinder made it to this release? Perhaps pcwalton could chime in?
Enabled in FF Nightly 65.0a1 (2018-10-26) (64-bit) and it felt a little sluggish especially with regards to scrolling. I understand it's in beta but I guess I was expecting things to "feel" faster. Tried resizing larger sites/pages and things felt snappy but scrolling felt jumpy and off.

That said, can't wait for this to come out of beta!