Active Topics
-
Extra softwares in Sailfish using CLI, repositories, etc (117)
to SailfishOS by nieldk - 1 day, 12 hrs ago -
Firefox with Leste (6)
to Maemo 7 / Leste by teroyk - 2 days, 9 hrs ago - more...
 |
|
2008-04-07
, 23:15
|
|
Posts: 868 |
Thanked: 474 times |
Joined on Oct 2007
@ Capital District, NY, USA
|
#22
|
Originally Posted by GeraldKo
It's a fine tradeoff... and unfortunately MicroB doesn't have smart enlarging of link targets. The other item is that later target areas that overlap "win" so to speak. I've been playing with some more advanced css for trying to be "smarter" about links close to each other, but the more I put in the worse it seems to perform in general.
Also, I pretty much like the enlarged link targets, but sometimes they seem too large and, in a crowded field of links, I find that the link "next door" gets activated instead of the one I was tapping on.
|
|
2008-04-08
, 10:29
|
|
Posts: 309 |
Thanked: 51 times |
Joined on Apr 2007
|
#23
|
For the overlapping links I found the following is a bit more conservative but still finger-friendly:
/* Make links bigger by default, can still be overridden by pages */
a { padding: 0.5em; margin: -.4em; }
|
|
2008-04-09
, 01:56
|
|
Posts: 868 |
Thanked: 474 times |
Joined on Oct 2007
@ Capital District, NY, USA
|
#24
|
Here is some of my latest stuff. The input css stuff seems pretty stable, all it does is increase the minimum size of the elements so that they can be easily selected and manipulated with a finger.
It's still a fine tradeoff between reducing the impact the border has on the layout of the page and overlapping links where one might be hard to select. Really what I need is css math so that I can enlarge links based on it's volume.
Last edited by brontide; 2008-04-09 at 02:00.
It's still a fine tradeoff between reducing the impact the border has on the layout of the page and overlapping links where one might be hard to select. Really what I need is css math so that I can enlarge links based on it's volume.
Code:
/* this is what I'm using now... using the psudeo elements seems to create fewer conflicts with site css files, salt to taste */
a:link, a:visited { padding: 5px; margin: -1px }
/* make all sorts of input fields more finger friendly by banishing small textareas, checkboxes, and radiobuttons */
input { min-height: 18px ! important }
input[type="checkbox"], input[type="radio"] { min-width: 20px ! important; min-height: 20px ! important; margin: 5px 10px 5px 15px !important }
Last edited by brontide; 2008-04-09 at 02:00.
| The Following User Says Thank You to brontide For This Useful Post: | ||
 |
|
2011-04-06
, 16:23
|
|
Posts: 2,427 |
Thanked: 2,986 times |
Joined on Dec 2007
|
#25
|
Still one of the more useful threads. Here's an example of my latest attempt to take control of the tmo experience:
Code:
img[alt="lucas777's Avatar"] { display: none ! important }
__________________
N9: Go white or go home
N9: Go white or go home
The page often renders in a way other than the designer intended. Specifically, frames (is that the right word? chunks of the webpage, like columns) often get lined up one below the other instead of side-by-side. (See, for example, the Homepage of The New York Times.) Usually, I find that a worthwhile trade-off.
What would be nice is if there were an easy way to toggle those settings on and off, switching at will to the original browser settings for userContent.css and prefs.js. (I've kept copies of both original files, but manually switching them out isn't "easy".) Or switching between two different modified sets of those files. Does anybody have the skills to create that option? Are the Brontide changes something that could be used inside a Greasemonkey script and thereby toggled between "Enabled" and "Disabled"?
Also, I pretty much like the enlarged link targets, but sometimes they seem too large and, in a crowded field of links, I find that the link "next door" gets activated instead of the one I was tapping on.
.
. .
Help Save This Forum for N8x0/Diablo Users! Register and Vote for Solution #1 on this Brainstorm. (The Solution will let you see New Posts with any threads you choose -- like the N900 and Maemo5/Fremantle threads -- filtered out.) (To understand the Solution better, see these posts #17, #18, and #19.)