Jump to content

My Browser Builds (Part 3)


Recommended Posts

8 hours ago, VistaLover said:

Well, each Saturday's releases do come with a changelog (Release Notes)

8 hours ago, NotHereToPlayGames said:

I don't read them.  99% of them make ZERO sense to me.  I wish they were in a "hide/show" toggle-box because I kinda see them as a pain to scroll, scroll, scroll, scroll, scroll 

I second that motion. The change log is usually quite long and very technical; hard to understand even for those of us who dabble in programming. Putting it in a spoiler tag would let us refer to it if need be but save our scroll wheels if not....

Even better would be a plain-language "executive summary" of the changes, but I'm sure that's out of the question. It would have to come from upstream....

Link to comment
Share on other sites


New build of Serpent/UXP for XP!

Test binary:
Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20220514-3219d2d-uxp-774750839-xpmod.7z
Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20220514-3219d2d-uxp-774750839-xpmod.7z

source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom

IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20220514-3219d2d-uxp-774750839-xpmod-ia32.7z

source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32

NM28XP build:
Win32 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20220514-d849524bd-uxp-774750839-xpmod.7z
Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20220514-d849524bd-uxp-774750839-xpmod-sse.7z
Win64 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win64-git-20220514-d849524bd-uxp-774750839-xpmod.7z

Official UXP changes picked since my last build:
- Issue #1891 - Fix ASAN and clang crashes on Linux, BSD and MacOS. Merge with the existing Solaris fix, by folding Solaris into the Linux/BSD section. Add Apple Silicon (ARM64) support. This should also address Issue #1884 by moving the offending code into assembly. (fd04893c3)
- Issue #1509 - Invalidate previous result when datalist is changed. (046b81d06)

No official Pale-Moon changes picked since my last build.

No official Basilisk changes picked since my last build.

My changes picked since my last build:
- gmp: replace preprocessor directives with AppConstants conditions (ef6b9353a)
- pref: add CSS grid pref (297adbdb2)

* Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

Link to comment
Share on other sites

New build of BOC/UXP for XP!

Test binary:
MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20220514-3dbfc66a-uxp-774750839-xpmod.7z
BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20220514-3dbfc66a-uxp-774750839-xpmod.7z

source repo (excluding UXP): https://github.com/roytam1/boc-uxp/tree/custom

* Notice: the profile prefix (i.e. parent folder names) are also changed since 2020-08-15 build, you may rename their names before using new binaries when updating from builds before 2020-08-15.

--

New build of HBL-UXP for XP!

Test binary:
IceDove-UXP(mail) https://o.rthost.win/hbl-uxp/icedove.win32-20220514-id-181ea5d-uxp-774750839-xpmod.7z
IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20220514-id-181ea5d-ia-c642e3c-uxp-774750839-xpmod.7z

source repo (excluding UXP):
https://github.com/roytam1/icedove-uxp/tree/winbuild
https://github.com/roytam1/iceape-uxp/tree/winbuild

for UXP changes please see above.

Link to comment
Share on other sites

New build of post-deprecated Serpent/moebius for XP!
* Notice: This repo will not be built on regular schedule, and changes are experimental as usual.
** Current moebius patch level should be on par with 52.9, but some security patches can not be applied/ported due to source milestone differences between versions.

Test binary:
Win32 http://o.rthost.win/basilisk/basilisk55-win32-git-20220514-afc5f1ab9-xpmod.7z
Win64 http://o.rthost.win/basilisk/basilisk55-win64-git-20220514-afc5f1ab9-xpmod.7z

repo: https://github.com/roytam1/basilisk55

Repo changes:
- import from UXP: about:profiles - fix "Launch profile in new browser" (added "-no-remote" for Windows) (54a727b3) (a01476644)
- pref: add CSS grid pref (dfbe0bc8b)
- partly imported from UXP: Issue #1891 - Add Apple Silicon (ARM64) support. (fd04893c) (79cc4fcd6)
- import from UXP: Issue #1509 - Invalidate previous result when datalist is changed. (046b81d0) (afc5f1ab9)

Link to comment
Share on other sites

New NewMoon 27 Build!

32bit https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20220514-646c78a9d0-xpmod.7z
32bit SSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20220514-646c78a9d0-xpmod-sse.7z
32bit noSSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20220514-646c78a9d0-xpmod-ia32.7z

64bit https://o.rthost.win/palemoon/palemoon-27.10.0.win64-git-20220514-646c78a9d0-xpmod.7z

source repo: https://github.com/roytam1/palemoon27

repo changes since my last build:
- partly import changes from `dev' branch of rmottola/Arctic-Fox:
 - Bug 1181518 - Change the reason for memory-pressure fired during priority change. r=gsvelto (03a726dd82)
 - Bug 1128472 - Part 1. Mac and Win for model, stepping, cores, cache, cpu speed; VM max on Win only, vendor on Mac only. r=gfritzsche (0e843a3e0b)
 - Bug 1128472 - Part 2. Linux support. r=gfritzsche (887ba30869)
 - Bug 1188983 - mozilla::Tokenizer improvements, r=nfroyd (4b57b84c3d)
 - Bug 1128472 - Part 3. Vendor string on windows. r=aklotz (852d4893c9)
 - fix typo (18d57dc0ee)
 - Bug 1350908 - Upgrade Hunspell to version 1.6.1. r=masayuki (54b6e9c049)
 - Bug 1184298 - Remove a spammy spellchecker warning (1f9a8c8227)
 - Bug 1170484 - Use {Begin,End}PlaceHolderTransaction from mozInlineSpellCheck::ReplaceWord. r=ehsan (8e19083cc9) (5628de57cc)
- import changes from `dev' branch of rmottola/Arctic-Fox:
 - Bug 1176681 - Make character buffer allocations in the HTML5 tree builder fallible. r=wchen. (f289384f90)
 - Bug 1142400 - Separate padding calculation in Get{Min,Pref}ISize and Reflow of nsBulletFrame. r=dbaron (e08bee6a1d)
 - Bug 1187432 - Avoid scheduling main-thread paints for scrolls handled by apz. r=tn (422d9e0c64)
 - Bug 1172450 - Size and position the dropdown arrow properly in vertical writing modes. r=smontagu (73c1464a6b)
 - Bug 1201529 - Ensure that zoomable scrollframes return true from WantAsyncScroll(). r=botond (7adb05b491)
 - Bug 1174553 part 1 - Add a new flag (BAIL_IF_REFLOW_NEEDED) for IntrinsicForWM() that makes it return early with a NS_INTRINSIC_WIDTH_UNKNOWN result if a reflow is needed to determine the child's correct BSize. r=dholbert (221b586fe0)
 - Bug 1174546 part 1 - Introduce nsLayoutUtils::MinSizeContributionForAxis which calculates an intrinsic size contribution from aFrame's 'min-width' property (or 'min-height' if the given axis is vertical) and the corresponding border, padding and margin values. r=jfkthame (c81d0b5aae)
 - Bug 1174553 part 2 - Move the AddPercents function into a static method in the nsLayoutUtils class. r=dholbert (18b1153de7)
 - Bug 1151212 part 1 - [css-grid] Introduce a few local structs (GridReflowState, Tracks, TrackSizingFunctions) to make it easier to pass around data. r=dholbert (10d9a635a6)
 - Bug 1151212 part 2 - [css-grid] Introduce a local GridItemInfo struct for holding a grid item's GridArea and other things. Put two nsTArrays of those in the grid container frame, one for normal flow items and one for abs.pos. grid-aligned descendants. Add a GridItemIndex method on the grid item iterator to return the index for the current item. r=dholbert (f4df44e43c)
 - Bug 1161038 - [css-grid] Make kAutoLine not clash with translated grid lines. r=dholbert (a467a13270)
 - Bug 1174546 part 2 - [css-grid] Implement the 'auto' min-sizing function in Grid layout. r=jfkthame (bf6d3ab2b3)
 - Bug 1174553 part 3 - [css-grid] Implement the 'min-content' / 'max-content' sizing functions in layout. r=dholbert (152e139615)
 - Bug 1151212 part 3 - [css-grid] Implement the "Resolve Intrinsic Track Sizes" algorithm. r=dholbert (710657b5c2)
 - Bug 1176619 - [css-grid] Implement the "Maximize Tracks" algorithm. r=dholbert (882da4b57e)
 - Bug 1176621 - [css-grid] Implement "Stretch Flexible Tracks" and associated algorithms. r=dholbert (5737f5fb47)
 - Bug 1174574 part 1 - [css-grid] Move the guts of nsGridContainerFrame::CalculateTrackSizes into a Tracks method. r=dholbert (871ca8dca6)
 - Bug 1174574 part 2 - [css-grid] Implement intrinsic sizing for grid containers (aka GetMinISize/GetPrefISize). r=dholbert (0958f2ad77)
 - Bug 1174553 part 5 - [css-grid] Replace the ambiguous Dimension with LogicalAxis. r=dholbert (15afa20c61)
 - Bug 1194892 - [css-grid] "span * / span *" should be treated as "auto / auto" for abs.pos. grid items. r=dholbert (9b229d7e07)
 - Bug 1194888 - [css-grid] A line outside the existing grid should be treated as 'auto' for abs.pos (10.1). r=dholbert (7bd2426be2)
 - Bug 1204585 part 2 - [css-grid] abs.pos. child position reftests. (fbf2d4e37a)
 - Bug 1206703 - [css-grid] In an empty grid all lines should be treated as 'auto' for abs.pos. items, i.e. snap to the padding edge. r=dholbert (42aeeb368f)
 - Bug 1204585 part 1 - [css-grid] Use the grid area's size when converting to physical coordinates for abs.pos. items. r=dholbert (ad68e0bab1)
 - Bug 1164918 - Allow multiple '.' per cell in grid-template-areas. r=dholbert (db6420ebc5)
 - [css-grid] Use a smaller font-size to make sure the rendering fits within the reftest snapshot area. (minor test changes only, no bug, r=me) (4868bd81c9)
 - Bug 1151212 part 4 - [css-grid] Tests for intrinsic track sizing and intrinsic grid container sizing (bug 1174574). (3b60858334)
 - Bug 1176621 part 2 - [css-grid] Tests for flex track sizing. (fb507cae8e)
 - Bug 1151212 - [css-grid] Tests for <flex> min-sizing. (a74a1bf328)
 - Bug 1174504 - Logical-coordinate versions of nsIFrame::SetSize should maintain the frame's logical position. r=smontagu (f053a277bf) (e8d74fa3c4)
- import changes from `dev' branch of rmottola/Arctic-Fox:
 - Bug 1143130 - Initialize nsIFrame::ContentOffsets members, and some additional cleanup. r=roc (334109d125)
 - Bug 1185436 - Mark DumpFrameTree() and DumpFrameTreeLimited() const. r=roc (f444841ce7)
 - Bug 1163328 - Tests for mozilla::Tuple. r=froydnj (9bdf4a67eb)
 - Bug 1184385 - Add a Tie() utility function for tuples (the equivalent of std::tie()) to MFBT. r=froydnj (a683a079e7)
 - Bug 1186315 - Fix TestTuple error and add it into testing list. r=nfroyd (8ea986d022)
 - Bug 1185706 - support Tie() for mozilla::Pair. r=froydnj (2a74853496)
 - Bug 1186126 - Note incompatibility with NSPR printf-like functions. r=nfroyd (eb3aa88cd3)
 - Bug 1188895 - Replace U+0A00 with U+0200 in MacroForEach.h. r=Ms2ger (e63d0be26f)
 - Bug 1182370 - _BitScan* does not modify *pIndex if input is zero. - r=waldo (3c1280da48)
 - Bug 1193600 - Add Clamp and IsPowerOfTwo to MFBT. - r=waldo (7e5e321a74)
 - Bug 1139036 - Bind all symbols from libmozglue.dylib when it is loaded. r=ted (c948da5c6d)
 - bug 1198226 - Add HOST_{CFLAGS,CXXFLAGS,DEFINES} support to mozbuild frontend+recursive make backend. r=mshal (c5558cbf4c)
 - bug 1198226 - Move HOST_{C,CXX}FLAGS to moz.build HOST_{CFLAGS,CXXFLAGS,DEFINES}. r=mshal (031909f24a)
 - bug 1198226 - Add HOST_{C,CXX}FLAGS recursive make varible blacklist. r=mshal (c808385c2f)
 - Bug 1204134 (attempt 2) - Fix and disallow warnings in config/moz.build. r=glandium. (e1a21ccade)
 - code style (374f57dbea)
 - Bug 1184284 - Remove txToRemove warning from nsSHistory::RemoveDuplicate. r=smaug (14f02229d5)
 - Bug 1203379 - Fix indentation of gfxWordCacheTest.cpp. r=jrmuizel. (c04b07ce17)
 - Bug 1203427 (part 1) - Add nsExpirationTracker::mName. r=froydnj. (974b39f117)
 - Bug 1203427 (part 2) - Remove an argument to nsTimeout::InitTimer. r=mccr8. (f6f196c26c)
 - Bug 1203809 - pass textperf obj into gfxFontGroup constructor. r=m_kato (1ea2f5cfd2)
 - Bug 1203427 (part 3) - Change order of InitCommon() arguments. r=froydnj. (07e6c9b5ca)
 - Bug 1203427 (part 4) - Remove trailing whitespace from nsITimer.idl. r=froydnj. (df4473f30a)
 - Bug 1186112 - Get rid of the #define'd constants in BMPFileHeaders.h. r=tn (c18103f391) (646c78a9d0)

Link to comment
Share on other sites

New regular/weekly KM-Goanna release:
https://o.rthost.win/kmeleon/KM76.4.6-Goanna-20220514.7z

Changelog:

Out-of-tree changes:
* update Goanna3 to git 5f65eee25...646c78a9d0:
- partly import changes from `dev' branch of rmottola/Arctic-Fox:
 - Bug 1181518 - Change the reason for memory-pressure fired during priority change. r=gsvelto (03a726dd82)
 - Bug 1128472 - Part 1. Mac and Win for model, stepping, cores, cache, cpu speed; VM max on Win only, vendor on Mac only. r=gfritzsche (0e843a3e0b)
 - Bug 1128472 - Part 2. Linux support. r=gfritzsche (887ba30869)
 - Bug 1188983 - mozilla::Tokenizer improvements, r=nfroyd (4b57b84c3d)
 - Bug 1128472 - Part 3. Vendor string on windows. r=aklotz (852d4893c9)
 - fix typo (18d57dc0ee)
 - Bug 1350908 - Upgrade Hunspell to version 1.6.1. r=masayuki (54b6e9c049)
 - Bug 1184298 - Remove a spammy spellchecker warning (1f9a8c8227)
 - Bug 1170484 - Use {Begin,End}PlaceHolderTransaction from mozInlineSpellCheck::ReplaceWord. r=ehsan (8e19083cc9) (5628de57cc)
- import changes from `dev' branch of rmottola/Arctic-Fox:
 - Bug 1176681 - Make character buffer allocations in the HTML5 tree builder fallible. r=wchen. (f289384f90)
 - Bug 1142400 - Separate padding calculation in Get{Min,Pref}ISize and Reflow of nsBulletFrame. r=dbaron (e08bee6a1d)
 - Bug 1187432 - Avoid scheduling main-thread paints for scrolls handled by apz. r=tn (422d9e0c64)
 - Bug 1172450 - Size and position the dropdown arrow properly in vertical writing modes. r=smontagu (73c1464a6b)
 - Bug 1201529 - Ensure that zoomable scrollframes return true from WantAsyncScroll(). r=botond (7adb05b491)
 - Bug 1174553 part 1 - Add a new flag (BAIL_IF_REFLOW_NEEDED) for IntrinsicForWM() that makes it return early with a NS_INTRINSIC_WIDTH_UNKNOWN result if a reflow is needed to determine the child's correct BSize. r=dholbert (221b586fe0)
 - Bug 1174546 part 1 - Introduce nsLayoutUtils::MinSizeContributionForAxis which calculates an intrinsic size contribution from aFrame's 'min-width' property (or 'min-height' if the given axis is vertical) and the corresponding border, padding and margin values. r=jfkthame (c81d0b5aae)
 - Bug 1174553 part 2 - Move the AddPercents function into a static method in the nsLayoutUtils class. r=dholbert (18b1153de7)
 - Bug 1151212 part 1 - [css-grid] Introduce a few local structs (GridReflowState, Tracks, TrackSizingFunctions) to make it easier to pass around data. r=dholbert (10d9a635a6)
 - Bug 1151212 part 2 - [css-grid] Introduce a local GridItemInfo struct for holding a grid item's GridArea and other things. Put two nsTArrays of those in the grid container frame, one for normal flow items and one for abs.pos. grid-aligned descendants. Add a GridItemIndex method on the grid item iterator to return the index for the current item. r=dholbert (f4df44e43c)
 - Bug 1161038 - [css-grid] Make kAutoLine not clash with translated grid lines. r=dholbert (a467a13270)
 - Bug 1174546 part 2 - [css-grid] Implement the 'auto' min-sizing function in Grid layout. r=jfkthame (bf6d3ab2b3)
 - Bug 1174553 part 3 - [css-grid] Implement the 'min-content' / 'max-content' sizing functions in layout. r=dholbert (152e139615)
 - Bug 1151212 part 3 - [css-grid] Implement the "Resolve Intrinsic Track Sizes" algorithm. r=dholbert (710657b5c2)
 - Bug 1176619 - [css-grid] Implement the "Maximize Tracks" algorithm. r=dholbert (882da4b57e)
 - Bug 1176621 - [css-grid] Implement "Stretch Flexible Tracks" and associated algorithms. r=dholbert (5737f5fb47)
 - Bug 1174574 part 1 - [css-grid] Move the guts of nsGridContainerFrame::CalculateTrackSizes into a Tracks method. r=dholbert (871ca8dca6)
 - Bug 1174574 part 2 - [css-grid] Implement intrinsic sizing for grid containers (aka GetMinISize/GetPrefISize). r=dholbert (0958f2ad77)
 - Bug 1174553 part 5 - [css-grid] Replace the ambiguous Dimension with LogicalAxis. r=dholbert (15afa20c61)
 - Bug 1194892 - [css-grid] "span * / span *" should be treated as "auto / auto" for abs.pos. grid items. r=dholbert (9b229d7e07)
 - Bug 1194888 - [css-grid] A line outside the existing grid should be treated as 'auto' for abs.pos (10.1). r=dholbert (7bd2426be2)
 - Bug 1204585 part 2 - [css-grid] abs.pos. child position reftests. (fbf2d4e37a)
 - Bug 1206703 - [css-grid] In an empty grid all lines should be treated as 'auto' for abs.pos. items, i.e. snap to the padding edge. r=dholbert (42aeeb368f)
 - Bug 1204585 part 1 - [css-grid] Use the grid area's size when converting to physical coordinates for abs.pos. items. r=dholbert (ad68e0bab1)
 - Bug 1164918 - Allow multiple '.' per cell in grid-template-areas. r=dholbert (db6420ebc5)
 - [css-grid] Use a smaller font-size to make sure the rendering fits within the reftest snapshot area. (minor test changes only, no bug, r=me) (4868bd81c9)
 - Bug 1151212 part 4 - [css-grid] Tests for intrinsic track sizing and intrinsic grid container sizing (bug 1174574). (3b60858334)
 - Bug 1176621 part 2 - [css-grid] Tests for flex track sizing. (fb507cae8e)
 - Bug 1151212 - [css-grid] Tests for <flex> min-sizing. (a74a1bf328)
 - Bug 1174504 - Logical-coordinate versions of nsIFrame::SetSize should maintain the frame's logical position. r=smontagu (f053a277bf) (e8d74fa3c4)
- import changes from `dev' branch of rmottola/Arctic-Fox:
 - Bug 1143130 - Initialize nsIFrame::ContentOffsets members, and some additional cleanup. r=roc (334109d125)
 - Bug 1185436 - Mark DumpFrameTree() and DumpFrameTreeLimited() const. r=roc (f444841ce7)
 - Bug 1163328 - Tests for mozilla::Tuple. r=froydnj (9bdf4a67eb)
 - Bug 1184385 - Add a Tie() utility function for tuples (the equivalent of std::tie()) to MFBT. r=froydnj (a683a079e7)
 - Bug 1186315 - Fix TestTuple error and add it into testing list. r=nfroyd (8ea986d022)
 - Bug 1185706 - support Tie() for mozilla::Pair. r=froydnj (2a74853496)
 - Bug 1186126 - Note incompatibility with NSPR printf-like functions. r=nfroyd (eb3aa88cd3)
 - Bug 1188895 - Replace U+0A00 with U+0200 in MacroForEach.h. r=Ms2ger (e63d0be26f)
 - Bug 1182370 - _BitScan* does not modify *pIndex if input is zero. - r=waldo (3c1280da48)
 - Bug 1193600 - Add Clamp and IsPowerOfTwo to MFBT. - r=waldo (7e5e321a74)
 - Bug 1139036 - Bind all symbols from libmozglue.dylib when it is loaded. r=ted (c948da5c6d)
 - bug 1198226 - Add HOST_{CFLAGS,CXXFLAGS,DEFINES} support to mozbuild frontend+recursive make backend. r=mshal (c5558cbf4c)
 - bug 1198226 - Move HOST_{C,CXX}FLAGS to moz.build HOST_{CFLAGS,CXXFLAGS,DEFINES}. r=mshal (031909f24a)
 - bug 1198226 - Add HOST_{C,CXX}FLAGS recursive make varible blacklist. r=mshal (c808385c2f)
 - Bug 1204134 (attempt 2) - Fix and disallow warnings in config/moz.build. r=glandium. (e1a21ccade)
 - code style (374f57dbea)
 - Bug 1184284 - Remove txToRemove warning from nsSHistory::RemoveDuplicate. r=smaug (14f02229d5)
 - Bug 1203379 - Fix indentation of gfxWordCacheTest.cpp. r=jrmuizel. (c04b07ce17)
 - Bug 1203427 (part 1) - Add nsExpirationTracker::mName. r=froydnj. (974b39f117)
 - Bug 1203427 (part 2) - Remove an argument to nsTimeout::InitTimer. r=mccr8. (f6f196c26c)
 - Bug 1203809 - pass textperf obj into gfxFontGroup constructor. r=m_kato (1ea2f5cfd2)
 - Bug 1203427 (part 3) - Change order of InitCommon() arguments. r=froydnj. (07e6c9b5ca)
 - Bug 1203427 (part 4) - Remove trailing whitespace from nsITimer.idl. r=froydnj. (df4473f30a)
 - Bug 1186112 - Get rid of the #define'd constants in BMPFileHeaders.h. r=tn (c18103f391) (646c78a9d0)

* Notice: the changelog above may not always applicable to XULRunner code which K-Meleon uses.

A goanna3 source tree that has kmeleon adaption patch applied is available here: https://github.com/roytam1/palemoon27/tree/kmeleon76

Link to comment
Share on other sites

4 hours ago, Mathwiz said:
13 hours ago, VistaLover said:

Well, each Saturday's releases do come with a changelog (Release Notes)

13 hours ago, NotHereToPlayGames said:

I don't read them.  99% of them make ZERO sense to me.  I wish they were in a "hide/show" toggle-box because I kinda see them as a pain to scroll, scroll, scroll, scroll, scroll 

I second that motion. The change log is usually quite long and very technical; hard to understand even for those of us who dabble in programming. Putting it in a spoiler tag would let us refer to it if need be but save our scroll wheels if not....

Even better would be a plain-language "executive summary" of the changes, but I'm sure that's out of the question. It would have to come from upstream....

It's a commit log, not something of vast interest to end users. Imagine Ubuntu folks posting commit logs of all software it ships at release.:buehehe: Upstream does write changelogs, eg. http://www.palemoon.org/releasenotes.shtml

But what is there to write about what are basically "test" releases compiled from trunk code? Changelogs are written when you release stable and tested code. We never give out nightly builds to customers where I work. When there's something important, relevant code is merged into the latest stable release and intermediate release is made.

Link to comment
Share on other sites

On 5/14/2022 at 7:59 AM, UCyborg said:

It's a commit log, not something of vast interest to end users.

Yes, for latest UXP builds it's a transcript from: 

https://github.com/roytam1/UXP/compare/e207b5a...7747508

Code imported from "upstream" issues has the corresponding issue number clearly indicated, e.g. 
"Issue #1509 - Invalidate previous result when datalist is changed."
One can find more details regarding that issue (and the "bugs" it potentially fixes... or not :sneaky: ) 
by looking it up in the upstream issue tracker, e.g. 
https://repo.palemoon.org/MoonchildProductions/UXP/issues/1509

Obviously, much of this is "Greek" (:P) to most, non-coder, users, but surely "big" things, like support for optional chaining operator (?.), are cleary marked ;) ; all one needs do is simply "comb" that commit log for resolved bugs that would positively affect one's own worklow... 

On 5/14/2022 at 7:59 AM, UCyborg said:

But what is there to write about what are basically "test" releases compiled from trunk code?
Changelogs are written when you release stable and tested code.

FWIW/OTOH, even Mozilla go into the trouble (?) of composing some form of "Release Notes" for their Firefox Nightly "trunk" builds (updated twice over the course of 24h) in, what @Mathwiz called, a plain-language "executive summary" of changes, e.g. 

https://www.mozilla.org/en-US/firefox/100.0a1/releasenotes/

with the "disclaimer": 

Quote

Firefox Nightly gets updated every day and as a consequence, the release notes for the Nightly channel are updated continuously to reflect features that have reached sufficient maturity to benefit from community feedback and bug reports.

Warning: Features listed here may or may not make a final release of Firefox.

:) ; a separate set of "Release Notes" is also available for pure developers/coders
https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/100

Edited by VistaLover
Link to comment
Share on other sites

I think the bigger point is whether they should be within "spoiler" tags or not.

Would reduce a TON of scrolling and make the thread more "efficient".

But on the other hand, I have seen the "spoiler" tag not really work correctly over the years (but the forum software has been updated at least twice since then, that I'm aware of).

Link to comment
Share on other sites

2 hours ago, VistaLover said:
13 hours ago, UCyborg said:

But what is there to write about what are basically "test" releases compiled from trunk code?
Changelogs are written when you release stable and tested code.

FWIW/OTOH, even Mozilla go into the trouble (?) of composing some form of "Release Notes" for their Firefox Nightly "trunk" builds (updated twice over the course of 24h) in, what @Mathwiz called, a plain-language "executive summary" of changes

Yeah, I guess they do. I was tired and not making much sense. 99,99% of the time I don't really do "nightlies", "betas", "auroras", "canaries", "Windows Insiders" etc. etc.

Software in general changes way too often too fast, even looking only at normal releases. Too much crap to keep up with.

Link to comment
Share on other sites

On 5/9/2022 at 6:38 PM, Mathwiz said:

Some button icons seem messed up in the latest (2022-05-06) St 55:

image.thumb.png.5119018479321d6d4821ba1234836182.png

What it looks like in earlier versions (this is from 2022-04-29):

image.thumb.png.8bfeff15eaede9887f980e6aff1e42cd.png

On 5/11/2022 at 2:29 PM, Mathwiz said:

I reinstalled the UOC Patch to start searching for the problem, and my button icons are still OK. So ... never mind? I'm so confused....

image.thumb.png.2bb3b4fea6ac9810554011305d85d4f8.png

This issue has me even more puzzled than ever. Here's what I've run into so far:

  • I still see the problem in the latest St 55 version.
  • On my home PC running Windows 7, both the 32 and 64 bit versions of St 55 exhibit the problem, regardless of profile, and even in "safe mode" (add-ons disabled).
  • On my work PC, I tested the 64 bit version under Windows 7 and the 32 bit version under Windows XP. Both worked fine. The screen shot above was from my work PC.
  • All versions (working and not) were tested with @looking4awayout's UOC patch, but removing it turned out to have no effect either.
  • My home PC has text set at 150% while my work PC is at the default 100%. But setting my home PC text size to 100% had no effect either.
  • I was able to regain the button icons on my home PC by replacing basilisk.exe, xul.dll, and a couple of .ini files, with the 4/29 versions of those files. Of course, that reverts many of the fixes @roytam1 made since 4/29, so it's definitely not a good solution. Reverting other files, without reverting those, doesn't help (I tried them all).

Conclusion: something about my home PC, in conjunction with one of the many changes made between 4/29 and 5/6, causes this problem. Nothing else seems to matter.

My home PC has an oldish AMD 2-core CPU with an integrated ATI Radeon GPU. My work PC is a Dell with a slightly newer Intel 4-core CPU; not sure about the GPU.

BTW, I consider myself lucky that reverting files worked at all; I was just trying to narrow down the location of the problem.

Link to comment
Share on other sites

3 hours ago, Mathwiz said:

All versions (working and not) were tested with @looking4awayout's UOC patch, but removing it turned out to have no effect either.

What the heck is a "UOC patch" ?  Disregard - found it  --  https://msfn.org/board/topic/178306-the-uoc-patch-optimize-firefox-and-derivatives-for-old-hardware/

 

3 hours ago, Mathwiz said:

Conclusion: something about my home PC, in conjunction with one of the many changes made between 4/29 and 5/6, causes this problem.

Did you alter any of the home PC fonts?  ie, experiment with "emoji's" ?

Edited by NotHereToPlayGames
Link to comment
Share on other sites

Mathwiz wrote:
>I second that motion. The change log is usually quite long and very technical;
> hard to understand even for those of us who dabble in programming.
> Putting it in a spoiler tag would let us refer to it if need be but save our scroll wheels if not...

No, please not SPOILER!
That tends to be hidden completely for old browsers, and not sure if also hindering page-search or archiving.
Perhaps something else - "code"? But that increases the size yet more, using ultrawide Courier-fonts.
Another...?
(That said, I'd be surprised if RT changes anything at all only for reading convenience)

But being a selfhelper, couldn't resist playing a bit now ;-)

Tweak-1:
This CSS filters all comments written by RT, then limits all single P-elements to a max height and if too long, shows a scrollbar:
body.ipsApp article.ipsComment div[data-quotedata*='roytam1'] div.cPost_contentWrap p{
max-height: 400px !important;
overflow-y: auto !important;
}
CSS-variations for example: remove author-requirement, or limit complete-comment height instead of single P-elements

Tweak-2:
This JAVASCRIPT (bookmarklet?) filters all comments written by RT, but (unlike above) takes the complete comment text. Then checks if the TEXT "- Bug " is contained more often than 8x. Only THOSE comments get limited with a scrollbar:
var c="body.ipsApp article.ipsComment div[data-quotedata*='roytam1']";
var j, el, lg0, lg2, x, LIST=document.querySelectorAll(c);
for (j=0; j < LIST.length; j++){
el=LIST[ j].querySelector("div[data-role='commentContent']");
lg0=el.textContent.length;
lg2=el.textContent.replace(/- Bug /gi, '').length;
x =(lg0 - lg2)/6;
if (x > 8) {
el.style.maxHeight='400px';
void(el.style.overflow='auto');
/* just for TESTING! Remove line: */
void(el.style.backgroundColor='yellow');
}}
JS-variations: remove author requirement, choose another max-height, choose another TEXT, choose another hits-limit
.
Edited by siria
Link to comment
Share on other sites

23 hours ago, siria said:

Mathwiz wrote:
>I second that motion. The change log is usually quite long and very technical;
> hard to understand even for those of us who dabble in programming.
> Putting it in a spoiler tag would let us refer to it if need be but save our scroll wheels if not...

No, please not SPOILER!
That tends to be hidden completely for old browsers, and not sure if also hindering page-search or archiving.
Perhaps something else - "code"? But that increases the size yet more, using ultrawide Courier-fonts.
Another...?
(That said, I'd be surprised if RT changes anything at all only for reading convenience)

But being a selfhelper, couldn't resist playing a bit now ;-)

Tweak-1:
This CSS filters all comments written by RT, then limits all single P-elements to a max height and if too long, shows a scrollbar:
body.ipsApp article.ipsComment div[data-quotedata*='roytam1'] div.cPost_contentWrap p{
max-height: 400px !important;
overflow-y: auto !important;
}
CSS-variations for example: remove author-requirement, or limit complete-comment height instead of single P-elements

Tweak-2:
This JAVASCRIPT (bookmarklet?) filters all comments written by RT, but (unlike above) takes the complete comment text. Then checks if the TEXT "- Bug " is contained more often than 8x. Only THOSE comments get limited with a scrollbar:
var c="body.ipsApp article.ipsComment div[data-quotedata*='roytam1']";
var j, el, lg0, lg2, x, LIST=document.querySelectorAll(c);
for (j=0; j < LIST.length; j++){
el=LIST[ j].querySelector("div[data-role='commentContent']");
lg0=el.textContent.length;
lg2=el.textContent.replace(/- Bug /gi, '').length;
x =(lg0 - lg2)/6;
if (x > 8) {
el.style.maxHeight='400px';
void(el.style.overflow='auto');
/* just for TESTING! Remove line: */
void(el.style.backgroundColor='yellow');
}}
JS-variations: remove author requirement, choose another max-height, choose another TEXT, choose another hits-limit
.

Thanks for the CSS!

Works really well. :)

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...