Posted by Ben C on 06/23/07 22:41

On 2007-06-23, dorayme <doraymeRidThis@optusnet.com.au> wrote:
> In article <slrnf7pjm7.dbt.spamspam@bowser.marioworld>,
> Ben C <spamspam@spam.eggs> wrote:
>
>> On 2007-06-22, dorayme <doraymeRidThis@optusnet.com.au> wrote:
>> > In article <f5gh8p$ja0$1@news.onet.pl>,
>> > "K." <halinacierniak@poczta.onet.pl> wrote:
>> >
>> >> > <a href="http://www.example.com"
>> >> > style="display:block;padding:40px;">Link
>> >> > to page</a>
>> >>
>> >> Thank you. It works but padding variable is not need
>> >>
>> >
>> > If you don't have padding, what quite is the difference between
>> > no style at all in the link and mere display: block for your
>> > purpose? You delivering the padding from elsewhere?
>>
>> Padding will still make the clickable area wider-- the full width of the
>> space available in the <td>-- but generally not much taller.
>
> I was a little puzzled to know what OP would benefit from 2 over
> 1 in
>
><http://members.optushome.com.au/droovies/test/display.html>

1 and 2 work out the same, but if in each case you give the <td>
containing the <a> a styled width making it wider than it is at the
moment, then the clickable area should be wider in 2.

> The differences are all a bit strange across different browsers
> and text sizes.
>
> (just btw, I discovered that iCab breaks the line after // in the
> left cell and wraps the www bit! unless one gives a big explicit
> width to the table.)

It does that even when the viewport is wide enough to fit everything
without any linebreaks? That is odd.

Breaking after the // and before www when the available space starts to
become restricted I think may possibly be the correct thing to do
according to Unicode breaking classes, although it's not what Firefox
does.

[Back to original message]