From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aankhen Subject: Re: bug: hovering window obscures text Date: Tue, 3 May 2011 12:30:42 +0530 Message-ID: References: <81ei4gcpea.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([140.186.70.92]:41728) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QH9bV-0005Qn-13 for emacs-orgmode@gnu.org; Tue, 03 May 2011 03:01:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QH9bT-0005i7-VP for emacs-orgmode@gnu.org; Tue, 03 May 2011 03:01:04 -0400 Received: from mail-vx0-f169.google.com ([209.85.220.169]:62504) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QH9bT-0005i1-Rk for emacs-orgmode@gnu.org; Tue, 03 May 2011 03:01:03 -0400 Received: by vxk20 with SMTP id 20so6192999vxk.0 for ; Tue, 03 May 2011 00:01:03 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Jambunathan K , Samuel Wales , Org mailing list (Sorry for replying to my own message.) On Tue, May 3, 2011 at 11:26, Aankhen wrote: > On Tue, May 3, 2011 at 11:11, Jambunathan K wrot= e: >> Aankhen writes: >> >>> On Mon, May 2, 2011 at 22:39, Samuel Wales wrote= : >>>> On this page >>>> >>>> =C2=A0http://orgmode.org/worg/org-faq.html#closing-outline-sections >>>> >>>> a hovering window in the upper right corner obscures text. >>>> >>>> This is possibly, but not necessarily, especially so when you use larg= e fonts. >>>> >>>> To reproduce, set the minimum font size in Firefox to the largest >>>> available setting. >>>> >>>> I wonder if a non-hovering solution is possible? =C2=A0I know we discu= ssed >>>> this before at one point, with several good designs. >>> >>> I=E2=80=99m not familiar with the prior discussions. =C2=A0The current = design seems >>> okay to me=E2=80=94notwithstanding the flaw you mention=E2=80=94because= it strikes a >>> good balance between making the TOC easily accessible and minimizing >>> the amount of space it takes up. =C2=A0Of course, this is predicated on= the >>> assumption that people actually want to use the TOC, and often enough >>> to justify it taking up that space. >> >> Considering that Samuel is making his argument from accessibility >> perspective, "Accessibility" is one another predicate that is missing in >> your assumption. > > I=E2=80=99m not sure how accessibility is hindered, given that the conten= ts of > the page are still perfectly accessible. =C2=A0All the fixed TOC does is > obscure a very small portion of them on occasion, which can be > rectified by scrolling. =C2=A0I would call that inconvenient, not > inaccessible. =C2=A0Unless there=E2=80=99s more happening here beyond wha= t I=E2=80=99ve > seen, that is. Poking around a little shows that the current design is entirely unusable via keyboard. Now that does seem like a gamebreaker, accessibility-wise. Aankhen