Firefox派生タブブラウザ　PaleMoonの話っぱの

The Pale Moon Project homepage https://www.palemoon.org/

前記事は2023/02/23 Pale Moon 32.0.1 が来てるっぱね

 

しばらく前にフォーラムで今後の方針に関して告知があり 大化けしたので見てない方は確認してきたほうがいい予感っぱ

特に今回は「GoogleWebコンポーネント実装」しちゃってるからの？

日本語化は何時もなら↓のでいいはずだっぱが… Pale Moon - Add-ons - Japanese (JP) **https://addons.palemoon.org/addon/pm-langpack-ja/

リリースノート曰く

Pale Moon - Release Notes https://www.palemoon.org/releasenotes.shtml

---

v32.1.0 (2023-03-21)

This is another major update with important compatibility improvements for the web. Most notably, our implementation of Google WebComponents is now at a state where we enabled them by default.Additionally, our Mac builds (for both Intel and ARM Macs) are no longer in beta and considered stable. Signed/notarized builds with the regular branding are available from the download page!Huge thanks to FranklinDM for his work this cycle getting us to this point. Of course major thanks to everyone who has contributed to this complex and difficult WebComponents task over a long time!Thanks also to Martok and Job Bautista for continuing to work on and improve the JavaScript engine as well as u3shit for working on video playback improvements.Changes/fixes:

 

 

• Shadow DOM and CustomElements, collectively making up WebComponents, have been enabled by default which should bring much broader web compatibility to the browser for many a site that uses web 2.0+ frameworks. See implementation notes.
• Tab titles in the browser now fade if they are too long instead of using ellipses, to provide a little more readable space to page titles. Note that this may require some updates to tab extensions or themes.
• A number of site-specific overrides have been updated or removed because they are no longer necessary or current with the platform developments in terms of web compatibility. We could use your help evaluating the ones that are still there; see the issue on our repo.
• Updated our promises and async function implementation to the current spec.
• Implemented Promise.any()
• Fixed several crashes related to regular expression code.
• Improved regular expression object handling so it can be properly garbage collected.
• Fixed some VP8 video playback.
• Fixed an issue where the caret (text cursor) would sometimes not be properly visible.
• Updated the embedded emoji font.
• Implemented the :is() and :where() CSS pseudo-classes.
• Implemented complex selectors for the :not() CSS pseudo-class.
• Implemented the inset CSS shorthand property.
• Implemented the env() environment variable CSS function. See implementation notes.
• Implemented handling for RGB encoded video playback (instead of just YUV).
• Implemented handling for full-range videos (0-255 luminance levels) giving better video playback quality.
• Removed the WebP image decoder pref. See implementation notes.
• Enabled the Web text-to-speech API by default (only supported on some operating systems).
• Updated NSPR to 4.35 and NSS to 3.79.4
• Cleaned up unused “tracking protection” plumbing. See implementation notes.
• Cleaned up URI Classifier plumbing (Google SafeBrowsing leftover).
• Fixed several intermittent and difficult-to-trace crashes.
• Improved content type security of jar: channels. DiD
• Improved JavaScript JIT code generation safety. DiD
• Fixed potential crash scenarios in the graphics subsystem. DiD
• Improved filename safety when saving files to prevent potential environment leaks.
• Security issues addressed: CVE-2023-25751, CVE-2023-28163 and several others that do not have a CVE.
• UXP Mozilla security patch summary: 1 fixed, 4 DiD, 14 not applicable.

Implementation notes:

 

 

• Google WebComponents has been long-running major feature work in UXP. We’re finally at a level with this (after several setbacks and brick-walling) that it can be enabled by default. Please note that while this greatly improves web compatibility with many Chrome-focused websites using these controversial technologies, our implementation is not yet complete and more work is necessary. As a result, this change to enable it by default may actually break some previously-working websites as well, but it’s expected the majority will work at our current state of implementation. Please visit the forum if you need help with web compatibility issues.
• The env() CSS function was implemented for compatibility with websites that rely on this without fallback. Note that this function actually has no real use for desktops as it is primarily used to indicate environmental restrictions of mobile screens, e.g. extra space needed to avoid a camera notch or folding screen margin. However, due to the way certain sites implement their styling in a mobile-first approach, it is assumed that this function is available on all systems and in all browsers by these sites. Note that Pale Moon simply hard-codes queried values here.
• WebP images have had a stable and complete implementation in Pale Moon for a long time now, so the preference to disable support for it has been removed, as it’s considered by now to be one of the “staple” image formats supported by web browsers. This was done to reduce complexity for content negotiation, especially since we’re adding more support for JPEG-XL that still isn’t as-complete. From here on out, we simply always support WebP decoding.
• While we’ve had a preference for “tracking protection” in our browser implementation (in about:config), this marketed feature of Firefox was never adopted by us, because it is for the most part a service-based feature, and the non-service parts were undesirable as they were crippling useful APIs. Our effective protection against tracking has not changed, we have simply removed the preference and plumbing for a non-functional service feature that would potentially give the false impression it would do anything.As a reminder, if you are concerned about tracking, use a competent adblocker extension, and enable “Tell sites not to share or sell my data” in Preferences -> Privacy under “Data Privacy”. You may also want to enable “canvas poisoning” by setting canvas.poisondata to true in about:config to reduce the risk of fingerprinting through canvases.

---

GoogleWebコンポーネントの実装でWeb互換性は間違いなく向上した予感っぱ(´･Θ･`) ただ、Googleを全力でオプトアウトしたいユーザーの方は「デフォルト」で初期値は有効になっているので手動でOFFにする必要があるので念の為のぅ？ 気にしない人はGoogle系の再生出来なかったページとかがコンテンツが機能する可能性が大幅に向上するので良かったねという話っぱ(人Θ’o)

他にWEBテキスト読み上げAPIを既定で有効になってるのも地味に「突然PCが喋りだした！？」になるので一応注目事項だの((´Θ`))ｹﾗｹﾗ

そしてうまく動作しないサイトの為にPale Moon 側で微調整していた上書き設定がもう必要ないので削除されたそうなので ごく一部のサイトで上手く動作しないとかあればフォーラムに相談するとよさそうだの

ほかはバグ修正関係っぽいの(´･Θ･`)

実装ノート側WebP画像の安定した実装・サポートしていく事についてと 昔はプライバシー追跡保護とかに気合を入れていたけど現在の利用者と実装希望との兼ね合い等で そこまでやる必要がないAPIも無効にしていた設定を削除したそうな ただabout:config からキャンバスフィンガープリント対策等の設定を有効にして使ったりはこれからも出来るそうっぱ(´･Θ･`) この実装は他のBrowserより一番ここが早かったもんのぅ・・ほかは素直に広告ブロックアドオンを使ったほうがプライバシー保護になる

という考え方での更新になったっぽいのえっと・・ 「canvas.poisondata」を“true”about:config からやっとけば一般論としては問題ないと思うっぱよ？**

おおむねそんな具合の話っぱの

日本のサイトだと広告関係の糞情報収集がえらいおおくての Pale Moon使わないにせよそれらのフィンガープリント絡みへの対策用アドオンいれて使った方がいいっぱよ？

どういう悪影響があるかは昔説明した気がするし最近はAIに聞いたほうが詳しく教えてもらえる様子だっぱので割愛っぱ（こら

かっぱでしたっぱ♪

---

Browser関係という事で１つぼやいておくとBingは不味いかもしれん（ボソ

BingAIが「漢字」多めの会話をしようとすると「中国」扱いしてくる事があるっぱ そうなると質問のログや地域の取り扱いが中国法の検閲フィルターの傘下に切り替わるっぱ（疑惑 これらに関してはBing自体がそもそも１年位前にも調査機関に釘をさされてるんだっぱが

BingAIもその悪い癖をもってる気配だの・・　なのでアレはおすすめしないっぱよ( ;’Θ`)ｳｰﾝ現時点では

ブラウザー選びに注意を払って、アドオン選びにも注意を払って、開発者が乗っ取られて吸われないかお祈りしながら使う時代… という疑惑があるっぱ（そこらはセキュリティ対策ソフトにお祈り面もあるにせよ難儀な時代っぱね）

📝

https://jp.wsj.com/articles/microsoft-said-to-censor-searches-in-u-s-for-politically-sensitive-chinese-names-11652975315

かっぱでしたっぱ♪