Re: svn commit: r1936555 - in subversion/site/staging: . blog docs docs/community-guide docs/release-notes pronunciation security style
Ivan Zhakov <[email protected]> Wed, 29 Jul 2026 16:49:15 +0300
| Newsgroups | gmane.comp.version-control.subversion.devel |
|---|---|
| Message-ID | <CAPZho0_-_xWBqvz_-zU9shOsrDpWBiLGFhrS7axxomfB8iVKvQ@mail.gmail.com> |
--0000000000005819c80657c0393d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, 29 Jul 2026 at 15:15, Daniel Sahlberg <[email protected]> wrote: > Den ons 29 juli 2026 kl 12:58 skrev Branko =C4=8Cibej <[email protected]>: > >> On 29. 7. 2026 11:38, Ivan Zhakov wrote: >> >> On Tue, 28 Jul 2026 at 19:51, Nathan Hartman <[email protected]> >> wrote: >> >>> On Tue, Jul 28, 2026 at 10:57=E2=80=AFAM Ivan Zhakov <[email protected]> = wrote: >>> > >>> > On Tue, 28 Jul 2026 at 17:11, Nathan Hartman <[email protected]= m> >>> wrote: >>> >> >>> >> On Fri, Jul 24, 2026 at 12:40=E2=80=AFPM <[email protected]> wrote: >>> >> > >>> >> > Author: ivan >>> >> > Date: Fri Jul 24 16:39:48 2026 >>> >> > New Revision: 1936555 >>> >> > >>> >> > Log: >>> >> > In site/staging: >>> >> > >>> >> > Use 'content' CSS property to add section link symbol. >>> >> > >>> >> > * style/site.css >>> >> > (.sectionlink::before): New class. Add 'pilcrow' symbol via >>> 'content' CSS >>> >> > property. >>> >> > >>> >> > * blog/2006-09-10-EnhancingSubversionServer.html >>> >> > * blog/2007-03-27-authz-and-anon-authn-agony.html >>> >> > * blog/2007-06-13-merge_auditing.html >>> >> > * blog/2008-03-29-merging-from-foreign-repositories.html >>> >> > * blog/2008-05-06-merge-info.html >>> >> > * blog/2009-11-19-where-did-that-mergeinfo-come-from.html >>> >> > * blog/2012-10-24-reducing_network_traffic_in_subversion_1-8.html >>> >> > * >>> blog/2013-06-24-repository-dictated-configuration-part-1-inheritable-pr= operties.html >>> >> > * >>> blog/2013-06-25-repository-dictated-configuration-part-2-autoprops.html >>> >> > * >>> blog/2013-06-26-repository-dictated-configuration-part-3-global-ignores= .html >>> >> > * blog/2013-06-28-foreign-repository-copies.html >>> >> > * blog/index.html >>> >> > * contributing.html >>> >> > * docs/community-guide/building.part.html >>> >> > * docs/community-guide/conventions.part.html >>> >> > * docs/community-guide/debugging.part.html >>> >> > * docs/community-guide/general.part.html >>> >> > * docs/community-guide/issues.part.html >>> >> > * docs/community-guide/l10n.part.html >>> >> > * docs/community-guide/mailing-lists.part.html >>> >> > * docs/community-guide/releasing.part.html >>> >> > * docs/community-guide/roles.part.html >>> >> > * docs/community-guide/web.part.html >>> >> > * docs/index.html >>> >> > * docs/release-notes/1.1.html >>> >> > * docs/release-notes/1.10.html >>> >> > * docs/release-notes/1.11.html >>> >> > * docs/release-notes/1.12.html >>> >> > * docs/release-notes/1.13.html >>> >> > * docs/release-notes/1.14.html >>> >> > * docs/release-notes/1.15.html >>> >> > * docs/release-notes/1.2.html >>> >> > * docs/release-notes/1.3.html >>> >> > * docs/release-notes/1.4.html >>> >> > * docs/release-notes/1.5.html >>> >> > * docs/release-notes/1.6.html >>> >> > * docs/release-notes/1.6.zh.html >>> >> > * docs/release-notes/1.7.html >>> >> > * docs/release-notes/1.8.html >>> >> > * docs/release-notes/1.9.html >>> >> > * docs/release-notes/index.html >>> >> > * download.html >>> >> > * faq.html >>> >> > * faq.ja.html >>> >> > * faq.zh.html >>> >> > * features.html >>> >> > * ideas.html >>> >> > * index.html >>> >> > * mailing-lists.html >>> >> > * news.html >>> >> > * opw.html >>> >> > * packages.html >>> >> > * pronunciation/index.html >>> >> > * quick-start.html >>> >> > * reporting-issues.html >>> >> > * roadmap.html >>> >> > * security/index.html >>> >> > * source-code.html >>> >> > Remove "¶" from section links: we add it via 'content' CSS >>> property. >>> >> >>> >> Hi, >>> >> >>> >> Sorry, this change doesn't seem to work on Firefox. >>> >> >>> >> I am using the very latest Firefox, version 153.0.1. >>> >> >>> > I am using Firefox 153.0.1 and it works for me. >>> > >>> > I have also tested Microsoft Edge 150.0.4078.99 and it also works. >>> > >>> > May it's some kind of caching issue? >>> >>> >>> You are correct, it was a caching issue. This confused me because I >>> believed that I had force-reloaded the page. However, I just checked >>> and it turns out that Cmd + R only reloads the HTML. You have to press >>> Cmd + Shift + R to also reload stylesheets. I had forgotten this. >>> >>> Strangely, an earlier change of the stylesheets (to add td.success, >>> td.warning, td.danger) took effect here without any special action on >>> my part. >>> >>> This issue is rather annoying. I was searching for a reliable method >>> to force browsers to reload CSS when it changes without forcing a >>> reload every time the page is accessed. One StackOverflow page [1] >>> contains an entire debate about this. The most simplistic idea from >>> that page is to rename the CSS file with some sort of monotonically >>> increasing version number in the filename each time the file is >>> edited. This method would always work; the downside is that it would >>> necessitate changes to all the files across the site, each time we >>> edit the CSS. That could be annoying for us. >>> >>> An alternative solution would be to add a query argument and increment >> it on every CSS change. Something like this: >> <link rel=3D"stylesheet" href=3D"/style/site.css?v=3D1" type=3D"text/css= " >> media=3D"all"> >> >> But we would still have to update 63 HTML files on every CSS change. I'm >> not sure it is worth it, but I can do this >> >> >> >> It's not worth it. Some browsers are just notorious for caching too much= . >> That is not the case for Firefox =E2=80=93 the difference between ^R/Shi= ft-^R (or >> =E2=8C=98R/Shift-=E2=8C=98R on the Mac) is well known. Safari, on the ot= her hand, is way >> too smart, it doesn't have an equivalent to Shift-=E2=8C=98R and will ha= ppily cache >> CSS and favicons and such even when they no longer exist at the source..= . >> >> TL;DR: This will only happen to people who are regularly tracking the >> changing staging web site. >> > > It will also happen to anyone who regularly check the main website, > whenever we merge this kind of changes. I have no idea how long it takes > before the web browsers refresh a cached resource. > > That said, I don't think it is worth changing 63 HTML files on every CSS > change. > > One possible solution: We already use mod_ssi to <!-- #include --> other > files. One possible solution would be to have the head as a separate > include. If I understand mod_ssi correctly, we could <!-- #set var=3D"tit= le" > value=3D"Some title" --> and then <title><!-- #echo var=3D"title" --></ti= tle> > in the header file. That way we only need to update the header-include fi= le. > > Yes, we can use mod_ssi, but this will require mod_ssi for local testing. I find it very convenient to test my changes without even starting the server. --=20 Ivan Zhakov --0000000000005819c80657c0393d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">On Wed, 29 Jul 2026 at 1= 5:15, Daniel Sahlberg <<a href=3D"mailto:[email protected]" ta= rget=3D"_blank">[email protected]</a>> wrote:</div><div class= =3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px = 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir= =3D"ltr"><div dir=3D"ltr"><span style=3D"background-color:transparent">Den = ons 29 juli 2026 kl 12:58 skrev Branko =C4=8Cibej <<a href=3D"mailto:bra= [email protected]" target=3D"_blank">[email protected]</a>>:</span></div><div= class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0p= x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u= ></u> =20 =20 =20 <div> <div>On 29. 7. 2026 11:38, Ivan Zhakov wrote:<br> </div> <blockquote type=3D"cite"> =20 <div dir=3D"ltr"> <div dir=3D"ltr"> <div dir=3D"ltr">On Tue, 28 Jul 2026 at 19:51, Nathan Hartman <<a href=3D"mailto:[email protected]" target=3D"_blan= k">[email protected]</a>> wrote:</div> <div class=3D"gmail_quote"> <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0= .8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Tue, Jul 28, 2026 at 10:57=E2=80=AFAM Ivan Zhakov <<a href= =3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>> wrote:<br> ><br> > On Tue, 28 Jul 2026 at 17:11, Nathan Hartman <<a href= =3D"mailto:[email protected]" target=3D"_blank">hartman.nathan@gmail= .com</a>> wrote:<br> >><br> >> On Fri, Jul 24, 2026 at 12:40=E2=80=AFPM <<a href= =3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>> wrote:<br> >> ><br> >> > Author: ivan<br> >> > Date: Fri Jul 24 16:39:48 2026<br> >> > New Revision: 1936555<br> >> ><br> >> > Log:<br> >> > In site/staging:<br> >> ><br> >> > Use 'content' CSS property to add secti= on link symbol.<br> >> ><br> >> > * style/site.css<br> >> >=C2=A0 =C2=A0(.sectionlink::before): New class. = Add 'pilcrow' symbol via 'content' CSS<br> >> >=C2=A0 =C2=A0 property.<br> >> ><br> >> > * blog/2006-09-10-EnhancingSubversionServer.html<br> >> > * blog/2007-03-27-authz-and-anon-authn-agony.html<br> >> > * blog/2007-06-13-merge_auditing.html<br> >> > * blog/2008-03-29-merging-from-foreign-repositories.html<br> >> > * blog/2008-05-06-merge-info.html<br> >> > * blog/2009-11-19-where-did-that-mergeinfo-come-from.html<br> >> > * blog/2012-10-24-reducing_network_traffic_in_subversion_1-8.ht= ml<br> >> > * blog/2013-06-24-repository-dictated-configuration-part-1-inheritable-proper= ties.html<br> >> > * blog/2013-06-25-repository-dictated-configuration-part-2-auto= props.html<br> >> > * blog/2013-06-26-repository-dictated-configuration-part-3-global-ignores.htm= l<br> >> > * blog/2013-06-28-foreign-repository-copies.html<br> >> > * blog/index.html<br> >> > * contributing.html<br> >> > * docs/community-guide/building.part.html<br> >> > * docs/community-guide/conventions.part.html<br= > >> > * docs/community-guide/debugging.part.html<br> >> > * docs/community-guide/general.part.html<br> >> > * docs/community-guide/issues.part.html<br> >> > * docs/community-guide/l10n.part.html<br> >> > * docs/community-guide/mailing-lists.part.html<br> >> > * docs/community-guide/releasing.part.html<br> >> > * docs/community-guide/roles.part.html<br> >> > * docs/community-guide/web.part.html<br> >> > * docs/index.html<br> >> > * docs/release-notes/1.1.html<br> >> > * docs/release-notes/1.10.html<br> >> > * docs/release-notes/1.11.html<br> >> > * docs/release-notes/1.12.html<br> >> > * docs/release-notes/1.13.html<br> >> > * docs/release-notes/1.14.html<br> >> > * docs/release-notes/1.15.html<br> >> > * docs/release-notes/1.2.html<br> >> > * docs/release-notes/1.3.html<br> >> > * docs/release-notes/1.4.html<br> >> > * docs/release-notes/1.5.html<br> >> > * docs/release-notes/1.6.html<br> >> > * docs/release-notes/1.6.zh.html<br> >> > * docs/release-notes/1.7.html<br> >> > * docs/release-notes/1.8.html<br> >> > * docs/release-notes/1.9.html<br> >> > * docs/release-notes/index.html<br> >> > * download.html<br> >> > * faq.html<br> >> > * faq.ja.html<br> >> > * faq.zh.html<br> >> > * features.html<br> >> > * ideas.html<br> >> > * index.html<br> >> > * mailing-lists.html<br> >> > * news.html<br> >> > * opw.html<br> >> > * packages.html<br> >> > * pronunciation/index.html<br> >> > * quick-start.html<br> >> > * reporting-issues.html<br> >> > * roadmap.html<br> >> > * security/index.html<br> >> > * source-code.html<br> >> >=C2=A0 =C2=A0Remove "&para;" from = section links: we add it via 'content' CSS property.<br> >><br> >> Hi,<br> >><br> >> Sorry, this change doesn't seem to work on Firefox.<br> >><br> >> I am using the very latest Firefox, version 153.0.1.<br> >><br> > I am using Firefox 153.0.1 and it works for me.<br> ><br> > I have also tested Microsoft Edge 150.0.4078.99 and it also works.<br> ><br> > May it's some kind of caching issue?<br> <br> <br> You are correct, it was a caching issue. This confused me because I<br> believed that I had force-reloaded the page. However, I just checked<br> and it turns out that Cmd + R only reloads the HTML. You have to press<br> Cmd + Shift + R to also reload stylesheets. I had forgotten this.<br> <br> Strangely, an earlier change of the stylesheets (to add td.success,<br> td.warning, td.danger) took effect here without any special action on<br> my part.<br> <br> This issue is rather annoying. I was searching for a reliable method<br> to force browsers to reload CSS when it changes without forcing a<br> reload every time the page is accessed. One StackOverflow page [1]<br> contains an entire debate about this. The most simplistic idea from<br> that page is to rename the CSS file with some sort of monotonically<br> increasing version number in the filename each time the file is<br> edited. This method would always work; the downside is that it would<br> necessitate changes to all the files across the site, each time we<br> edit the CSS. That could be annoying for us.<br> <br> </blockquote> <span> <div>An alternative solution would be to add a query argument and increment it on every CSS change. Something like this:<br> <link rel=3D"stylesheet" href=3D"/style/s= ite.css?v=3D1" type=3D"text/css" media=3D"all"><br> <br> But we would still have to update 63 HTML files on every CSS change. I'm not sure it is worth it, but I can do this<br> </div> </span></div> </div> </div> </blockquote> <br> <br> It's not worth it. Some browsers are just notorious for caching too much. That is not the case for Firefox =E2=80=93 the difference between ^R/Shift-^R (or =E2=8C=98R/Shift-=E2=8C=98R on the Mac) is well known. = Safari, on the other hand, is way too smart, it doesn't have an equivalent to Shift-=E2=8C=98R and will happily cache CSS and favicons and such even = when they no longer exist at the source...<br> <br> TL;DR: This will only happen to people who are regularly tracking the changing staging web site.<br> </div></blockquote><div><br></div><div>It will also happen to anyone wh= o regularly check the main website, whenever we merge this kind of changes.= I have no idea how long it takes before the web browsers refresh a cached = resource.</div><div><br></div><div>That said, I don't think it is worth= changing 63 HTML files on every CSS change.</div><div><br></div><div>One p= ossible solution: We already use mod_ssi to <!-- #include --> other f= iles. One possible solution would be to have the head as a separate include= . If I understand mod_ssi correctly, we could <!-- #set var=3D"titl= e" value=3D"Some title" --> and then <title><!--= #echo var=3D"title" --></title> in the header file. Tha= t way we only need to update the header-include file.</div><div><br></div><= /div></div></blockquote>Yes, we can use mod_ssi, but this will require mod_= ssi for local testing. I find it very convenient to test my changes without= even starting the server.</div><div class=3D"gmail_quote"><br clear=3D"all= "></div><br><span class=3D"gmail_signature_prefix">-- </span><br><div dir= =3D"ltr" class=3D"gmail_signature">Ivan Zhakov</div></div> </div> --0000000000005819c80657c0393d--