Not totally related, but someone know if exist an RSS feed to follow the stable Firefox releases? Can't find it on this page. This Firefox changelogs are awesome to know big improvements and new features on a surface level. For Chrome I didn't find a proper way to follow the releases even if it has some RSS feeds, I follow the RSS feed of Chrome Releases blog [1] with a tag filter [2] but can't exclude the several po…
Interested myself, currently using https://groups.google.com/forum/feed/mozilla.announce/msgs/r... ( https://groups.google.com/g/mozilla.announce ).
Firefox 86.0
171–180 of 183 posts
Re: Firefox 86.0
#172Not totally related, but someone know if exist an RSS feed to follow the stable Firefox releases? Can't find it on this page. This Firefox changelogs are awesome to know big improvements and new features on a surface level. For Chrome I didn't find a proper way to follow the releases even if it has some RSS feeds, I follow the RSS feed of Chrome Releases blog [1] with a tag filter [2] but can't exclude the several po…
https://hg.mozilla.org/mozilla-unified/tags https://hg.mozilla.org/mozilla-unified/atom-tags https://hg.mozilla.org/mozilla-unified/rss-tags And here's my lua script that uses notify-send to notify me of new releases: https://gist.github.com/folknor/32f703b270c6ad72bc12d98feb2f... I modified it slightly before posting it here, but it's mostly useless unless you're me :-D Because when I write shell scripts (which I al…
Re: Firefox 86.0
#173Re: Firefox 86.0
#174Earlier quoted context omitted.
Should be possible using the Browser Toolbox to inspect the entire interface? I just checked and the HTML is definitely in the inspector at least, but I'm not sure what your requirements are.
What do you mean by "Browser Toolbox"? Firefox doesn't have Chrome's @media (print) emulation.
The Browser Toolbox is the normal DOM inspector, just extended to the whole user interface. If you open the print preview, then open the Browser Toolbox, you can inspect the preview and edit styles just like any other document.
Also, @media print {} works fine, I just tested it. But I'm not sure how that relates to the original question.
Re: Firefox 86.0
#175Earlier quoted context omitted.
Should be possible using the Browser Toolbox to inspect the entire interface? I just checked and the HTML is definitely in the inspector at least, but I'm not sure what your requirements are.
What do you mean by "Browser Toolbox"? Firefox doesn't have Chrome's @media (print) emulation.
Re: Firefox 86.0
#176I wonder if the web engine development pretty much stopped, or developer notes are just less detailed over the last year or so. Those are a shadow of the former self, certainly.
it’s particularly aggravating that form fields have been largely stagnant over the past 20 years. so much repetitive development happens around forms (validations or date/time pickers, for instance) and yet very little effort goes into improving them.
Re: Firefox 86.0
#177Not totally related, but someone know if exist an RSS feed to follow the stable Firefox releases? Can't find it on this page. This Firefox changelogs are awesome to know big improvements and new features on a surface level. For Chrome I didn't find a proper way to follow the releases even if it has some RSS feeds, I follow the RSS feed of Chrome Releases blog [1] with a tag filter [2] but can't exclude the several po…
https://hg.mozilla.org/mozilla-unified/tags https://hg.mozilla.org/mozilla-unified/atom-tags https://hg.mozilla.org/mozilla-unified/rss-tags And here's my lua script that uses notify-send to notify me of new releases: https://gist.github.com/folknor/32f703b270c6ad72bc12d98feb2f... I modified it slightly before posting it here, but it's mostly useless unless you're me :-D Because when I write shell scripts (which I al…
Re: Firefox 86.0
#178Re: Firefox 86.0
#179Earlier quoted context omitted.
>My bet is that they were receiving complaints of Firefox breaking due to bad migration of settings between versions, so instead of fixing the migrations, they decided that this user-hostile anti-feature was good enough. I think this is actually a good feature, one of the few introductions which I think if worthwhile, even if the implementation is a bit lacking. You have to balance the user being able to see the mess…
Hum... Keep in mind that there is no option to not erase your configurations. And that "configurations" has a very bread sense, including everything from about:config settings, themes, extensions, history, cache, cookies, saved passwords, and even for a short period including bookmarks (thankfully that one they stopped erasing). And, by the way, Firefox will revert from a backup if you are logged in into an account,…
Re: Firefox 86.0
#180Earlier quoted context omitted.
>My bet is that they were receiving complaints of Firefox breaking due to bad migration of settings between versions, so instead of fixing the migrations, they decided that this user-hostile anti-feature was good enough. I think this is actually a good feature, one of the few introductions which I think if worthwhile, even if the implementation is a bit lacking. You have to balance the user being able to see the mess…
Hum... Keep in mind that there is no option to not erase your configurations. And that "configurations" has a very bread sense, including everything from about:config settings, themes, extensions, history, cache, cookies, saved passwords, and even for a short period including bookmarks (thankfully that one they stopped erasing). And, by the way, Firefox will revert from a backup if you are logged in into an account,…
It sounds like something which started out as a good idea and was then steered into user abuse territory.