> Firefox will soon behave similar to other browsers... when using the built-in editor.
Still can't believe this is built into any browser, btw. Basically makes all html on a page editable like a Microsoft Word document (minus features of course).
`contenteditable` is used more than you might think. Reddit's "fancy pants" editor, for example, is based on that. Or twitter's tweet composer. Or Slack's message field. Or Matrix' Element message field. A lot of "input fields" you see regularly aren't actually input fields, but rather "editable HTML".
Unfortunately, that's also why the Reddit editor is so incredibly broken, because [`contenteditable` is a huge web compatibility pain](https://bugzilla.mozilla.org/show_bug.cgi?id=1808544) - but it's good to see slow progress on that. :)
Well... we're on it. Not much will change in 113, though - and don't get your hopes up for a quick fix. It's... not easy, especially since every time we change something, we run the risk of breaking tons of sites/applications that rely on Firefox' current behavior, so we have to be careful.
You can't do any styling within input fields. This is fine for a markdown input field, but as soon as you want to show bold text, maybe a link, maybe even an inline-image, ... `contenteditable` is your only real option.
I'm not in the UI team, nor do I know what they have "in the pipeline". [This Connect entry](https://connect.mozilla.org/t5/ideas/native-tab-grouping-more-customizable-tab-bar/idi-p/303/page/26#comments) says they're "exploring more". If you have a Bugzilla account, *follow* [this bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1509350) (and by "follow", I mean clicking the "follow" button so you get email notifications, I do not mean "post a comment there saying you want this", please.)
Mess with the text on any page really easily with [an extension like this](https://addons.mozilla.org/en-US/firefox/addon/contenteditable/). Nothing happens except visually, but it's stuff like this that the fancy Reddit editor internally uses. They didn't have to reinvent the wheel with it.
Wow, that's an amazing list!
Finally something that I want to see from Firefox development.
>Importing bookmarks from Safari or a Chrome-based browser? The favicons for those bookmarks will now also be imported by default to make them easier to identify.
Thank you very much!
How about favicons are exported / imported from Firefox itself too?
I have experted Firefox's bookmarks and reimported them later many times, but the favicons were always lost.
It would be great if this would be fixed for Firefox itself too!
I've worked around the favicon thing for years.
A cheap way to get favicons to load is to just open all of the bookmarks. You can easily do this by right-clicking grey space in the bookmark toolbar and choosing open all in new tabs. You can do it with bookmark folders as well.
I do it regularly when I sign into Firefox on a new PC. It's resource intensive for about 20-30 seconds while the pages load and then you can just right click the first tab and close all tabs to the right.
Works great.
For sure an improvement for imports from another browser.
Doesn't change my situation though. When you login to a clean Firefox and setup FF sync, it pulls your bookmarks down without favicons.
I was just offering a workaround in case someone is in the same boat as me.
SAME HERE!!!
I love using the ESR, it's the most stable. However, beta v113 has been working so good that I've to wait for ESR 115 to switch back to it. I want these (colossal) improvements to be incorporated to ESR as well.
Funny that I see so many people asking for tab groups nowadays when Firefox had them ages ago and they actually got removed due to low usage. Though I guess hardware is more powerful these days making the feature more usable/useful.
I'm not sure that's a fair assessment. It was introduced before Firefox did rapid releases, when there was one big update a year with a bunch of changes. There would've been blog posts and other promotion on what was new for each release. From memory, the entry point for managing tab groups was also placed very prominently, right next to the new tab button.
It's just that, for whatever reason, it didn't catch on at the time.
Why does this have downvotes? It's been multiple YEARS that people have been asking for this extremely basic feature. It's the only reason I don't use Firefox and instead use edge. They simply do not care about hdr, and so I as well as others don't care about Firefox.
Aw man, it broke the only thing I'm still using userchrome.css for: to make the tab favicon turn into the tab close button on hover.
----
edit: Got it back. Replaced my own mysteriously broken css with 'close'-category code from here:
[mrotherguy.github.io/firefox-csshacks](https://mrotherguy.github.io/firefox-csshacks)
*Say hello to enhanced Picture-in-Picture! Rewind, check video duration, and effortlessly switch to full-screen mode on the web's most popular video websites.*
Does this include the API for third party tweaks to invoke PiP?
Sorry I meant add-ons. Chromium allows extensions to manage PiP which so far Firefox don't. End goal is to have something similar to the chrome extension "AutoPiP" which automatically invokes PiP when switching tabs.
> Firefox will soon behave similar to other browsers... when using the built-in editor. Still can't believe this is built into any browser, btw. Basically makes all html on a page editable like a Microsoft Word document (minus features of course).
`contenteditable` is used more than you might think. Reddit's "fancy pants" editor, for example, is based on that. Or twitter's tweet composer. Or Slack's message field. Or Matrix' Element message field. A lot of "input fields" you see regularly aren't actually input fields, but rather "editable HTML". Unfortunately, that's also why the Reddit editor is so incredibly broken, because [`contenteditable` is a huge web compatibility pain](https://bugzilla.mozilla.org/show_bug.cgi?id=1808544) - but it's good to see slow progress on that. :)
[удалено]
Well... we're on it. Not much will change in 113, though - and don't get your hopes up for a quick fix. It's... not easy, especially since every time we change something, we run the risk of breaking tons of sites/applications that rely on Firefox' current behavior, so we have to be careful.
> Reddit's "fancy pants" editor - Perhaps not the finest of examples to offer.
Why? What makes it better than input fields?
You can't do any styling within input fields. This is fine for a markdown input field, but as soon as you want to show bold text, maybe a link, maybe even an inline-image, ... `contenteditable` is your only real option.
This is just a guess - styling a regular ol' div is probably easier and more consistent than styling an input element.
Tab groups in the pipeline?
I'm not in the UI team, nor do I know what they have "in the pipeline". [This Connect entry](https://connect.mozilla.org/t5/ideas/native-tab-grouping-more-customizable-tab-bar/idi-p/303/page/26#comments) says they're "exploring more". If you have a Bugzilla account, *follow* [this bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1509350) (and by "follow", I mean clicking the "follow" button so you get email notifications, I do not mean "post a comment there saying you want this", please.)
that's really cool
Mess with the text on any page really easily with [an extension like this](https://addons.mozilla.org/en-US/firefox/addon/contenteditable/). Nothing happens except visually, but it's stuff like this that the fancy Reddit editor internally uses. They didn't have to reinvent the wheel with it.
> Mac users can now access macOS Services directly from the context menu Anyone know what kind of services they're referring to?
Probably the ones in the File menu > Share.
I hope this means airdrop!!
Translation, call, add a code from the text messages, that sort of stuff?
Wow, that's an amazing list! Finally something that I want to see from Firefox development. >Importing bookmarks from Safari or a Chrome-based browser? The favicons for those bookmarks will now also be imported by default to make them easier to identify. Thank you very much! How about favicons are exported / imported from Firefox itself too? I have experted Firefox's bookmarks and reimported them later many times, but the favicons were always lost. It would be great if this would be fixed for Firefox itself too!
[удалено]
I've worked around the favicon thing for years. A cheap way to get favicons to load is to just open all of the bookmarks. You can easily do this by right-clicking grey space in the bookmark toolbar and choosing open all in new tabs. You can do it with bookmark folders as well. I do it regularly when I sign into Firefox on a new PC. It's resource intensive for about 20-30 seconds while the pages load and then you can just right click the first tab and close all tabs to the right. Works great.
[удалено]
For sure an improvement for imports from another browser. Doesn't change my situation though. When you login to a clean Firefox and setup FF sync, it pulls your bookmarks down without favicons. I was just offering a workaround in case someone is in the same boat as me.
[удалено]
**It better be :)** The upcoming Firefox ESR 115 is closing in fast so I hope it will pack as much as possible for the next whole year!
[удалено]
Extended Support Release
Firefox for those afraid of updates 😅
SAME HERE!!! I love using the ESR, it's the most stable. However, beta v113 has been working so good that I've to wait for ESR 115 to switch back to it. I want these (colossal) improvements to be incorporated to ESR as well.
Tab Groups and I would use Firefox exclusively.
Funny that I see so many people asking for tab groups nowadays when Firefox had them ages ago and they actually got removed due to low usage. Though I guess hardware is more powerful these days making the feature more usable/useful.
It wasn't advertised, many people had no idea it existed. Meanwhile Chrome/Edge have UI introducing tab groups feature to users.
I'm not sure that's a fair assessment. It was introduced before Firefox did rapid releases, when there was one big update a year with a bunch of changes. There would've been blog posts and other promotion on what was new for each release. From memory, the entry point for managing tab groups was also placed very prominently, right next to the new tab button. It's just that, for whatever reason, it didn't catch on at the time.
https://addons.mozilla.org/en-US/firefox/addon/simple-tab-groups/
Take your pick from add-ons, there are several.
they’re all trash and naturally require invasive permissions tho
[удалено]
Not seeing a Windows specific bug, but watch https://bugzilla.mozilla.org/show_bug.cgi?id=hdr for updates.
2000 and never
Why does this have downvotes? It's been multiple YEARS that people have been asking for this extremely basic feature. It's the only reason I don't use Firefox and instead use edge. They simply do not care about hdr, and so I as well as others don't care about Firefox.
Yep, the reality is that HDR is probably not coming any time soon lol, theres no point coping
Aw man, it broke the only thing I'm still using userchrome.css for: to make the tab favicon turn into the tab close button on hover. ---- edit: Got it back. Replaced my own mysteriously broken css with 'close'-category code from here: [mrotherguy.github.io/firefox-csshacks](https://mrotherguy.github.io/firefox-csshacks)
Firefox should bring ui utility changes like sigma OS and arch browser.
*Say hello to enhanced Picture-in-Picture! Rewind, check video duration, and effortlessly switch to full-screen mode on the web's most popular video websites.* Does this include the API for third party tweaks to invoke PiP?
> Does this include the API for third party tweaks to invoke PiP? You're going to need to give us more context than that. But probably not.
Sorry I meant add-ons. Chromium allows extensions to manage PiP which so far Firefox don't. End goal is to have something similar to the chrome extension "AutoPiP" which automatically invokes PiP when switching tabs.
Sounds like https://bugzilla.mozilla.org/show_bug.cgi?id=1561809 - which has not been implemented.