From: Aankhen <aankhen@gmail.com>
To: Jambunathan K <kjambunathan@gmail.com>,
Samuel Wales <samologist@gmail.com>,
Org mailing list <emacs-orgmode@gnu.org>
Subject: Re: bug: hovering window obscures text
Date: Tue, 3 May 2011 12:30:42 +0530 [thread overview]
Message-ID: <BANLkTinFbqrPaadLLZJyHrkAj-pff35dbw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinCsoc+zaR5t=nX6tr1jUMK4iKKuQ@mail.gmail.com>
(Sorry for replying to my own message.)
On Tue, May 3, 2011 at 11:26, Aankhen <aankhen@gmail.com> wrote:
> On Tue, May 3, 2011 at 11:11, Jambunathan K <kjambunathan@gmail.com> wrote:
>> Aankhen <aankhen@gmail.com> writes:
>>
>>> On Mon, May 2, 2011 at 22:39, Samuel Wales <samologist@gmail.com> wrote:
>>>> On this page
>>>>
>>>> http://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 large fonts.
>>>>
>>>> To reproduce, set the minimum font size in Firefox to the largest
>>>> available setting.
>>>>
>>>> I wonder if a non-hovering solution is possible? I know we discussed
>>>> this before at one point, with several good designs.
>>>
>>> I’m not familiar with the prior discussions. The current design seems
>>> okay to me—notwithstanding the flaw you mention—because it strikes a
>>> good balance between making the TOC easily accessible and minimizing
>>> the amount of space it takes up. Of 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’m not sure how accessibility is hindered, given that the contents of
> the page are still perfectly accessible. All the fixed TOC does is
> obscure a very small portion of them on occasion, which can be
> rectified by scrolling. I would call that inconvenient, not
> inaccessible. Unless there’s more happening here beyond what I’ve
> 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
next prev parent reply other threads:[~2011-05-03 7:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 17:09 bug: hovering window obscures text Samuel Wales
2011-05-03 5:02 ` Aankhen
2011-05-03 5:41 ` Jambunathan K
2011-05-03 5:56 ` Aankhen
2011-05-03 7:00 ` Aankhen [this message]
2011-05-04 7:59 ` Eric S Fraga
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTinFbqrPaadLLZJyHrkAj-pff35dbw@mail.gmail.com \
--to=aankhen@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@gmail.com \
--cc=samologist@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).