From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] hover
Date: Thu, 22 Feb 2018 13:54:18 -0500 [thread overview]
Message-ID: <20180122135418.eklhad@comcast.net> (raw)
This from Geoff.
==============================
Well here the concept of 'hovering' is a bit misleading. Such dropdown
menu lists are really always there in html, they are just marked
visually 'hidden'...
That is `display: none;` in css terms. Then when you hover that is
changed to 'display: block;`...
Try browsing my example http://geoffair.org/tmp/test4.html... visually
I only 'see' Dropdown' in a browser, until I hover the mouse
over it...
And in EB I correctly see the three links... virtually ignoring
the `display: none;`, which is fine...
==============================
His little test program, derived from nasa, is important for all of us to digest and understand.
It was asked long ago if edbrowse should scan through all the css and "hide" those things with display none.
This example suggests we should not, for such things only come to light if you hover over something,
and you can't hover in edbrowse, you wouldn't even know that was a possibility, so those links would be forever lost.
This moves us towards the thing I was worried about 20 years ago when I started this;
some websites are so dog gone visual that edbrowse just won't be able to simulate them in a textual manner.
I hope I'm wrong, and we can shoehorn most websites into our model.
Karl Dahlke
next reply other threads:[~2018-02-22 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 18:54 Karl Dahlke [this message]
2018-02-23 5:47 ` [Edbrowse-dev] return value from removeChild Kevin Carhart
2018-02-23 6:05 ` Karl Dahlke
2018-02-23 6:17 ` Kevin Carhart
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180122135418.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.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.
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 NNTP newsgroup(s).