From: Jambunathan K <kjambunathan@gmail.com>
To: Aankhen <aankhen@gmail.com>
Cc: Org mailing list <emacs-orgmode@gnu.org>
Subject: Re: bug: hovering window obscures text
Date: Tue, 03 May 2011 11:11:01 +0530 [thread overview]
Message-ID: <81ei4gcpea.fsf@gmail.com> (raw)
In-Reply-To: <BANLkTimwcu0yfd3afkX7t2-=ZMspVt_MCw@mail.gmail.com> (aankhen@gmail.com's message of "Tue, 3 May 2011 10:32:54 +0530")
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.
Jambunathan K.
>
> Meanwhile, for a quick fix, try this user style:
>
> http://userstyles.org/styles/47418/worg-disable-fixed-toc
>
> Aankhen
>
>
--
next prev parent reply other threads:[~2011-05-03 5:41 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 [this message]
2011-05-03 5:56 ` Aankhen
2011-05-03 7:00 ` Aankhen
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=81ei4gcpea.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=aankhen@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).