Re: Some RFCs are unreadable on phone?
Nicolas Giard <[email protected]> Fri, 17 Jul 2026 04:27:34 -0400
| Newsgroups | gmane.ietf.general |
|---|---|
| Message-ID | <CAL_px1Pj+8iKEeyqwf4-Qs0P3bEw4UhrQpyyajD_un4hA=HW6A@mail.gmail.com> |
--000000000000bab0580656ca54d7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Job, This is definitely a bug. Please create an issue on https://github.com/ietf-tools/red/issues and include the list of RFCs that have problems. Feel free to submit UI improvement suggestions there as well. Nick On Fri, Jul 17, 2026 at 3:55=E2=80=AFAM Job Snijders <job=3D40bsd.nl@dmarc.= ietf.org> wrote: > Hi, > > If I=E2=80=99m not mistaken, it used to be the case that RFC document HTM= L content > properly flowed, as in, you could always read specifications on narrow > screens (like your phone) without constantly scrolling right to left and > back. > > Nowadays for _some_ RFCs it=E2=80=99s harder to quickly read the spec on = your > phone, text disappears beyond the right border, see attached screenshot. > Tried 2 browsers on iPhone: Safari and DuckDuckGo. Some tables also rende= r > poorly with sideways scrolling inside sideways scrolling. Also, IMHO havi= ng > the title persist at the bottom wastes valuable screen real estate. > > The current content presentation puts me at a disadvantage when trying to > settle arguments in the hallway track ;-) > > What=E2=80=99s the process to improve the presentation? > > Kind regards, > > Job > > Ps. Only seems an issue with some RFCs > > > --000000000000bab0580656ca54d7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Hi Job,<div><br></div><div>This is definitely a bug.</div>= <div>Please create an issue on=C2=A0<a href=3D"https://github.com/ietf-tool= s/red/issues">https://github.com/ietf-tools/red/issues</a> and include the = list of RFCs that have problems.</div><div><br></div><div>Feel free to subm= it UI improvement suggestions there as well.</div><div><br></div><div>Nick<= /div></div><br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D= "ltr" class=3D"gmail_attr">On Fri, Jul 17, 2026 at 3:55=E2=80=AFAM Job Snij= ders <job=3D<a href=3D"mailto:[email protected]">[email protected]= tf.org</a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"m= argin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left= :1ex">Hi,<br> <br> If I=E2=80=99m not mistaken, it used to be the case that RFC document HTML = content properly flowed, as in, you could always read specifications on nar= row screens (like your phone) without constantly scrolling right to left an= d back.<br> <br> Nowadays for _some_ RFCs it=E2=80=99s harder to quickly read the spec on yo= ur phone, text disappears beyond the right border, see attached screenshot.= Tried 2 browsers on iPhone: Safari and DuckDuckGo. Some tables also render= poorly with sideways scrolling inside sideways scrolling. Also, IMHO havin= g the title persist at the bottom wastes valuable screen real estate.<br> <br> The current content presentation puts me at a disadvantage when trying to s= ettle arguments in the hallway track ;-)<br> <br> What=E2=80=99s the process to improve the presentation?<br> <br> Kind regards,<br> <br> Job<br> <br> Ps. Only seems an issue with some RFCs<br> <br> <br> </blockquote></div> --000000000000bab0580656ca54d7--