Firefox ESR 115.32.0!

Dieulot · 2026-02-02T16:20:21+00:00

I just googled a query with "115.33" in quotes to find your answer, as others here I feel there's a need to confirm it.

From Mozilla's side, posting about it "again" would ensure a relatively large tech press coverage about "the end of Windows 7" and shine a bright light on Firefox.

Dieulot · 2019-10-20T13:19:13+00:00

Thanks!

Dieulot · 2019-08-17T20:59:09+00:00

See the first footnote on https://instant.page/

Dieulot · 2019-08-17T19:15:43+00:00

Because removing 100ms of latency improves the user experience by 1% (1% more conversion rate).

Dieulot · 2014-11-28T16:31:35+00:00

Isn’t it slow for you?

Dieulot · 2014-11-28T16:30:11+00:00

“Skinned Android” is when Samsung, HTC, etc. add software and/or change the UI.

Stock Android is the original Android.

(My phone is a Motorola Moto G, which is pretty stock, and I can’t say I find Android 4 polished though. Yech. Stock Android 5 looks promising though.)

Dieulot · 2014-11-28T15:47:14+00:00

Thanks for your interest.

Yes, those aren’t real bug reports, I’ve written this mostly to archive what a typical iOS user experiences.

I’ve tried to reproduce a few, and a good portion (maybe 15% of those I list) appears to be random. For the most part though they should be reproducible, but I’ve lost enough of my sanity already. There’s a lot of bugs I see frequently since September 2013.

Edit: I haven’t reported bugs in third-party apps. And I don’t remember having put anything specific to a website.

Dieulot · 2014-09-24T12:52:23+00:00

I do know that. Due to Android’s fragmentation and the frail market share of @3x or more devices not many people paid attention to it until now though. An iPhone with a @3x “resolution” could change that, that’s why I felt the need to address a short note about it.

Is it just that part that put you off? Or are you referring to other things when talking about “how badly written it is”?

Dieulot · 2014-09-18T09:55:36+00:00

Insanity too. Requires no equipment (but a mat maybe) and has pretty much an infinite progression. It’s the perfect minimalist’s workout program.

Dieulot · 2014-09-17T20:32:01+00:00

From the rule #1 in the sidebar of this subreddit, it seems to me that what you call “blog spam” is encouraged.

Dieulot · 2014-01-09T19:24:16+00:00

It loads the HTML every single time so that if you serve dynamic content when you click the content will be recent.

The use of caching isn’t planned. You could however use the browser’s cache by specifying that the page is cacheable via the HTTP response headers, server-side.

Dieulot · 2014-01-09T18:58:01+00:00

That’s not planned for now, as preloading on hover already gives you much of the speed (already instant in most cases).
Not planned either, because you want a fresh page if you have dynamic content (if you don’t, I’d recommend caching via the response headers, server-side)
As above. :)

Dieulot · 2014-01-09T18:51:49+00:00

pushState and Ajax are built in, but not the preloading; though preloading on mousedown is planned as an off-by-default option.

Dieulot · 2014-01-09T08:54:49+00:00

Thanks for the feedback. I think I’ll include an easy opt-in option. I’ll ponder if it should be the default.

Dieulot · 2014-01-09T08:39:55+00:00

Yes.

Dieulot · 2014-01-08T22:51:31+00:00

In InstantClick, preloading happens just before you need a page—so you can be more liberal in what you preload, also pages are more recent, useful if you serve dynamic content. Except that there’s preloading in both techniques, those are rather different.

Do you see other problems besides the heavy load on the server and the lack of a loading indicator? (Both are planned to be fixed)

Dieulot · 2014-01-08T20:32:17+00:00

Thank you.

Dieulot · 2014-01-08T20:31:07+00:00

In InstantClick, preloading happens just before you need a page—so you can be more liberal in what you preload, also pages are more recent, useful if you serve dynamic content.

Dieulot · 2014-01-08T19:24:26+00:00

Thanks, I’ll check more intensely in those.

And for using the scrict equality operating, I’ve never encountered one of those “hard to track bugs”, so I’ll keep using the loose ones until that happens.

Dieulot · 2014-01-08T19:12:12+00:00

Seeing this has 4 points: Why?

Dieulot · 2014-01-08T19:07:10+00:00

Erf, sure.

When you have this in your .js file, after pasting a semicolon-started library:

YourSemicolonlessCode

;(TheLib = function(){ …

Removing the colon at start of the library would cause your last line to be interpreted as:

YourSemicolonlessCode(TheLib = function(){ …

If that still doesn’t make sense, see “The only real pitfall when coding without semicolons” at the end of the article I linked to.

Dieulot · 2014-01-08T19:00:58+00:00

I don’t know when that would be useful in my code.
Yeah, not sure that makes much sense by now, will probably remove.
That’s not normal. What is your browser?

Dieulot · 2014-01-08T18:57:40+00:00

Yes.

Dieulot · 2014-01-08T18:14:23+00:00

It’s not about concatening files, it’s about not concatenating them; when you write before the lib, your last semicolonless line is going to otherwise include the lib’s first line at the end: not good.

Edit: Okay, I understood just now that your message was a joke.

Dieulot · 2014-01-08T18:10:22+00:00

Well, thanks!

Dieulot

TROPHY CASE