SUMO community discussions

Firefox 122 for Desktop - Release Notes / Issues / Discussions

  • 6 Replies
  • Last reply by jscher2000 - Support Volunteer
  1. philipp
    philipp 1301 posts
    more options

    Tomorrow, January 23, is the release date for Firefox 122.

    These links will contain the usual bits of information for the new version once the release is live:

    As always feel free to add to this thread if you see other news or common problems popping up with the release as it goes live to more users. If you're a user yourself looking for help though, post in the support forum instead pls :))

    Tomorrow, January 23, is the release date for Firefox 122. These links will contain the usual bits of information for the new version once the release is live: * release notes: https://www.mozilla.org/firefox/122.0/releasenotes/ * sec advisories: [https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/#firefox122] * complete list of changes: [https://bugzilla.mozilla.org/buglist.cgi?j_top=OR&f1=target_milestone&o3=equals&v3=Firefox%20122&o1=equals&resolution=FIXED&o2=anyexact&query_format=advanced&f3=target_milestone&f2=cf_status_firefox122&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&v1=mozilla122&v2=fixed%2Cverified&limit=0] * developer notes: [https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/122] As always feel free to add to this thread if you see other news or common problems popping up with the release as it goes live to more users. If you're a user yourself looking for help though, [https://support.mozilla.org/questions/new post in the support forum instead] pls :))
  2. AliceWyman
    AliceWyman 6313 posts
    more options

    The above "complete list of changes" link comes back with zero bugs for me. Using the "Complete list of changes ..." link at the bottom of the Firefox 122 release notes under "Other Resources" does produce a bug list <snip> (but posting it here doesn't work). Disregard -it works now.

    <s>The above "complete list of changes" link comes back with zero bugs for me. Using the "Complete list of changes ..." link at the bottom of the [https://www.mozilla.org/firefox/122.0/releasenotes/ Firefox 122 release notes] under "Other Resources" does produce a bug list <snip> (but posting it here doesn't work).</s> <sub>Disregard -it works now.</sub>

    Modified by AliceWyman on

  3. Kiki
    Kiki 1660 posts Mozilla Staff
    more options

    Cross post here for reference.

    Related to the changes from “about:logins” to “about:passwords” from our Credential Management articles (bug1865866), the content team is going to revert the revisions since the changes are postponed on desktop. Changes on mobile should be underway, on the other hand. Feel free to watch the bug I reference to get update on this matter.

    Cross post here for reference. Related to the changes from “about:logins” to “about:passwords” from our Credential Management articles ([https://bugzilla.mozilla.org/show_bug.cgi?id=1865866 bug1865866]), the content team is going to revert the revisions since the changes are postponed on desktop. Changes on mobile should be underway, on the other hand. Feel free to watch the bug I reference to get update on this matter.
  4. Vanho
    Vanho 1 post
    more options

    Hi,mozilla. I have a suggestion.

    The line breaking rules of Web content now match the Unicode Standard. This improves Web Browser compatibility for line breaking. An additional improvement for East Asian and South East Asian end users, Firefox now supports proper language-aware word selection when double-clicking on text for languages including Chinese, Japanese, Burmese, Lao, Khmer, and Thai.

    I am japanese. "Firefox now supports proper language-aware word selection when double-clicking on text for languages " This function is not suitable for Japanese. For example, 炊飯器 means rice cooker　is not "炊飯+器 = rice+cooker". "rice cooker" is "炊飯器 = ricecooker" in japanese. 調理時間 means "cooking time" is not "調理+時間 = cooking+time". "cooking time" is "調理時間 = cookingtime" in japanese. Unlike English, Japanese is very often a combination of several words into a single word. In addition, when a person's name is written in kanji, it is no longer possible to select it by double-clicking. The Japanese Firefox user community complained a lot about this change, and it has been addressed in user.js to revert to the old specifications. However, the percentage of Japanese users who come to this community is small, and there are barriers to using user.js, so I think most people remain dissatisfied. "The line breaking rules of Web content now match the Unicode Standard. " I think this change is great, but I strongly suggest that the word selection feature be changed back to being selected by a block of Unicode. I would like Japanese developers and contributors to also inquire about this proposal.

    I think the sentences are unnatural because I use machine translation, so please forgive me.

    Hi,mozilla. I have a suggestion. The line breaking rules of Web content now match the Unicode Standard. This improves Web Browser compatibility for line breaking. An additional improvement for East Asian and South East Asian end users, Firefox now supports proper language-aware word selection when double-clicking on text for languages including Chinese, Japanese, Burmese, Lao, Khmer, and Thai. I am japanese. "Firefox now supports proper language-aware word selection when double-clicking on text for languages " This function is not suitable for Japanese. For example, 炊飯器 means rice cooker　is not "炊飯+器 = rice+cooker". "rice cooker" is "炊飯器 = ricecooker" in japanese. 調理時間 means "cooking time" is not "調理+時間 = cooking+time". "cooking time" is "調理時間 = cookingtime" in japanese. Unlike English, Japanese is very often a combination of several words into a single word. In addition, when a person's name is written in kanji, it is no longer possible to select it by double-clicking. The Japanese Firefox user community complained a lot about this change, and it has been addressed in user.js to revert to the old specifications. However, the percentage of Japanese users who come to this community is small, and there are barriers to using user.js, so I think most people remain dissatisfied. "The line breaking rules of Web content now match the Unicode Standard. " I think this change is great, but I strongly suggest that the word selection feature be changed back to being selected by a block of Unicode. I would like Japanese developers and contributors to also inquire about this proposal. I think the sentences are unnatural because I use machine translation, so please forgive me.
  5. Luz White
    Luz White 1 post
    more options

    Thank for sharing valuable info.

    Thank for sharing valuable info.
  6. Mandy
    Mandy 16 posts
    more options

    Hi y'all! Just want to share an upcoming update on Feb 22 -- Firefox Desktop will be retiring BrowserID officially (a protocol to leverage data syncing (bookmarks, passwords) via Firefox Accounts). BrowserID has already been retired everywhere except our current ESR version V78. We will email users on version 78 and older and request that they follow some steps to ensure they do not lose sync data, but wanted to flag here too in case we see any users who miss the notice, or who see the notice and reach out with questions/concerns.

    Hi y'all! Just want to share an upcoming update on Feb 22 -- Firefox Desktop will be retiring [https://hacks.mozilla.org/2011/07/introducing-browserid-easier-and-safer-authentication-on-the-web/ BrowserID] officially (a protocol to leverage data syncing (bookmarks, passwords) via Firefox Accounts). BrowserID has already been retired everywhere except our current ESR version V78. We will email users on version 78 and older and request that they follow some steps to ensure they do not lose sync data, but wanted to flag here too in case we see any users who miss the notice, or who see the notice and reach out with questions/concerns.

    Modified by Mandy on

  7. jscher2000 - Support Volunteer
    jscher2000 - Support Volunteer 832 posts
    more options

    Vanho said

    The Japanese Firefox user community complained a lot about this change, and it has been addressed in user.js to revert to the old specifications.

    Hi, what preference is changed by the user.js file? Is it setting intl.icu4x.segmenter.enabled to false?

    That is a change which could be made more easily through the about:config preferences editor (Configuration Editor for Firefox), although we generally give a warning about using it.

    More generally:

    That might be a temporary preference, so it would be a good idea to file a bug regarding the segmenter on https://bugzilla.mozilla.org/ with details about the problem if no one has done that yet.

    ''Vanho [[#post-86974|said]]'' <blockquote> The Japanese Firefox user community complained a lot about this change, and it has been addressed in user.js to revert to the old specifications. </blockquote> Hi, what preference is changed by the user.js file? Is it setting '''intl.icu4x.segmenter.enabled''' to false? That is a change which could be made more easily through the about:config preferences editor ([[Configuration Editor for Firefox]]), although we generally give a warning about using it. ''More generally:'' That might be a temporary preference, so it would be a good idea to file a bug regarding the segmenter on https://bugzilla.mozilla.org/ with details about the problem if no one has done that yet.