Firefox 39.0 released (opens in new tab)

Guess nobody told them,

https://bachelorburnbook.files.wordpress.com/2013/07/image.p...

fetch looks nice on the surface, but you can't cancel a request. is there even a timeout?

how do I use it with the yield keyword?

Good. Breaking their websites is the only way some people will fix their broken security.

Actually, the security.tls.unrestricted_rc4_fallback is still true by default.

I'm torn.. I dislike scroll hijacking and in a sense don't want support for this practice, _but_ at the same time I assume this will never go away and then this seems less hacky and easier to make it work without ruining use on various input devices and settings.

For example, I tried the demo and saw how the pages jumped to the nearest page if I middle click and pulled down to go half way. Corner cases or anything more complicated than simple wheel flips often don't seem to work if you hack your own solution. Now the browser seems to have a much better idea of what's going on. So.. That's nice. We'll get hijacks but at least they seem to be much more robust? But at the same time I hope this won't make more designers hijack scrolling or go overboard with this. :\

People experimented with new ways of handling user input (as they have for decades), found that it was a good way to layout some pages, and then complained to browser vendors that doing it in JS sucks. CSS snap points is just a way to make the experience better for developers and users. That's exactly how the Web should work.

Personally I think CSS is "style hijacking" — the Web really is about the text, not the colors.

The Firefox/native version of the page works much better than the jQuery version. Both are a little bit janky with touchpad scrolling, but the native version allows you to scroll to the next page before waiting for the animation to finish. With a mousewheel, the native version is far better and acts as you expect; the jQuery version just feels like a terrible hack and doesn't let you scroll where you want, when you want.

Woah I did not expect it to work that well. I always hated scroll-hijacking webpages, because ~1% of them did it right.

As much as the effect can be irritating, Firefox lets you over-scroll before snapping which is a much better experience compared to that fallback jQuery plugin.

this is in Safari 9 as well. https://developer.apple.com/library/prerelease/mac/releaseno...

I'm on ff 40 (developer edition), so presumably I've been running project silk for a while now, and for me the scrolling is visually indistinguishable from chrome. The difference is in the inertia: chrome slows to a halt marginally more smoothly, and it does that thing where you can elastically scroll past the end of the page.

The increased smoothness of the inertial model probably indicates that chrome's scrolling is actually better, repaints more closely aligned to vsync or whatever, but like I say there are no actual artifacts, tearing etc. visible on my macbook retina. If you've got a top of the line 120fps gaming monitor its probably more noticeable.

That fancy lcd-testing website probably has some way of measuring it.

For me the big issue is the lack of visual feedback when swiping left and right to go back and forward. In chrome/safari you get a big sliding animation to tell you you're triggering the gesture correctly. In FF you just get an arrow after the gesture has been triggered, when its just annoying visual clutter. This means it still sometimes takes me multiple attempts to hit it, because I don't have that feedback during the gesture to cement the muscle memory.

EDIT: apparently chrome gives you the arrow, ff gives you absolutely nothing.

For what it's worth, I've just updated on OS X and scrolling feels just as janky as ever.

I noticed a huge difference with this site: http://www.2ality.com/2015/02/es6-classes-final.html

In the previous Firefox version scrolling on that site was laggy to the point of being unusuable for some reason.

Definitely an improvement for me. Smooth inertial scrolling on trackpad has been the reason why I still use Safari on OS X.

I can't feel any difference between Chrome and Firefox when scrolling, but http://www.vsynctester.com/ is jankier on Firefox on my old-ish Macbook Air.

I can't wait to write it tonight! This is one missing thing on OSX.

It's OSX only for now.

Firefox's URL bar is literally my favorite Firefox feature. It's quick, it searches my local history much better than Chrome, and it doesn't leak anything to the world.

If I want to search the Internet, I type in the search box.

I really do miss typing part of a domain name (often YouTube), hitting tab, and doing an on site search.

But I'll put up with whatever to support Mozilla. Their work on Firefox and Rust is some of the most important going on.

I can't think of a situation that would make me want to move nodes around from place to place. Where would that be useful?

Chrome dev tools also support node drag-and-drop as well as ctrl-x/c/v in the Elements panel.

That would annoy me too, but I've never noticed it. My main laptop is a Core 2 Duo, so not a speed demon. Have you tried with extensions disabled and/or with a new profile?

If i ever go to hell i know what my punishment will be - implement unicode

You’ll need to have a font installed that supports them, Firefox does not bundle fonts for emoji ;)

I only recently discovered that Unicode characters can now have colour in them, and frankly, I'm disappointed that we're adding complexity to an already hugely complex topic.

This is bullshit.

Yes I have noticed the exact same thing on Reddit lately. My guess it's because they started sending "Cache-Control: no-cache" which prevents Firefox to cache the page for the back button.

I haven't seen many people mentioning this problem before. I've seen it come up in discussions on the current AMD GPU lines. Hard to say who is to blame, but it's rarely obvious just how many problems there are before buying a card. I got a cheap R7 260x which seems to have trouble with waking up from low power states. Some people even made custom BIOS's to fight the problem.

I don't know how more modern stuff like accelerated transforms, canvas, WebGL or DirectWrite play into that equation. Browsing seems to pull out GPU's from the lowest power modes constantly, which might cause these problems on a wide variety of GPUs.

Can you post a screenshot?

firefox is on a 6-week release schedule, and has been for a while. They increment a by whole number each time, but the for both chrome and FF they shouldn't really be thought of as .0 releases. It's a fairly minor, incremental change.

Windows XP never stopped having bugs, and who knows how many patches they'd applied to it.

It's fixed in the dev channel, it just hasn't propagated to stable or beta yet.

Since Chromium is open source, you can contribute to the project. I'm sure if you send a quality patch to the Chromium dev team to fix Logjam, they'd be willing to review it.

Did you try to contribute to Chromium and Firefox to speed up fixing the Logjam issue ?