For some reason I read this as "Starfox 64 Released". I was confused and happy. Now I'm a little less of both.
Firefox 64 Released
81–90 of 527 posts
Re: Firefox 64 Released
#82Earlier quoted context omitted.
Answering my own question... it is, indeed, markedly better than the last new release I tried. It was really janky looking for a while. It still doesn't look as clean as Chrome's tab bar, but it's reasonable now. So props to the Mozilla team on that.
I actually prefer the old 'triangle' Chrome tab bar.... the new curvy Chrome one is horrible.
I think I liked the more triangle shaped tabs as well, but w/r/t Firefox, there was a recent release (couple of months ago?) where the tab-bar was all kinds of jacked up. Maybe it was just a short-lived bug or something... what it was, it looks a lot better now.
Re: Firefox 64 Released
#83Firefox is in a major version number race status with minor fixes.
It's all been downhill since 3.x... If they could put the current engine behind the 3.x series interface, I'd be one happy camper. I mean, other than the fact all "modern" websites suck now too.
Yep, things were better in the good old days.
Re: Firefox 64 Released
#84I wish they'd finally fix pinch-to-zoom on OS X. This is the main thing that keeps me using Chrome.
Same for me. And two finger scrolling. Just feels wrong in Firefox on macOS.
What do you mean? I have not noticed anything different. Although i am on old macbook pro with the smaller trackpad.
Re: Firefox 64 Released
#85The new API browser.menus.overrideContext is announced with documentation links pointing to blogs, including a personal blog page with unrelated Japanese texts and anime pictures. The official documentation (MDN) has no reference to the new features. Even the API features from FF63 (august 2018) are only have a draft of documentation (e.g. Menus.getTargetElement). Documentation is important, even more for an API. I think this pattern is worrying.
Re: Firefox 64 Released
#86Earlier quoted context omitted.
You have no idea how excited I am for this. I use sway as my daily driver since it supports HiDPI so much better than i3, but the one caveat to that has been firefox and xwayland. Once this ships, sway will have nearly flawless HiDPI support.
This has actually worked decently well in Fedora for awhile now by doing: `export GDK_BACKEND=wayland` before starting Firefox.
Yea that was for Fedora-specific builds, in 65 it's now enabled for the general Linux release on their site.
Re: Firefox 64 Released
#87Anecdotally I keep finding myself stuck in Captcha loops of Firefox and the same sites work fine on Chrome?
Anyone else finding this?
Re: Firefox 64 Released
#88Still no bounce scroll on mac makes this dead in the water for me. Folks, the UI look and feel stuff really matters. You can't treat a platform like a second-class citizen and hope to gain widespread adoption.
Interesting. I am ux designer and i never thought people care about this or even realize there is difference. I mean actually quite opposite lot of people i know were confused from the movements first time this feature landed in safari.
Anyway surely this is not a showstopper. I mean it is not functional in any way.
Re: Firefox 64 Released
#89I've just updated to new beta (Firefox 65.0b3) with WebRender enabled and it started showing such error in about:support: [GFX1-]: shader-cache: Shader disk cache is not supported I'm using AMD GPU and as far as I know, Mesa supports shader cache for radeonsi and radv. Does anyone know why that error is showing up?
because you're on a beta build?
Why would beta build not find shader cache?
Re: Firefox 64 Released
#90Earlier quoted context omitted.
You have no idea how excited I am for this. I use sway as my daily driver since it supports HiDPI so much better than i3, but the one caveat to that has been firefox and xwayland. Once this ships, sway will have nearly flawless HiDPI support.
I'm not. Wayland lacks a lot compared to X.[1] From the linked-to-post, it lacks: * Programmatic output configuration (xrandr, arandr, etc.) * CLI clipboard access (xsel, xclip) * Third party app launcher/window switcher (rofi, dmenu, albert, docky). * Clipboard managers (parcellite, klipper, Gpaste, clipman, etc.) * Third party screen shot/capture/share (shutter, OBS, ffmpeg, import, peek, scrot, VNC, etc.) * Color…
xclip works fine for me on wayland (Arch), the rest... yeah, colorpicker? doesn't work. Screenshot? Gnome tool works but grabbing an area has a weird tainted color.