Path: csiph.com!weretis.net!feeder8.news.weretis.net!reader5.news.weretis.net!news.solani.org!.POSTED!not-for-mail
From: Richmond <dnomhcir@gmx.com>
Newsgroups: alt.comp.software.firefox
Subject: Re: Unwanted update to 150 just happened
Date: Wed, 29 Apr 2026 16:54:54 +0100
Organization: Frantic
Message-ID: <82fr4d69td.fsf@example.com>
References: <10sinht$tpvi$1@dont-email.me> <10sisme$vqg1$1@dont-email.me> <n54bahFsmdqU1@mid.individual.net> <e0upukpuk6cs9gv3upar9072uqvamrvula@4ax.com> <10sivi0$10uuo$1@dont-email.me> <10sptp2$311i3$1@dont-email.me> <10sr2ep$3c77i$1@dont-email.me> <10sr8ck$3f3pq$1@dont-email.me> <10srqs8$3jk6e$1@dont-email.me> <cke9cm-st8.ln1@spock.lan> <82jytp6a67.fsf@example.com> <n5enpjFhjn7U1@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain
Injection-Info: solani.org; logging-data="1222677"; mail-complaints-to="abuse@news.solani.org"
User-Agent: Gnus/5.13 (Gnus v5.13)
Cancel-Lock: sha1:wOgrDHKxH2lMyEcaTN35ebsNuQg= sha1:kHuc/4opestQPNWsRvwh8czYBU4=
X-User-ID: eJwNycEBgDAIA8CViiTRjgOp7D+C3veYCvmGKHA4jc4XDk6OrtB/s84GQC9brOpeT7T3qUB9IIIReg==
Xref: csiph.com alt.comp.software.firefox:16948

Andy Burns <usenet@andyburns.uk> writes:

> Richmond wrote:
>
>> You tested whether it blockedabout:config, but you didn't test whether
>> it blocked an update, or if the update altered the json file.
>
> I think dilinger did more than his bit to test stuff, at this point if
> Bev is happy, nobody is likely to go back and find what actually
> happened, but it doesn't sound to me like a stray CR or LF would be
> the cause ...

But how does firefox process json? it may be different code that
processes the update part from the block part.