14 replies

1. Alesandro Ortiz 🇵🇷🏳️‍🌈 Mastodon 20 min later

   @zachleat I haven't noticed any changes recently. Quick testing shows non-trailing-slash paths redirect to trailing-slash path on a couple of my Netlify sites.

   Haven't deployed in a few days, but not sure if that would change behavior.

   1. Zach Leatherman Mastodon 28 min later

      @AlesandroOrtiz appreciate the sanity check! 🙌

      1. Alesandro Ortiz 🇵🇷🏳️‍🌈 Mastodon 3 hr later

         @zachleat Were you able to investigate further?

         This would be a breaking change for us, so want to make sure behavior didn't change (intentionally or due to a bug).

         1. Zach Leatherman Mastodon 3 hr later

            @AlesandroOrtiz I did and it still looks broken to me (I have pretty urls disabled):

            https://www.zachleat.com/web/trailing-slash
            https://www.zachleat.com/web/trailing-slash/
            https://www.zachleat.com/web/trailing-slash/index.html
            https://www.zachleat.com/web/trailing-slash.html

            all resolve without redirect.

            I am still investigating, I may have an errant _redirect? not sure

            1. Khalid ⚡ Mastodon 3 hr later

               @zachleat @AlesandroOrtiz It's a battle I wage in my mind all the time. It's not settled. Good slashes died out there maaaaaan!

            2. Alesandro Ortiz 🇵🇷🏳️‍🌈 Mastodon 3 hr later

               @zachleat Hm, I am seeing the issue on my personal site: https://alesandroortiz.com/articles should redirect to /articles/ but doesn't. I'm pretty sure it did before.

               But on a couple other sites that I tried earlier, it does redirect with a 301. Will check what might be different between them.

               1. Alesandro Ortiz 🇵🇷🏳️‍🌈 Mastodon 4 hr later

                  @zachleat Ok, the difference is pretty URLs is enabled on the ones that _do_ redirect, and disabled on the ones that _don't_ redirect.

                  Seems like the same you are seeing.

                  They all use 11ty with `/dir/index.html` output (so /articles/ on my personal site is /articles/index.html)

                  1. Zach Leatherman Mastodon 4 hr later

                     @AlesandroOrtiz might need to cheekily ping the friendly @eduardoboucas on this one?

                     1. Alesandro Ortiz 🇵🇷🏳️‍🌈 Mastodon 4 hr later

                        @zachleat I'll have you reach out to Netlify folks since it's not broken on my prod sites where it would be a breaking change. And I'm on free plan so I can't ping support directly either.

                        Would be great to have it fixed on my personal site, but not critical there. I'll just hopefully not run into this in the future until it's fixed. :/

                        I wonder how long it's been like this.

                        1. Zach Leatherman Mastodon 4 hr later

                           @AlesandroOrtiz hmm, same!

2. Dean Leigh Bluesky 22 min later

   Hi @zachleat.com - I noticed these word breaks and wondered if hyphens: auto; reduce readability in certain contexts? No criticism, just curios if it's accessibly has been documented for it's use in paragraph text.

   
   1. Zach Leatherman Bluesky 36 min later

      Oh, huh, after git blaming that it’s about 9 years old (we may never know what user was responsible for it though *ahem*)

      Agree though that it feels aggressive! Gonna revert it

      1. Dean Leigh Bluesky 1 hr later

         Hehe I have thought about it for headings in the past but modern CSS and fluid typography seems to address most cases now.

         1. Tobias Fedder Bluesky 17 hr later

            Hyphenation is needed, especially for German writing. But when it comes to headings, it's a balancing act. I agree, modern CSS helps avoid it.
            Still, can't wait for baseline `hyphenate-limit-chars`.
            I have headings with `text-wrap:balance`, I need to pair them with `hyphens:manual` most of the time.