a href area to enlarge

Hello!

I have such tag:

Re: a href area to enlarge

> Link
> to page

Thank you. It works but padding variable is not need

K.

Re: a href area to enlarge

In article ,
"K." wrote:

> > Link
> > to page
>
> 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?

--
dorayme

Re: a href area to enlarge

On 2007-06-22, dorayme wrote:
> In article ,
> "K." wrote:
>
>> > Link
>> > to page
>>
>> 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 -- but generally not much taller.

Re: a href area to enlarge

In article ,
Ben C wrote:

> On 2007-06-22, dorayme wrote:
> > In article ,
> > "K." wrote:
> >
> >> > > >> > style="display:block;padding:40px;">Link
> >> > to page
> >>
> >> 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 -- but generally not much taller.

I was a little puzzled to know what OP would benefit from 2 over
1 in



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.)

--
dorayme

Re: a href area to enlarge

On Sat, 23 Jun 2007 12:16:48 GMT dorayme scribed:

>> >> > >> >> > style="display:block;padding:40px;">Link
>> >> > to page
>> >>
>> >> 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 -- but generally not much taller.
>
> I was a little puzzled to know what OP would benefit from 2 over
> 1 in
>
>
>
> The differences are all a bit strange across different browsers
> and text sizes.

As you suggested earlier, I see no difference in "the big three" (between
examples 1 & 2) except ie6 cuts off the top and bottom border. Ergo, the
OP's reply is puzzling.

--
Neredbojias
He who laughs last sounds like an idiot.

Re: a href area to enlarge

On 2007-06-23, dorayme wrote:
> In article ,
> Ben C wrote:
>
>> On 2007-06-22, dorayme wrote:
>> > In article ,
>> > "K." wrote:
>> >
>> >> > >> >> > style="display:block;padding:40px;">Link
>> >> > to page
>> >>
>> >> 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 -- but generally not much taller.
>
> I was a little puzzled to know what OP would benefit from 2 over
> 1 in
>
>

1 and 2 work out the same, but if in each case you give the
containing the 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.